Journeys and GDPR

In order to help our customers comply with GDPR, and other laws that restrict data collection from certain users, we’ve updated our Web SDK with a Do Not Track mode.

This way, if a user indicates that they want to remain private on your website, or if you otherwise determine that a particular user should not be tracked, you can continue to make use of the Branch Web SDK (e.g. for creating Branch links) while not tracking that user. This setting can also be enabled across all users for a particular link, or across your Branch links.

If you enable that mode, you can still display some Journeys to your users. Whether or not a Journey will display for users in Do Not Track mode depends on the targeting criteria you’ve defined for that Journey. If the Journey uses any of the following audience filters, it will not display for users in Do Not Track mode. Otherwise, the Journey will display.

  • Has completed event
  • Has visited web
  • Has visited the app
  • Has clicked on email
  • Has clicked on ad
  • Has the app installed

If a Journey does display for a user in Do Not Track mode, any analytics related to the Journey’s display or the user’s interactions with that Journey will not be published in the Branch dashboard.

Updated 2 months ago

Journeys and GDPR


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.