Our first version of Consent Control autoblocking works using a portion of our TagControl functionality. To do this involves a few steps of our “Omni” tag.
- You deploy the tag on your site. Once the tag is on the site, we begin to observe records from real user data.
- With this data then you can begin to build a list of resources you want to be allowed to fire. Once this list is created you simply have Consent Control turned on UCP and it will begin to work together.
Consent Control its self doesn’t work as something separate from opt-out consent (CCPR) or Opt-In (GDPR) it works together. Depending on how your UCP notice is setup for one of the prior mentioned consent types will determine how it fires. In the case of GDPR/Opt-In it would block all non-essential tags from firing until consent has been given. For CCPE/Opt-Out it would allow everything to fire until someone has say opted out for filled out a Do Not Sell Request.
To answer you second question, that really entirely up to you. Having your notices setup through Consent Control has some significant advantages over the previous implementation. The biggest of those being Real Time Scanning. Having this functionality gives an up to date picture of what’s happening on your site. Without having to back into your Tag-Manager you simply approve a new tag and Consent Control takes care of the rest.
