Cross-Domain Tracking with Personyze
Personyze enables automatic tracking of user activities across different domains! Doing so will enable you to track the entire activity of users throughout all your domains.
The process involves running a custom function that will open an iFrame to the requested domains (if the function does not include specific domains URLs, Personyze will automatically use all domains defined in your account “domain settings”).
The iFrame is linked to a URL which contains a few URL parameters representing user information such “user id”, “session ID”, “always segment”, etc. Using the iFrame URL mechanism enables Personyze to check if this user has already visited another domain, and if so, it will extract his existing user ID provided by the other domain and will open a cookie for him which will be based on that data.
Doing so will ensure that all activities done on both (or more) domains will be attributed to the SAME user. To achieve cross-domain tracking, please follow one of the following two options.
Option 1:
- Define all the domains you’d like to track in the “Domain Settings” page
- Place the Personyze tracking code into all the different domains you’d like to track
- Run the following function (using a JavaScript action) on all the new visitors to each one of the domains:
JavaScript API Reference
For developers, the cross-domain identity passing exposes two helper calls. These are the same functions used internally by the snippets above.
Push the visitor’s identity to all configured domains
Fires a request to each homepage in your account’s domain list, ensuring the same visitor maps to the same Personyze profile across every domain you’ve registered:
(self.personyze = self.personyze || []).push(['Delegate identity']);
Wrap a single outbound link with identity
For one-off cross-domain links (a CTA pointing at a different brand domain, for example), append the user/session ID to the URL so it round-trips with identity attached:
var url = 'https://yourlink.com';
var wrapped = _S_T.pass_cookie_url(url, true);
// Use `wrapped` as the href for the link
The second argument (true) signals that this is an SSL link.