Cross-domain tracking · Documentation-based guide

Cross-domain lead attribution: map and test the journey

Content updated:

Short answer

Cross-domain tracking requires identity and source continuity along the actual visitor journey. Map domains and forms, configure supported continuity and test the final lead; installing the same script on two sites does not establish a shared session.

Key verification: Check the identifier across domains and define a fallback for pages you cannot modify.

Sources and limitations

If a visitor moves from your website to another domain to request a quote or make a reservation, the system may lose their tracking identity and attribute the contact to the second site. First draw the complete route. Installing the same code on two domains does not prove that they both share a session.

Domain, subdomain and external page

Document the input URL, each hop, and the URL where the conversion occurs. Distinguishes a new page from the same domain from a separate domain. Identify which part you control and where you need the external provider to intervene.

WhatConverts explains that its own cookies do not automatically accompany the visitor between separate domains. For this journey, refer to support to implement cross-domain tracking using the visitor ID. It also flags potential consent or subdomain issues. Official diagnosis of cookies and domains .

Route map

Cross-domain lead attribution: map and test the journey: table 1
Step Fictitious example Control question
Advertising entry web-a.example/quote Is the authorized source captured?
Link to external service reservations-b.example/home What identifier can the link carry?
Confirmation reservations-b.example/confirmation Where is the accepted conversion recorded?
Business record Test contact in CRM Does it retain the expected origin or does an internal reference appear?

The example domains are illustrative. Do not add names, emails or telephone numbers to URLs to preserve identity. Technical identifiers also need proper processing and permissions; transporting them does not make the tracking anonymous.

Request a specific configuration

Provides the provider with the map of URLs, jumping mechanisms and available technical access. Ask if the external system supports the necessary changes and what happens to visitors without consent for such tracking. Don't compensate for user rejection with hidden parameters.

If there is a form in an iframe, the problem may be different: its capture and link to the containing page. The forms guide explains that validation. This article addresses continuity of identity and origin during navigation between sites.

Test protocol

  1. Opens a new session and documents browser and consent status.
  2. Enter with parameters of a fictional test campaign.
  3. Loop through the actual links to the second domain without manually copying the final URL.
  4. Complete a contact with its own test data.
  5. Verify identifier, source and chronology in the lead system.
  6. Repeats with a direct entry to the second domain and with unauthorized tracking.

Direct input must preserve a result other than the labeled traversal when that is the design. The no-tracking scenario may produce incomplete information; document that limitation rather than forcing attribution.

If the second site does not support changes

Keep a verifiable campaign link and measure only what you can credit. You can separate visits that go to the service from conversions confirmed by it, explaining that you do not have a complete individual connection. An honest partial report is preferable to assigning all contacts by temporal proximity.

Choosing a tool

WhatConverts may fit if support confirms the path and exact implementation. Don't buy expecting any external domain to be joined automatically. The acceptance result is a test contact with correct origin and trace limits documented for each scenario.

Sources and limitations

Documentary review: . Content type: Documentation-based guide.

Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.

How to report a correction

Check current terms

Consider these options if they solve the problem described. Confirm features, limits and availability in your country.

WhatConvertsAffiliate link

The labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.

How this guide was prepared

Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.