[Feature request] Add before consent / after consent gestion

[SW-Vincent]

While managing consent is becoming a chalenge over time, it would be nice to have dedicated features such as :

• tagging variables as consent variables, these consent variables will then be declared within the tags as the tested consent variable for this tag ;
• tagging trigger as consent update trigger, this trigger will then be declared within the tags as the the ;
• within tag template, declaring what needs to be done before consent and what needs to be done after consent* ;
  Eventually, make the third point an option (ex : throught a checkbox)

*For the last point, it basically means that each tag will actually be x tags in one with one trigger and one trigger group :

• First tag (before consent) will trigger when the defined trigger is matched.
• Second tag -eventually more- (after consent) will trigger either when the default trigger is matched and the consent variable is "true" OR after the default trigger has been triggered if the consent trigger is matched and the consent variable is "true". It will have to be triggered once per default trigger, weither the consent trigger has been matched before or after them.

Note that for such a thing to be reliable for SPA, we'll need some data layer "reset" mechanic.

[snake14]

Hi @SW-Vincent . Thank you for taking the time to submit this enhancement request. I'm marking it to be reviewed by our Product team. Any additional information or clarification you can provide would be appreciated.

[SW-Vincent]

Hi,

Here is an exemple of how it might look on a custom HTML Tag :

Below the usual custom HTML tag definition, a CTA would allow to add a new section within the same tag :

Maybe this CTA should be after the trigger section ?

Anyways, the rest is pretty mutch the same that adding any custom HTML tag with slight differences as it requires :

• the HTML content ;
• consent triggers (although the consent will also be tested at default triggers), it would make sense to have advanced settings (such as "once per page", etc.) for consent triggers too
• The consent variable(s) and a matching value (or regex ?)
  

Note that it would make sense to be able to add as much consent sections as you want.

If you need some user case for a Matomo Tag, here is what would be wonderful :

• creating a Matomo Pageview tag, with a default parameter "require consent for heatmaps and session recordings", "require consent for e-commerce", "require consent for Youtube videos tracking" (note that such parameters don't exist at the moment) ;
• creating a tag to reactivate each consent, with a consent update trigger and a dedicated consent variable for each ;

In a nutshell, it would be pretty much like Google Consent Mode but better, as you can chose what is sent before and after consent freely and for any tag.