Does your plugin support script blocking? (ex. Google Analytics )
-
I tested your plugin and it doesn’t seem to block scripts. The way i did it was through placing the script code to my header.php file. Is there a different way that actually works or is this not supported by your plugin?
-
I think this plug-in is somewhat misleading or at least missing some information.
On the Quantcast Choice FAQ it says:
Does Quantcast Choice block my vendor tags from firing on my site before consent is given?
No. Quantcast Choice is a piece of JavaScript tag that you will need to manage the sequencing of on your site similar to all other tags. From a compliance perspective, it’s recommended for the CMP to fire first, and all other vendor tags are held from firing until a user has made a choice. After a user has made a consent choice, then Quantcast Choice will share and transmit that consent to 3rd party vendors on the IAB Framework. Then those tags will fire based on the user’s consent decisions.No information is given about the mechanism of this plug-in. From my understanding the plug-in will generate the consent popup for you but not actually defer any scripts unless explicitly programmed.
Futhermore, I found this in technical implementation guide which raises more questions:
Determining Consent
Just like vendors, some publishers will need to wait for a consent signal before setting cookies or processing user personal data for one or more of the purposes they selected if they choose consent as their legal basis for one or more of the purposes.To do this, publishers will need to update their website code to look for the consent signal. This can be done using the getPublisherConsents command from the IAB framework JS API. More info can be found here in the IAB Europe Transparency and Consent Framework JS API Specification.
Executing Code after Consent Collection
In order to perform an operation when the UI is closed (indicating the user has made a new choice of consents), the __cmp operation to register a callback (specific to the Quantcast Choice CMP, not part of the IAB JS API standard) is as follows:__cmp('setConsentUiCallback', callback)The callback will be invoked (with no arguments) the next time the UI is closed which indicates the user has made a new consent choice. To invoke the callback every time the UI is shown, this operation will need to be made before each time the UI is brought up with
__cmp('displayConsentUi')My first impression of Quantum choice is that the solution will work out of the box without further configuration. I think it should be more clear that this plug-in doesn’t actually do anything except collecting the choice but the choice signal, without any actual effect on the loading of Google Analytics, Facebook Pixel etc.
The topic ‘Does your plugin support script blocking? (ex. Google Analytics )’ is closed to new replies.
