How the ad trail passes between your sites
The ad trail (also called customer source, cross-site tracking or cross-domain attribution) is the information about which campaign brought a person in. Your business has several “homes” on the internet: your profile on goconverso.com, your own domain, ZapVerso on zapverso.com, the customer app, the booking page and form embedded on someone else’s website, and the pages you publish in Pages, which also go live as a static page. Each one keeps the customer’s source separately. Before, someone who arrived from an ad on your profile and then moved to another home showed up at the destination “out of nowhere”, and the ad lost its credit. Now GoConverso carries the campaign along, on the paths the product itself builds for the visitor.
This works on its own, with nothing to turn on. To see the result (how many customers came from each ad and how much money), use the Return tab of the Ads app, available on the paid plans Plus, Pro, Max and Ultra.
What does the trail carry from one site to the other?
When a visitor moves from one home to another through a path that GoConverso builds, the URL carries:
- The ad campaign: the
utm_source,utm_medium,utm_campaign,utm_contentandutm_termparameters, as the ad created them. - The tracked link code, when the click came from one of your tracked links (
gcl). - The real click time (
gcq). So a click from yesterday still counts as yesterday and does not become “now” at the destination. - The ad click identifier (Meta’s
fbclid, for example): only when the visitor accepted cookies on BOTH sides, on the site they left and on the site they went to, and only if the click is up to 90 days old. A visitor with the “Global Privacy Control” signal on in their browser counts as not having accepted.
Without consent at the destination, only the campaign (utm_*) and one arrival cross over. Never the click identifier, never anything that identifies the browser. ZapVerso has no cookie banner, so a click identifier never goes to it, even when the visitor accepted on your profile.
Where does the trail pass today?
| From where to where | What happens |
|---|---|
| Chat button on your site or profile to ZapVerso | The button that opens zapverso.com/@yourbusiness carries the campaign and the click time. ZapVerso notes the arrival in its own home. |
| Page you publish in Pages (static version), to your profile | The buttons that lead to YOUR profile (goconverso.com/your-username...) get the campaign and the click time. The GoConverso brand link in the footer stays as it is. |
| Booking page embedded on third-party sites | The campaign of the page of the site where the booking page sits reaches your CRM along with the booking. |
| Form embedded on third-party sites | Same thing: the campaign of the site page reaches you along with the form submission. |
| Chat embedded on third-party sites | The chat button opens ZapVerso through the same path as the first row, carrying the campaign. |
| ZapVerso to your CRM | If the conversation creates the contact, the ad arrival stays linked to that contact. |
How does ZapVerso link the ad to the contact?
ZapVerso keeps the visitor’s arrival (the campaign, the link code and the click time) separately for each business @. When the conversation becomes a contact, whether through a message, through Leave a message or through the sign-up inside the conversation, the arrival becomes part of that contact’s history. If that contact books or buys later, the credit shows up in Return.
The arrival is only linked to the contact when the conversation creates the contact. If the email typed in already belonged to a customer of yours, nothing changes in their history. This protects against someone typing another person’s email.
In ZapVerso the arrival is stored without a click identifier and without a browser identifier, because there is no cookie banner there.
What about the booking page and form embedded on third-party sites?
The embed code (embed.js) copies the campaign from the page of the site where you pasted the code and hands it to the embedded booking page or form. Each booking page and each form keeps its arrival separately (an agency can embed different businesses on the same site without mixing campaigns). The embed also records the third-party page as the landing page, not the address of the embedded frame. Without cookie consent, only the campaign and one arrival cross over. The click identifier from the outside page is not copied, and it does not appear inside the page address or referrer the embed hands over either.
Only the form embedded on a third-party site carries the campaign. Form sections inside your GoConverso site did not change.
What does NOT pass from one site to the other?
- The link YOU paste in your Instagram bio, a status or a WhatsApp conversation, and the QR code. When you are the one building the link, the history in the browser is yours, not the customer’s. So those links carry no campaign at all, on purpose.
- Emails. Email has its own attribution.
- The customer app on a
.appdomain and the one on the subdomain (yourapp.goconverso.com) of the same app do not join. They are two homes that cannot see each other. - Someone who reaches ZapVerso through the home page (
zapverso.com) and only then opens your@: the arrival stays on the home page and does not follow. - A click identifier going to ZapVerso, in any case.
A link I build vs a link the site builds: which one carries the campaign?
| Who builds it | Carries the campaign? | |
|---|---|---|
| Chat button on your site, page published in Pages, embed | GoConverso, in the visitor’s browser | Yes |
| Profile link, ZapVerso invite, chat link you copy and paste | You, in your browser | No |
What changes in Return?
Because the campaign now follows the customer when they move between sites, the number of customers from ads may go up in the Return tab, especially for those who get customers through more than one place (profile and ZapVerso, for example).
What arrives through these doors counts as an origin touch. It is not a conversion or a sale, and nothing is sent to Meta because of it. Money still comes only from the booking, store order or sale the customer makes afterwards. Since the real click time travels along, an old click may not count as the last ad (the window is 28 days), but can still count as the first ad that introduced the customer (up to 13 months). See How the Return tab counts your money.
Common problems
The ad disappears when the customer moves to another site
Check how they moved. The trail only passes through paths GoConverso builds (chat button, page published in Pages, embed). If they went through a link you pasted, through email, or between the .app app and the subdomain one, the trail does not pass. See the list in “What does NOT pass”.
Why does my link have utm_ and gcq in the address bar?
It is the ad campaign and the click time. They do not identify the person, and the server checks everything again before saving it.
The customer did not accept cookies. What crosses over?
The campaign (utm_*), the link code and the click time, and a single arrival. Never the ad click identifier or the browser identifier.
My .app app and the subdomain one do not join
Correct. Each address is a separate home in the browser and they cannot see each other. A customer who uses both appears as two visits.
My old page does not carry the campaign
Only pages published or edited after this update get the feature. For an older page, edit anything and save, or unpublish and publish again. The script only touches links that lead to your profile, not the GoConverso brand link in the footer.
The ZapVerso button shows the ad source and not “site button”
That is expected. When the visitor came from an ad, the ad source wins, so the ad is not lost. Someone who arrived without an ad still shows up as coming from the site button.
The ad arrival does not show on the ZapVerso contact
The arrival is only linked to the contact when the conversation creates the contact. If the email typed in already belonged to a customer of yours, nothing changes in their history.
What the trail does not do
- It does not create a server-side bridge between sites: what crosses over travels in the link address.
- It does not add a cookie banner to ZapVerso or the embed.
- It does not carry a click identifier without consent on both sides.
- It does not record a conversion or a sale, and does not send anything to Meta by itself.
- It does not change pages published before the update, until you edit them or publish them again.
Related
Ads (Meta Ads): the Return tab shows how much each ad brought in.
Ads (Meta Ads)How the Return tab counts your money: Received, Booked and what goes to Meta.
How the Return tab counts your moneyZapVerso: the profile and conversation at zapverso.com/@yourbusiness.
ZapVersoBooking System: how to put the booking page on your website.
Booking System