Fix for tracking calls in Explicit Consent Prompt

Employee Emeritus

We recently identified some issues with how the Explicit Consent Prompt was handling tracking calls under certain conditions. This led to scenarios where extra tracking calls were being made or tracking calls were being permitted prior to consent. The latest release of this feature has addressed these issues.

Who Is Affected

Pages Using noview Option

If you are using the utag override option, noview, then you might have experienced extra tracking calls. The explicit consent prompt was ignoring the noview option and triggering tracking calls based on the consent status. Since a page that uses the noview option typically triggers a tracking call based on other criteria, this often led to duplicate tracking calls.

Event Tracking Prior to Consent

If your page tracks additional events to the initial page load, then these might have been allowed even prior to acquiring consent. If the explicit consent prompt was actively displayed to the visitor, tracking calls that occurred at the same time were incorrectly allowed.

How It Works Now

The latest updates to the Explicit Consent Prompt include the following fixes:

  • Explicit Consent Prompt will not trigger a tracking call if the noview option is enabled.

    If you previously implemented a work-around for this scenario, you should test the new behavior and make adjustments as needed.

  • Tracking calls that occur while the consent prompt is active will be queued and handled appropriately after consent is received.

These changes will be reflected upon your next publish. We always recommend that you publish to Dev or QA first to test your changes before promoting to Prod.

0 Kudos