09-18-2018 03:48 PM - edited 10-22-2018 04:12 PM
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.
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.
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.
The latest updates to the Explicit Consent Prompt include the following fixes:
noviewoption is enabled.
If you previously implemented a work-around for this scenario, you should test the new behavior and make adjustments as needed.
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.