Practice · June 22, 2026 · 8 min read

Multi-domain B2B setups: tracking several sites without losing the picture

Product site, marketing site, docs, regional TLDs, a legacy microsite nobody wants to sunset. Real B2B companies live on multiple domains. Here is how to track them without turning your data into confetti.

Three stylised browser windows connected by lines meeting at a central glowing node on a navy grid.

Every real B2B company runs on more than one domain. There is the marketing site, the docs subdomain, the app on a different host, the country TLDs someone launched in 2022, and the microsite for the acquired product that nobody has quite retired. If you are trying to track identified visitors across all of that as if it were one site, you are going to end up with confusion dressed as data. Here is how to structure it so the picture stays coherent.

The default: one workspace per web property

Start with the simplest rule: one workspace per top-level web property. Marketing site is one. Docs subdomain is another. Country TLDs are separate. This is not a purity argument — it is because each property tends to have a different owner, a different intent profile, and a different definition of "a good visit". Bundling them into one workspace produces a busy dashboard nobody trusts.

When to add a consolidated view

One workspace per property does not mean you cannot see the total picture. A consolidated view — "any identified company that touched any of our web properties this week" — is where the interesting patterns live. A company visiting the marketing site, then the docs, then a regional TLD in 48 hours is a much stronger signal than any single property would show on its own. Set up the consolidated view once you have three or more workspaces in play.

The five pitfalls (in order of frequency)

PitfallWhat happensFix
Same snippet ID across domainsAttribution collapses; you cannot tell docs from marketingOne property = one workspace
Cross-domain "session" assumptionsYou count one company as two, or vice versaTreat each domain as its own scope; join at company-level in the consolidated view
Docs traffic dominates the numbersMarketing metrics look flat because docs drowns themKeep docs in a separate workspace and out of marketing KPIs
Regional TLDs unlabelledYou cannot answer "who is visiting in DACH?"Suffix workspace names with region; use it in filters
Sunsetted microsite still firingGhost visits from a domain nobody ownsRemove the snippet or archive the workspace
Multi-domain gotchas we see repeatedly and the honest fix.

Ownership beats architecture

The most common failure in multi-domain setups is not technical. It is that no single human owns "the whole picture". Nominate one person to look at the consolidated view once a week and be the arbiter of "is a company across multiple properties actually important". That role does not need to be senior — it needs to be consistent. Two months of the same pair of eyes beats any org-chart decision.

Tagging you will thank yourself for later

Two labels save more time than any dashboard: property (which of your domains they visited) and journey shape (marketing-only, docs-only, marketing→docs, docs→marketing). Both are trivial to add during setup and painful to backfill later. Add them now; your future self will owe you a coffee.

The migration shortcut

Coming from a single-workspace setup and dreading the split? Do not migrate historical data — just cut over today and archive the old workspace as read-only. The two weeks of parallel views cost less than any migration plan you can write.

A note on compliance across domains

If your domains have different privacy policies, opt-out controls, or DPA arrangements (e.g. an acquired brand still on its own terms), keep them in separate workspaces so the audit trail matches the legal reality. Merging them into one workspace to "clean up" ends the audit trail and creates a compliance headache. Match the data structure to the legal structure, not the other way round.

  • Related: [Installing a tracking snippet the right way](/blog/install-tracking-snippet-wordpress-shopify-gtm)
  • Related: [Server-side vs client-side tracking](/blog/server-side-vs-client-side-tracking-what-matters-for-b2b)
  • Related: [Company-level tracking: what it stores](/blog/b2b-tracking-without-cookies)
lead.box Team

Published by

lead.box Team

More articles

See lead.box on your own traffic

Start free — no card, no sales call required. Or book a 20-minute walk-through if you want the guided tour.

Start free trial

Notes on GDPR B2B lead intelligence

B2B Lead Identification Platform

lead.box — Identify the companies visiting your website

lead.box turns anonymous B2B website visitors into named companies. GDPR-first, first-party only, with EU data processing.

What lead.box does

How it works

  1. Add a single lightweight tracking snippet to your website.
  2. lead.box identifies the companies behind each visit using first-party IP intelligence.
  3. Hot leads are scored, enriched with contact data and exported as a file for your sales team.

Quick links