Specific Implementations

Cross-Domain Tracking

Cross-domain tracking helps you follow the user in the case when one or more pages are hosted on a different domain name than the original one. Cross-domain tracking is necessary when a website has a page (payment confirmation, for example) that redirects the user to an external domain. To set-up a cross-domain tracking, go on this page on the settings.

You can add a URL pattern as a setting for pages hosted on other domains. Then, click Add and validate your modification.

Since cross-domain tracking is relying on third-party cookies to operate, the feature will no longer work on browsers or environment that don't support these cookies anymore. It can be the browser type (Safari or Firefox), specific settings, the use of extensions or any other external element that might block third-party cookies. This feature is still supported by Google Chrome for the moment. All visitors that are not using a browser or environment compatible with third-party cookies won't be tracked over domains, even when the feature is properly set up.

Server-Side Rendering

If you are using server-side rendering (SSR) on your website, you might need to add a specific implementation for your tag.

In some situations, you might need to ask our tag to wait before applying its modifications. Indeed, with some SSR frameworks, modifying the DOM before the reconciliation has occurred might cause performance or render issues.

You can force our tag to lock its execution until you unlock the tag. To achieve that, you need to declare a variable before injecting our tag:

window.lockABTastyTag = true;

Once you consider your page to be ready for front-end modifications, you can call the following method to unlock our tag:

window.unlockABTasty();

For more information, please refer to the complete technical documentation about global methods and variables or our troubleshooting article on cross-domain tracking limitations.