Cross-Domain Tracking¶

By using the Cross-Domain Tracking feature, services that run across completely different multiple domains will be able to associate user data among those domains and track data accordingly. For example, if a website that runs on example.com has links between example.co.jp, by activating Cross-Domain Tracking these two domains will be able to share the same data of their users.

Please note that Cross-Domain Tracking is not necessary for sites that are running on different sub-domains such as mail.example.com and news.example.com. Cross-Domain Tracking is necessary only when the root domain differs.

Supported cases of Cross-Domain Tracking¶

When following a link via <a> tag from the source domain to destination domain

Note

Example:

Links on E-commerce site to an external checkout system/site
From a landing page domain to the actual service domain

Unsupported cases of Cross-Domain Tracking¶

Page transitions via form submission with <form> tags
Navigation with page redirection
Servers that order to redirect to the browser, more specifically that return response with redirection status code along with Location header, could also copy the original query parameters, although these cases heavily depend on the server implementation and therefore are not supported.

Points to consider while configuring¶

When these options are not configured properly Web SDK may not be able to collect data properly, so please make sure that this implementation will be done by those with knowledge of HTML and JavaScript.

Important notes¶

When multiple domains are integrated as one service while having authentication individually and you want to activate Cross-Domain Tracking two-way (often times this is described as "MultiTenant Service"), since user identification data from the source domain will override the one for the destination domain you need to configure this feature with that behavior in mind

Points to consider while configuring¶

Below is a more detailed description of what's written in API related to Cross-Domain Tracking

1. linker_domains (required)¶

Please assign an array of domains you wish to track as cross-domain to linker_domains

reproio("setup", "YOUR_REPRO_SDK_TOKEN", {
  linker_domains: ["blog.example.com", "shop.example.com"],
})

If the given domain matches the current domain the user is viewing the links won't be regarded as cross-domain target. Please see the below table for different cases combining the current domain, destination domain of a link and what is configured as linker_domains. When the table says YES then parameters for cross-domain tracking will be added to the links.

2. disable_linker_params_referrer_check¶

When the Web SDK tries to transfer the data from the Cross-Domain source, it first checks the document.referrer value and see if this navigation can be regarded as cross-domain. Unless one of the domains set as linker_domains matches the domain of document.referrer Cross-Domain Tracking will not be activated.

By setting disable_linker_params_referrer_check to true, the check whether document.referrer matches any of the domains from linker_domains will not be performed, which will result in always activating Cross-Domain Tracking regardless to the source of the navigation.

In addition, referrer domain checks will also have the same logic described in the table for linker_domains. For instance, if linker_domains: ['example.com'] had been specified, Cross-Domain Tracking will be activated when the access was from referrers such as example.com or sub.example.com.

Warning

Important notes

If the link with Cross-Domain Tracking parameters added becomes publicly accessible, for instance via social media or within chat tools, Cross-Domain Tracking may be activated under unintended situations resulting in associating users' data inappropriately.

reproio("setup", "YOUR_REPRO_SDK_TOKEN", {
  linker_domains: ["blog.example.com", "shop.example.com"],
  disable_linker_params_referrer_check: true,
});

3. disable_auto_attach_linker_params¶

Web SDK not only adds linker parameters for Cross-Domain Tracking when the page is loaded, but also observes the DOM changes and automatically adds appropriate parameters to new a tag links. If this behavior is not necessary, you can turn it off by setting true to disable_auto_attach_linker_params.

reproio("setup", "YOUR_REPRO_SDK_TOKEN", {
  linker_domains: ["blog.example.com", "shop.example.com"],
  disable_auto_attach_linker_params: true,
});

4. updateLinkerParameters¶

Web SDK adds linker parameters for Cross-Domain Tracking upon page load. For sites that have relatively long user session length or perhaps using the disable_auto_attach_linker_params option, there may be cases where you would want to manually update new links adding the Cross-Domain parameters. For such situation you could call the reproio('updateLinkerParameters'); method to add parameters to missing a links and refresh the data manually.

reproio("updateLinkerParameters");