The Hidden Cost of Cross-Domain and Subdomain Tracking Gaps
www.yourcompany.comapp.yourcompany.comhelp.yourcompany.comgo.yourcompany.comyourcompany.scheduler-tool.com
That's a normal B2B website: four subdomains and a scheduler on someone else's domain. Each piece was set up by a different person, at a different time, with different tracking. Somewhere in the handoffs the source gets lost, so UTMs disappear before the form and pipeline shows up in the CRM with no origin.
The fix depends on which kind of gap you have. Subdomains and separate domains break in different ways, and a lot of advice treats them as the same thing.
Subdomains and separate domains fail differently
Subdomains of the same root (www.yourcompany.com, app.yourcompany.com, go.yourcompany.com) usually aren't a GA4 problem. GA4's default cookie covers the whole root domain. If every subdomain runs the same tag, a visitor keeps one ID and one session as they move around. You don't need cross-domain measurement for this.
Subdomains break when:
- One of them is missing the tag. Usually the app, the help center, or a page built in some other tool.
- One sends to a different GA4 property.
- Someone set a custom cookie domain on one site.
- Consent settings differ, so tags fire on one subdomain and not the next.
Separate root domains are a different animal. yourcompany.com and yourcompany-app.io can't share cookies. Neither can a scheduler or checkout on its own domain. Without cross-domain measurement, the visitor lands on the second domain as a brand new person, the source becomes your own website as a referral, and the conversion loses the campaign that started it.
Search your referral sources for your own domain name. If it's near the top, that's the gap.
The part GA4 doesn't fix: forms and the CRM
GA4 can be set up perfectly and your CRM will still only know what the form sends it.
UTMs live in the landing page URL. Someone lands on a blog post, reads two more pages, and fills out the demo form on another subdomain. The hidden UTM fields come through blank, unless something saved the values when they arrived.
That saving has to reach every place a form lives:
- A first-party cookie set on the root domain can be read on every subdomain.
- Browser local storage can't. It belongs to one subdomain only.
- Separate domains need the values passed along in the link, or the form tool's own tracking.
- A form embedded in an iframe from another domain can't be reached by your page's scripts. Use the non-iframe embed if you can, or pass the values in the iframe URL if the tool supports it.
(The setup for those fields: hidden form fields for HubSpot UTM tracking.)
How to find your gaps
Check which hostnames send data. In GA4, open Explore, start a free-form exploration, add Hostname as a dimension. Compare that list to every domain and subdomain your company runs. Anything getting traffic that isn't in the report is probably missing the tag. Rule out a consent banner, a filter, or a tag sending to another property first.
Look for your own domain as a referral. In Traffic acquisition, switch to Session source / medium and search for your own domain names. Seeing them there is the signature of a separate-domain gap.
Confirm one measurement ID everywhere. Run Tag Assistant on each domain and subdomain. Every one should fire the same GA4 tag.
Watch the trend in Direct, not a number. There's no universal "too much direct." A direct share that jumps after a site launch, a new subdomain or a consent change is worth chasing. A steady one might just be your audience. (More on what's hiding in direct.)
Check the CRM on its own. Pull contacts created from forms on each subdomain and landing page tool, and see how many have UTM values. A form whose contacts never have UTMs is a capture gap, whatever GA4 says.
The fix, by case
- Same-root subdomains: the same GA4 tag on every subdomain, the cookie domain left on its default, consent behaving the same everywhere.
- Separate domains: in GA4, go to Admin, Data streams, your web stream, Configure tag settings, Configure your domains, and add every domain you own. Then click from one domain to the other and check the URL carries a
_glparameter. Redirects that strip parameters will break it. - Third-party tools: schedulers, checkouts and landing page builders each handle this their own way. Some take the GA4 tag, some don't. For the ones that don't, track the conversion as an event on your own site instead.
- HubSpot tracking code: on every domain and subdomain. Its cookie works across subdomains. Separate domains need to be listed in HubSpot's tracking settings.
- Forms: hidden UTM fields on every form, on every domain, filled from a root-domain cookie.
After any change, do one test visit with a tagged link, start to finish. Land, cross domains, submit a form, then check GA4 and the new CRM record.
The one nobody remembers is the landing page tool someone bought for one campaign in 2023.
Why this gets missed
Tracking gaps don't announce themselves. The data keeps flowing, it just credits conversions to your own website or to Direct and fills the CRM with records that have no source.
It tends to come up one of two ways. A campaign launches on a landing page tool and tracking shows almost nothing, even though the form is filling. Or someone audits attribution and finds a big share of pipeline with no source at all.
Either way, finding the gap takes longer than fixing it.
Want yours checked?
Get a free Tracking Scan
I'll open your homepage and one landing page the way an ad click does and write down what fires, which redirect drops your UTMs, and what your cookie banner changes. Done by hand, back in two business days.
Request a scanRather score it yourself? Run the free audit.
Notes from the Field.
Every other week, one broken thing and how I’d fix it.
One email every other week · unsubscribe anytime · Privacy policy