Cross Domain Tracking

Cross Domain Tracking provides a way to track a user'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 users in a couple different ways.

1. You can track users using multiple Woopra projects and keep this data separate.
2. 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 user's session when they explore unique domains. The events of previously identified users 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 user visits an alternate domain, the cookies associated with that user are inaccessible, which causes split profiles in your Woopra project. Without the cookie to associate to the user, Woopra has no way of knowing that the user on the new domain is the same as the user from the previous domain. Woopra would require the user 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 user from your previous domain.

Your Woopra configuration will require an update of your provided JavaScript Tracking code. In some instances, when using a different SDK, the tracking code will be different, but in this guide we will cover the implementation for our JavaScript tracking SDK.

Throughout the following Methods section, we will show you the necessary woopra.config() alterations you will need to make within this tracking snippet.