Cross Domain Tracking
Cross Domain Tracking provides a way to track a visitor's journey across multiple domains. This enables you to track your mobile app to a subdomain to the website and back again!
Cross Domain Tracking provides a way to track a visitor's journey across multiple domains. This enables you to track your mobile app to a subdomain to the website and back again! It's now fairly common for businesses to break down their applications into smaller parts by using different domains and sub-domains.
When you are working with unique domains, you can track visitors in a couple different ways.
- You can track visitors using multiple Woopra projects and keep this data separate.
- You can send all of your customer data to a single project.
The second option is the Woopra preferred method for customer tracking, as this will provide a full customer journey and offers the most actionable insights for your business.
The importance of cross-domain tracking is to not only store your data in a single project, but to also maintain a visitors session when they explore unique domains. The events of previously identified visitors should be monitored and associated with the same customer profile, regardless of the domain they visit. This is the key to providing a comprehensive customer journey.
When a visitor visits an alternate domain, the cookies associated with that visitor are inaccessible, which causes split profiles in your Woopra project. Without the cookie to associate to the visitor, Woopra has no way of knowing that the visitor on the new domain is the same as the visitor from the previous domain. Woopra would require the visitor to again identify themselves by signing up to an email list or logging in to the platform.
This is the problem that cross-domain tracking solves. When configured correctly, Woopra will attach the cookie value to the url of all specified domains, allowing it to associate that cookie with the visitor from your previous domain.
Throughout the following Methods section, we will show you the necessary
woopra.config() alterations you will need to make within this tracking snippet.
Updated over 4 years ago