Keep visitor journeys connected across domains
Connect your main website, store or booking site so a visitor can follow a link between them without losing their active session or original campaign.
What you’ll achieve
- Linked visits retain the anonymous visitor ID, active session and original campaign across your configured websites.
What you’ll need
- Two HTTPS sites you control, on separate domains or subdomains
- The same Leado Marketing website pixel installed and allowed to run on both sites
Follow the workflow
-
1
Open Settings → Website & pixel
In the correct workspace, open the Website & pixel tab in Settings and find Cross-domain tracking. It is off until you enable it.
-
2
Add both sides of the journey
Enter each separate HTTPS domain on a new line, for example example.com and example-store.com. Adding a parent domain automatically includes all its subdomains: example.com also covers www.example.com and shop.example.com without extra entries. One parent-domain entry is enough if you only need to connect its subdomains. You can list up to 20 domains whose subdomains you also control. Enter names without wildcards; IP addresses and custom ports are not supported. Enable cross-domain tracking and select Save website settings. Allow about 90 seconds for the website configuration to refresh.
-
3
Use the same website pixel on every domain
Install the website script shown in this tab once on each site, using the same workspace pixel. If it is already installed, do not add another copy. The script also powers on-site features such as popups and surveys. Keep its activation connected to your existing consent setup. A native Shopify app pixel is a separate source and does not replace this shared website script for cross-domain handoffs.
-
4
Understand when the two-minute timer starts
The handoff is created when a visitor clicks a supported link to a listed domain—not when they arrive on the first website. Someone can spend 3 or 20 minutes on website A and still receive a fresh handoff when they click through to website B. The destination pixel has 2 minutes from creation to process it. This is separate from the normal 30-minute session inactivity rule.
-
5
Test a linked journey
Start on website A with recognizable campaign tags, such as utm_source=cross-domain-test&utm_medium=test&utm_campaign=setup-check. Let the pixel load, wait more than 2 minutes, then click a normal link to website B. In Pixel Tracking, open Event explorer and inspect the visitor journey. Confirm that events from both domains share the session ID and that the original campaign remains in the session-arrival parameters. The temporary leado_xd parameter should disappear from the destination URL after the pixel handles it.
Verify your work
- Events from the source and destination appear together with the same session ID
- The original campaign remains visible in session-arrival parameters
- Links outside configured domains and their subdomains are left unchanged
If something doesn’t look right
The destination shows a separate session
Check that each hostname is a configured domain or its subdomain, and verify that both sites load the same website pixel. A specific entry such as shop.example.com covers its own descendants, but not example.com or sibling subdomains; use the parent example.com to include them all. Confirm tracking is enabled, configuration has refreshed and consent or blockers did not delay the destination pixel. A missing, expired or already-used handoff falls back to the destination’s own session.
A redirect or custom button loses the handoff
Normal website links and supported new-tab clicks are handled automatically. Redirects must preserve leado_xd until the destination pixel loads. For JavaScript navigation, ask your developer to await window.leadoDecorateLink(url) immediately before navigating. Form submissions and custom routers are not automatically decorated.
A copied link no longer recognizes the visitor
Each handoff is single-use and valid for 2 minutes after creation. Do not save decorated links for later or reuse them for other visitors. Click the original website link again to create a fresh handoff.
Limitations and safeguards
This connects supported linked navigation, not unrelated visits, different browsers or different devices. Both websites need the same website pixel; unrelated pixel sources are not merged.
The handoff follows the existing pixel activation and consent setup. It does not activate a blocked pixel or transfer consent decisions.
Important notes
Time spent on website A does not use up the handoff window. The two-minute window only covers the transfer after the click. Later explicit campaign tags can still appear as subsequent touchpoints; they do not replace the session’s original arrival.