Cross-Domain Tracking

Overview

By default, Ruler’s Tracking Tag is designed to track visitors on a single domain and any associated subdomains.

If your customer journey moves visitors between separate domains that you manage, Ruler can be configured to support cross-domain tracking. This ensures visitor sessions and attribution data continue seamlessly as users move between websites.

📘

Please note this is not an out the box feature so will not work without additional configuration.

When You May Need Cross-Domain Tracking

Cross-domain tracking is commonly required when part of your customer journey takes place on another domain, such as:

• Ecommerce checkouts that occur on a different domain
• Third-party booking or application platforms
• Microsites or campaign landing pages

How Cross-Domain Tracking Works

To enable cross-domain tracking, Ruler’s Tracking Tag must be installed on your primary domain and any additional domains involved in the customer journey.

The additional domain URLs must be provided to Ruler Analytics so they can be configured within your account to allow Ruler Analytics to enable and configure the cross-domain setup for you.

Once configured, visitor tracking and attribution data can continue across the connected domains.

Requirements

Before cross-domain tracking can be enabled, ensure that you manage and control all domains involved and that Ruler’s Tracking Tag is implemented on each domain and that you can provide the full URLs for the additional domains

Getting Started

To set up cross-domain tracking, speak with your Ruler Analytics onboarding manager to confirm your tracking requirements and validate the domains involved.

Need Help?

If you are unsure whether your setup requires cross-domain tracking, contact your Ruler Analytics onboarding manager for advice.