- GA4
- GTM
- sGTM
- Google Ads
Several sites of one network: the ad is on one, the request comes on another
What is wrong
Picture a network of travel agencies. The network runs a shared brand site, and every city is a separate franchise: its own site, its own ad budget, its own Tag Manager (the tag container on the site), its own property in analytics (a separate GA4 account) and its own reports. You bought the franchise and you run Da Nang. You advertise to your own site – but some customers, before they leave a request, move to the brand site: to compare cities, read reviews, choose a tour. That is where they leave the request. The network forwards those customers to you and the business gets them. But the Da Nang ads get nothing: the request landed in the brand's reports, not in your account.
Then the loss mechanics. The city's ad brings a customer to its site, and the conversion happens on another site of the network. In the reports it shows up as "direct" (the visitor came on their own) or as a referral from the brand site, and the city's ad that brought it gets no credit.
Example. Da Nang's ads bring 100 customers. 30 of them leave a request on the brand site. The network forwards those 30 to Da Nang and the business gets them. But the Da Nang ad account sees 70: Google Ads learns from 70, the report shows a result almost a third worse than the real one, and the budget is cut in the campaign that brought all 100. The requests that disappear belong to people who moved between the network's sites, that is, to those who chose more carefully.
The legend in this demo: a network of travel agencies in Vietnam. The network runs a brand site, every city is a separate franchise with its own site, its own ad budget, its own GTM and its own reports. All the businesses are fictional.
What the business loses
- The ad identifier is lost when the visitor moves between sites. Google Ads and Meta optimise towards the conversions they can see. A request left on another site of the network does not exist for bidding.
- In analytics the source of the request is "direct" or a referral from the network site. In the reports the franchise's ads look useless, and its budget is the first one cut.
- Two views, both true. For the network owner, a customer who clicked a Da Nang ad and left a request on the brand site is still a sale. For the Da Nang franchise it is a lost budget. A customer who left Da Nang, wandered through the network and came back is a gap for both: the ad that found them gets no credit, and the algorithm learns nothing.
Ways to close the gap
| Option | Pros | Cons | In the demo |
|---|---|---|---|
| One Google tag on every domain (GA4 cross-domain linking) | The official path: Google itself carries the visitor's identifier between your domains inside the link. | Needs one property (analytics account) and one owner across all domains, and that is not always available. In this fictional example the city franchises are separate owners with their own properties, so the linking does not apply. | description only |
| A signed hand-off between sites | Each site keeps its own container and its own property. The first site asks our server for a single-use code and adds it to the link; the second site exchanges the code for the journey and sets its own cookie. Two cookies, two properties, one journey. | Needs server-side GTM (Tag Manager on a server) on your domain, with the journey record set up on it. The code is only issued when consent allows it. | in the demo |
What the demo does
The demo keeps one journey record on its own server. Site A (the network) hands the journey to Site B (the franchise) with a single-use signed code. Site B exchanges the code for the journey and sets its own cookie: the sites have separate properties and separate containers, and the journey is one.
In a real project the hand-off is built on server-side GTM (Tag Manager on a server, through which events reach analytics): keeping the record, issuing the code and exchanging it become one more job for that server. A separate service for this can be written, but in effect it becomes your own server-side GTM: you would maintain it yourself, and it would lack the rest of what server-side GTM offers. With server-side GTM you get that at once: events reach analytics from your own domain, the cookie is set by the server, and conversions can be sent to ad platforms straight from the server (the demo does not do this).
Consent decides whether any of this happens. In the opt-out regime (US and most of the world) the journey is created at once. In the opt-in regime (EU, UK, CH) nothing is stored and no code is issued until the visitor accepts; on decline the hand-off link says why: "No hand-off token: consent was not given, so no cross-site identifier is passed."
The demo shows the mechanics, not a finished integration. The demo click id (a click marker) is never sent to Google Ads – validating a real gclid needs a live campaign. The demo sets its identifier from the server, which makes it more durable than a script-written one; testing for weeks in every browser is a separate step.
Open the demo
It opens already set up for this case, with server-side transport. While "Start clean" is ticked, every run starts anew: the demo's cookies and data are reset on both sites of the network.
https://alpha.nexusnode.ru/?utm_source=GAds&utm_medium=CPC&utm_campaign=case_cross_domain&demo_click_id=GADS-11111&al_case=cross-domain-journey&al_lang=en&al_transport=server&al_regime=auto&al_guide=1&al_reset=1The demo shows that the source survives the move between the network's sites: from the brand site to the city site the journey continues – the first touch, the campaign and the timestamp are kept, even though the sites have different analytics and different containers. You see it on the "Show what was recorded" panel: status LINKED and the same journey ID on both sites. Where to click and what happens is prompted by the demo itself.
About the author
I used to be a design engineer in the power industry. In 2013 I traded that for an online store, a loan from friends and ads that sold nothing. Things improved from there, mostly. Clients' businesses grew several times over, and a few even asked me to pause the ads so they could get a break from the phone. Thirteen years in, I still enjoy this more than is probably professional.
The long version, awkward bits included →
Book a call
Bring the addresses of your sites. I will follow a customer's path from an ad click through all your sites and show what happens to the source of the request: whether it reaches the report or the request turns into "direct".