Third-party and first-party tracking

Some browsers use mechanisms that disable third-party tracking scripts and cookies. This disables Synerise tracking.

To avoid this, you must serve the Synerise tracking tools from your own sub-domain. The Synerise Customer Success & Implementation (CSI) team delivers a modified tracking script that uses the new domain.

Configuring Synerise as first-party tracking

  1. In your hosting, create a sub-domain for Synerise tracking, for example api.example.com
  2. Configure a CNAME DNS entry for the created sub-domain:
    NAME                    TYPE   VALUE
    --------------------------------------------------
    api.example.com.        CNAME  web.snrbox.com.
    Note: After creating a DNS entry, you may need to wait 24-72 hours before it becomes active.
  3. Contact CSI and provide the sub-domain name.
    CSI delivers a a JS SDK script that uses the new sub-domain.
  4. Optional: If you want to use your own SSL certificate, deliver the public key to CSI.
    The certificate must be in X.509 standard, stored in a .pem file.
    Important: When you use your own certificate, it is your responsibility to monitor its expiration time and re-generate it.
  5. Begin using the modified JS SDK script. See Getting started.
    Result: the tracking domain changes from web.snrbox.com to your sub-domain. Third-party tracking blockers do not affect Synerise tracking.
😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker