Disabling JavaScript tracking

In some cases, it may be necessary to disable the ReSci tracking code on a page without having to remove the JavaScript tracking snippet. For example, you might do this if your site's privacy policy includes the ability for a user to opt-out of 3rd party tracking.

Important: Allowing users to disable tracking can have large impacts on your Cortex campaign performance.  Users who opt out cannot be tracked as they navigate and shop in your online store.  This means we cannot sort them by purchase intent, cannot track shopping cart contents, and cannot track their behavior to predict item preferences.

When implementing a user tracking opt out, ensure that the system is thoroughly tested and sends back the correct information for all opted-in users.

Opt-out of tracking for your site

The ReSci javascript library includes a window property that, when set to true, disables all tracking through cookies and 3rd party http requests to our servers.

To disable tracking, set the following window property to true:

window['rsci-disable-tracking'] = true;

This window property must be set before our JavaScript file is loaded, and it must be set on each page for which you want to disable tracking. If the property is not set or set to false then tracking works as usual.

How can the user opt out of tracking?

The client site is expected to display its own notification and management system to allow users to opt out of tracking. 

When a user chooses to opt out of tracking, set the following window property to true:

window['rsci-disable-tracking'] = true;

How does the user get confirmation they are no longer being tracked?

The client site is expected to display its own notification system to provide confirmation to the user.

For certainty, use browser developer tools to confirm that tracking is disabled by:

• Confirming that no calls to https://waves.retentionscience.com/wave are made after the page is loaded (instructions).
• Confirming that there are no cookies that begin with "rsci_" being stored in the browser.

How many users have opted out?  How can we report on this?

Once a user opts out, it's as if they have no more activity on the site.  We aren't able to differentiate them from a user that simply stopped using the site.  Opt-outs are not tracked or counted by ReSci.

What is the impact on specific cortex stages and models if a user stops being tracked (ie what doesn't work anymore?)

This affects all stages and models which rely on user actions.  A user who opts out of tracking appears inactive between their purchases.  

• Most Affected - Cart Abandon, Browse Abandon, Churn State Predictions, New+High/Low Intent
• Moderately Affected - New Arrivals, Item Back in Stock, Price Drop, Customer Future and Lifetime Value
• Not affected - Stages with hard-coded rules such as NTYB, Follow Up, and Smart Blast