Tracking visitors across multiple websites involves three separate jobs: measuring the journey, identifying eligible visitors, and joining records in your CRM. Installing a tag on each domain does not automatically solve all three.
At Leadpipe, we support multiple pixels so teams can separate traffic and delivery workflows. This guide explains how to design a multi-domain setup without assuming that browser cookies, identities or client permissions transfer between properties.
The answer: inventory your domains, configure the appropriate measurement and identification tools on each, then test the downstream join. A unified contact view must be demonstrated with actual records, not inferred from the fact that two pixels share an account.
Separate measurement from identification
| Layer | Question it answers | What to verify |
|---|---|---|
| Analytics | How did a visitor move between properties? | Cross-domain measurement and campaign continuity |
| Identification | Can eligible activity be linked to a company or person? | Returned identity, source domain and observation time |
| CRM | Which existing record owns that activity? | Matching rules, account ownership and duplicate handling |
| Permissions | Which team or client may access it? | Organization boundaries and destination access |
A single person can generate many sessions. A single company can have many visitors. Keeping these units separate prevents a returning visitor from becoming several “new leads” in a report.
If you are choosing the identity layer, read the company-level versus person-level comparison first.
Build a domain map before installing pixels
Use one row per property. The example below is a proposed configuration, not a record of a customer’s setup.
| Property | Purpose | Identification scope | Destination |
|---|---|---|---|
www.example.com |
Marketing site | Approved commercial pages | Main sales review queue |
docs.example.com |
Product documentation | Only the sections approved for the pilot | Existing-account research queue |
campaign.example.net |
Campaign microsite | Campaign landing pages | Same CRM with source retained |
| Client-owned property | Separate client’s website | Client-specific scope | That client’s destination only |
Document who owns each property and who can approve changes. A domain under the same brand can still have different data-handling requirements. Separate clients should not share a contact queue simply because the same agency operates their pixels.
Keep internal tools, authenticated areas and sensitive paths outside the scope unless they have been explicitly approved for the intended use.
Configure analytics across domains separately
Google’s cross-domain measurement guidance explains how GA4 maintains measurement across configured domains. Test actual links between properties and verify that redirects preserve the required linker information. Analytics continuity does not itself produce a named contact.
Check source attribution before and after the transition. A visitor moving from a campaign page to the main site should not acquire a misleading new campaign simply because a redirect or intermediate page discarded its context.
Keep person records in the systems designed to handle them. Google’s data-redaction guidance describes controls for reducing inadvertent email and query-parameter collection. Do not put contact details in tracking URLs to create your own cross-domain identity system.
Set up Leadpipe pixels by property
The current pixel management guide supports using separate pixels for distinct domains, brands and routing needs. Create the pixel for the property, use its generated snippet, and verify it in the dashboard. Do not copy a guessed installation URL from a blog post.
Use the available path controls to define the intended scope. The Identification API introduction documents include-only and exclusion modes as mutually exclusive. Check the current schema if you manage pixels programmatically.
Then configure the receiving workflow. Keep its source pixel or domain alongside the identity and event time. This source context helps investigate a failed join and prevents one property’s visit from being reported as another property’s performance.
Design the CRM join explicitly
A downstream identity policy is an operations decision. Write down the matching key your integration will use and how it behaves when that key is missing. Do not join two people because they share a name or employer.
A useful delivery record has two distinct concepts:
- Person or company key: identifies the entity you are updating.
- Activity key: identifies the visit or delivery event so retries do not duplicate activity.
The exact fields depend on the integration. Verify them against the real payload and destination schema. A repeat delivery should not create a second contact or restart outreach. A genuine new visit should remain visible without erasing the previous activity.
Preserve the CRM’s assigned owner and suppression state. If the record already belongs to an active opportunity, route the context to its owner rather than treating the visitor as a new prospect. See the suppression guide for the operating principles.
Test the transitions that usually break
| Test | Expected behavior | Evidence to retain |
|---|---|---|
| Main site to documentation | Source and destination activity remain attributable | Analytics trace and destination record |
| Repeat eligible match | Existing entity is reused where the matching key supports it | CRM record IDs before and after |
| Integration retries delivery | One activity is recorded once | Delivery history and activity ID |
| Missing matching key | Record is held for review or follows a documented fallback | Rejection or review log |
| Suppressed record revisits | It stays out of the outreach queue | Suppression and destination evidence |
| Client A versus client B | Destinations and access remain separate | Client-specific test records |
Use approved test accounts and avoid treating a tester who is not matched as proof the installation failed. Pixel verification, page activity and successful identification are separate checks.
Repeat the transition tests when you change redirects, consent behavior, the receiving integration or a domain’s ownership. A setup can continue showing traffic while silently losing the context sales relies on.
Report results without double counting
Show each domain’s eligible traffic and accepted records, plus a deduplicated total for the relevant organization. The sum of domain-level people can exceed the total because the same person visited several properties. That is expected when the join is working.
Report agency clients separately. For a shared organization, distinguish new contacts from additional activity on existing contacts. A docs visit from an existing customer may be useful to customer success, but it is not automatically new acquisition pipeline.
Use the ROI guide when connecting these records with financial outcomes.
FAQ
Can I create more than one Leadpipe pixel?
Yes. The product documentation supports multiple pixels. Check your account’s plan and organization controls for the commercial and permission details of your setup.
Does a shared account guarantee cross-domain identity stitching?
No. Verify the returned identifiers and downstream matching behavior. Sharing an account or installing pixels does not prove every visit will resolve to the same person.
Do multiple domains change the price?
Compare the current plan and required domain setup with your actual volume. Do not assume every additional domain or client is included; confirm the applicable terms on the pricing page or with the provider.
What should an agency evaluate?
Evaluate client separation, ownership, access and delivery alongside coverage. The white-label guide covers the commercial model; the technical pilot should establish that records reach the correct client.
Start with two properties and one destination
Review Leadpipe Identification, then start a trial with a deliberately small scope. The offer is 7 days or 500 profiles, whichever comes first, no card. Expand after the identity, attribution and destination checks pass.
