If you’re building a custom template for a consent management platform (or really any script that should define consent status), there are new template APIs available for you. If you’re not looking to build custom templates, you can skip to the next chapter. The built-in trigger that’s automatically available in all containers is called Consent Initialization - All Pages. In other words, if you are using a consent management platform and you want to run some code (perhaps their own custom template) that establishes the default consent state for the five different consent types, this is the correct trigger type to use. This means that it’s good for, as the name implies, establishing the default consent state of the new consent types, for example (see below). It is programmatically generated to be the very first trigger that can fire on any given page. Consent InitializationĬonsent Initialization is a trigger that fires before any other trigger in the container. If you have an asynchronous call to fetch consent state, for example, then it’s possible that even when firing the tag with the Consent Initialization trigger, it completes only after some other tags have already started firing on later triggers. Note! These triggers can’t really handle asynchronous requests. The tag will only fire if all the listed consent types have the granted state. When you check this option, a small table appears, and you can add any of the five consent types into the table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |