You run more than one website. Maybe it’s your main marketing site and a separate product documentation site. Maybe it’s regional domains for different markets. Maybe you acquired a company last year and their site is still running on a different domain. Maybe your agency manages 15 client websites from a single account.
Whatever the reason, you have multiple domains - and each one generates visitor traffic independently. Google’s Search Central documentation covers the SEO implications of multi-domain setups, but the analytics and identification challenges are equally significant. Your analytics are fragmented. Your CRM gets duplicate contacts. And the same person who visited your main site on Monday and your product site on Wednesday looks like two completely different visitors.
This is the multi-domain problem. And it gets worse with visitor identification, because fragmented identification means fragmented contact records, fragmented scoring, and fragmented outreach. Your sales team doesn’t know that the VP who browsed your pricing page also spent 10 minutes reading your API documentation on a different domain. They see two unconnected data points instead of one strong buying signal.
Leadpipe solves this with a unified account structure that supports multiple domains. One account, one pixel per domain, one unified contact view. Here’s how to set it up and the use cases it unlocks.
The Multi-Domain Problem
When you run multiple domains without unified tracking, every domain operates as an island. The problems compound:
Fragmented visitor history. As Google Analytics documentation notes, cross-domain tracking with GA4 requires additional configuration and still operates at the session level, not the person level. Sarah Chen visits your marketing site (acme.com) on Monday and views the pricing page. On Wednesday, she visits your developer docs site (docs.acme.com) and reads the API integration guide. Without multi-domain tracking, these appear as two separate visitors. You miss the fact that the same person is evaluating both your business case and your technical fit - a combined signal much stronger than either visit alone.
Duplicate CRM contacts. When visitor identification runs independently on two domains, each domain creates its own contact record in your CRM. Now you have two “Sarah Chen” records with different activity histories. Your SDR sees one record showing a pricing page visit. A different SDR sees another record showing API doc activity. Neither has the complete picture.
Inconsistent scoring. Your lead scoring model only sees activity from one domain. Sarah’s composite score on the marketing site might be 45 (warm). Her score on the docs site might be 30 (cold). Combined, she’d score 75 (hot). But because the scores live on separate records, nobody acts with the urgency her actual behavior warrants.
Double outreach. Two separate records mean two separate sequences. Sarah might get an email from your marketing team about the pricing page visit AND an email from your developer relations team about the API docs visit. That’s a terrible experience for her and a waste of your team’s time.
The solution is unified identification across all domains, resolving to a single contact record regardless of which domain the visitor is on.
How Multi-Domain Identification Works
Leadpipe’s identification engine works at the person level, not the domain level. When a visitor is identified on any of your domains, the identification resolves to the same contact record.
How it works:
- Each domain gets its own Leadpipe pixel (a unique snippet of JavaScript)
- All pixels are associated with your single Leadpipe account
- When a visitor is identified on Domain A, Leadpipe creates a contact record
- When the same visitor is identified on Domain B, Leadpipe matches them to the existing record
- The contact record accumulates activity from all domains
Matching logic:
Leadpipe uses deterministic matching to identify visitors. The match is based on the person’s identity, not the domain they’re visiting. So if Sarah Chen is identified on acme.com via her email address, and she later visits docs.acme.com, the same deterministic match resolves her to the same contact record.
What the unified record looks like:
Contact: Sarah Chen
Email: sarah.chen@globex.com
Title: VP of Marketing
Company: Globex Corp (250 employees)
Activity:
acme.com/pricing - April 7, 2m 34s
acme.com/case-studies/saas - April 7, 1m 15s
docs.acme.com/api/getting-started - April 9, 4m 12s
docs.acme.com/integrations/hubspot - April 9, 2m 45s
blog.acme.com/visitor-identification-guide - April 10, 3m 20sOne person, one record, complete activity history across all your domains. Your sales team sees the full picture.
Setup: One Account, Multiple Pixels
Setting up multi-domain tracking with Leadpipe is straightforward. No complex cross-domain cookie configurations, no tag manager gymnastics.
Step 1: Add domains to your Leadpipe account
In the Leadpipe dashboard, navigate to Settings and add each domain you want to track. Each domain gets its own pixel ID.
Step 2: Install the pixel on each domain
Each domain receives a small JavaScript snippet. Install it the same way you’d install any tracking pixel - directly in the HTML, via Google Tag Manager, or through your CMS’s script injection feature.
<!-- Domain 1: acme.com -->
<script src="https://cdn.leadpipe.com/pixel/YOUR_PIXEL_ID_1.js"></script>
<!-- Domain 2: docs.acme.com -->
<script src="https://cdn.leadpipe.com/pixel/YOUR_PIXEL_ID_2.js"></script>
<!-- Domain 3: blog.acme.com -->
<script src="https://cdn.leadpipe.com/pixel/YOUR_PIXEL_ID_3.js"></script>Step 3: Verify installation
Visit each domain and check the Leadpipe dashboard to confirm data is flowing. Each domain should appear as a separate source in your reports, but contacts should be unified.
That’s it. No cross-domain linking scripts. No first-party cookie synchronization. No subdomain configuration. Leadpipe’s identification is identity-based, not cookie-based, so cross-domain tracking works natively.
Unified Contact View
Once multi-domain tracking is running, the contact view in Leadpipe shows activity across all domains in a single timeline. This is the key differentiator from running separate tracking tools on each domain.
What you see per contact:
- All pages viewed across all domains, with timestamps and duration
- The domain each page belongs to, so you can understand the cross-domain journey
- Visit sequence, showing how the visitor moved between domains over time
- Firmographic data, resolved once and applied to all domain activity
Cross-domain journey example:
Day 1: acme.com/blog/visitor-identification-guide (3m)
Day 1: acme.com/product (1m 30s)
Day 3: docs.acme.com/api/authentication (5m)
Day 3: docs.acme.com/api/webhooks (4m)
Day 5: acme.com/pricing (2m 45s)
Day 5: acme.com/case-studies/enterprise (1m 20s)This journey tells a clear story: the visitor started with content (awareness), moved to technical evaluation (consideration), and then revisited for pricing and social proof (decision). If this activity were split across two separate tracking systems, you’d only see fragments of the story.
CRM integration:
When you push Leadpipe data to your CRM via webhooks or native integrations, multi-domain activity flows into a single contact record. Configure your webhook to include the domain field so you can see which domain each page view came from:
{
"email": "sarah.chen@globex.com",
"page_url": "/api/webhooks",
"domain": "docs.acme.com",
"duration_seconds": 240,
"timestamp": "2026-04-09T14:23:00Z"
}Use Case 1: Main Site + Product Site
This is the most common multi-domain scenario. Your marketing site lives at acme.com. Your product or documentation site lives at app.acme.com or docs.acme.com.
The insight gap without unified tracking:
Your marketing team sees that a visitor checked out your pricing page. Your product team sees that someone read your API documentation. Nobody connects these two signals.
What unified tracking reveals:
Visitors who check pricing AND read technical docs are significantly more likely to convert than visitors who do only one. They’re evaluating both the business case and the technical fit simultaneously - which means they’re further along in the buying process than either signal alone would suggest.
Actionable workflow:
IF visitor viewed pricing on acme.com
AND visitor viewed API docs on docs.acme.com
WITHIN 7 days
THEN route to AE with "technical buyer" tag
AND include both marketing site and docs activity in the alertThis multi-domain trigger catches buying behavior that a single-domain setup would miss entirely.
Use Case 2: Regional Domains
Companies operating in multiple geographies often run regional domains: acme.com for the US, acme.co.uk for the UK, acme.de for Germany, acme.com.au for Australia.
The regional tracking challenge:
Without unified tracking, a prospect who evaluates your US site and then checks your UK site (maybe to see if you support their London office) creates two separate visitor records. Regional sales teams have no visibility into cross-market activity.
What unified tracking provides:
- A single view of visitors who browse multiple regional sites
- The ability to see which regions a prospect is interested in (informing deal scope)
- Deduplication of contacts across regional CRM instances
Example scenario:
A VP of Marketing at a global company visits acme.com and checks US pricing. Two days later, she visits acme.co.uk and checks UK-specific features. This tells you she’s evaluating your product for a multi-region deployment - a much larger deal than a single-region purchase. Without multi-domain tracking, two different regional reps might each pursue a single-region deal independently.
Use Case 3: Acquisition Brands
After an acquisition, you often run the acquired company’s website alongside your own for months or years. The acquired brand has its own traffic, its own content, and its own audience.
The acquisition tracking challenge:
Visitors to the acquired brand’s website don’t appear in your main site’s analytics. If someone visits the acquired brand’s site and then visits your main site, you see them as two different people.
What unified tracking reveals:
- Visitors evaluating both brands (researching the relationship between them)
- Acquired brand visitors who might be interested in your expanded product suite
- Cross-sell opportunities where a visitor of one brand needs the other brand’s capabilities
Migration use case:
If you’re planning to sunset the acquired brand and migrate customers to your main platform, multi-domain tracking lets you identify acquired-brand visitors who are also exploring your main site. These visitors are naturally transitioning and may be receptive to migration-focused messaging.
Use Case 4: Agency Multi-Client Management
Agencies managing visitor identification for multiple clients need multi-domain tracking for an entirely different reason: operational efficiency.
The agency challenge:
Each client has their own website. Without a unified management layer, you’re logging into separate accounts, running separate reports, and managing separate webhook configurations for every client.
Leadpipe’s agency solution:
With Leadpipe’s white-label dashboard, agencies can manage multiple client domains from a single account. Each client’s data is isolated (Client A can’t see Client B’s visitors), but the agency has a master view across all clients.
What this enables:
- Centralized reporting: See identification rates, visitor volume, and lead quality across all client domains from one dashboard
- Shared webhook infrastructure: Use a single webhook endpoint that routes data to different CRM instances based on the domain field
- Cross-client insights: Identify patterns and benchmarks across your client portfolio
- Scalable onboarding: Add new clients by adding a domain and installing a pixel, not provisioning an entire new account
For agencies running visitor identification at scale, multi-domain support isn’t optional - it’s the foundation of a manageable operation. Learn more about the agency setup in our multi-tenant guide.
Leadpipe supports unlimited domains per account. Identify visitors across all your websites with a unified contact view. Start with 500 free identified leads.
Domain Filtering in API Queries and Webhooks
When you’re tracking multiple domains, you need the ability to slice data by domain. Leadpipe supports domain filtering in both API queries and webhook configurations.
API domain filtering:
Query visitors from a specific domain:
GET /api/visitors?domain=docs.acme.com&start_date=2026-04-01Query visitors who visited multiple domains:
GET /api/visitors?domains=acme.com,docs.acme.com&cross_domain=trueThe cross_domain=true parameter returns only visitors who were seen on both domains - the highest-value cross-domain signals.
Webhook domain routing:
Create separate webhooks for different domains to route data to different destinations:
| Domain | Webhook Destination | Use Case |
|---|---|---|
| acme.com | Salesforce + Slack #sales | Marketing site visitors -> sales team |
| docs.acme.com | Slack #product-leads | Technical evaluators -> product team |
| blog.acme.com | HubSpot nurture workflow | Content readers -> nurture sequence |
| All domains (cross-domain) | Slack #hot-leads | Multi-domain visitors -> priority routing |
Domain-specific scoring:
You can also apply different lead scoring weights based on the domain. A visitor who reads your blog gets standard content scoring. The same visitor who then checks your API documentation gets technical-evaluation scoring. Combine both for the composite score.
FAQ
Do I need a separate Leadpipe plan for each domain?
No. Multiple domains are managed under a single Leadpipe account. Your identification credits are shared across all domains. If you’re on the Starter plan with 500 identifications, those 500 IDs apply to visitors across all your tracked domains.
Does this work with subdomains (docs.acme.com) and completely different domains (acmeproduct.com)?
Yes to both. Subdomains and entirely separate domains are supported. Each gets its own pixel, but all data flows into the same account with unified contact records.
How does cross-domain identification work without cookies?
Leadpipe uses deterministic identity resolution, not cookies. The identification is based on the visitor’s identity, not their browser state. This means cross-domain tracking works natively without any cookie synchronization or cross-domain linking scripts. If Sarah Chen visits Domain A and then Domain B, she’s identified as the same person on both, regardless of cookies.
Can I give different teams access to different domains?
Yes. Leadpipe supports role-based access. You can configure team members to see data from specific domains only. Your marketing team sees acme.com data. Your product team sees docs.acme.com data. Your leadership sees everything.
What about GDPR? Does multi-domain tracking change anything?
The same compliance rules apply regardless of how many domains you track. For EU visitors, Leadpipe provides company-level identification only. For US visitors, person-level identification is available. The multi-domain structure doesn’t change the compliance framework - it’s applied per visitor, not per domain.
How do I handle microsites that only run for a few weeks?
Add the domain when the microsite launches, install the pixel, and start tracking. When the microsite ends, you can deactivate the domain in your account settings. The visitor data from the microsite period remains in your account and can still be queried.
One Visitor, One Record, Every Domain
Your websites might be fragmented, but your understanding of your visitors doesn’t have to be. Multi-domain tracking turns isolated data points into a complete picture of how each prospect engages with your brand across every touchpoint.
The setup takes minutes per domain. The payoff is a unified view that catches cross-domain buying signals your competitors’ fragmented tracking will never see.
Leadpipe supports unlimited domains. One account, unified contacts, complete activity history. Start with 500 free identified leads, no credit card required.
Start tracking visitors across all your domains →
