VWO
VWO runs experimentation and personalization code that uses cookies and often qualifies as non-essential. Load VWO after Intastellar Consents and only when consent allows the relevant purpose.
Prerequisites
- Quickstart.
- Map VWO to your banner’s marketing, statistics, or custom category consistently.
Google Tag Manager
- Install the VWO snippet via GTM Custom HTML (or VWO’s GTM instructions).
- Use a trigger that fires after consent for that purpose—e.g. custom event when the visitor accepts, or GTM consent checks if you use them with VWO.
- Keep the CMP tag on Consent Initialization — Google Tag Manager.
Async smart code
If VWO provides async loader code, ensure it still does not execute above the CMP in the document. Order in the initial HTML matters more than “async” for first paint races.
Verify
- VWO cookies / local storage should not appear as active for restricted users before accept.
- After accept, experiments and heatmaps behave as VWO expects.
Related
Last updated