Some tools are intuitive enough to update your privacy policy for you as and when you add or amend scripts that reference cookies. In any case, it’s important to be aware that any changes to cookies being placed on users’ browsers, you will need to update your policies and notices to reflect this.
3. Enable Tracking & Consent Javascript API
This is a crucial step to ensure Account Engagement can integrate with your cookie consent tool. It’s a simple checkbox that you need to tick.
Pay attention to the settings surrounding the featurecayman islands phone number though, as you can align these settings with your privacy policy. Take note of:
When you delete visitor records that do not convert.
Types of cookies placed from your first party domain i.e. will you still place third-party cookies?
Retroactively recording first touch after an opt-in is a good feature, I recommend enabling this for better lead source data.
The max. duration of your cookies
Screenshot of Account Engagement cookie settings
4. Customise the MCAE tracking code as needed
One step that a lot of teams seem to miss is customisation of the MCAE tracking code. To use a cookie consent tool, the original tracking code becomes primitive and you’ll need to update it as per the documentation.
See the Tracking & Consent API documentation here.
The documentation is really good and provides you with a menu of snippets so you can customise your tracking code to exactly how you need it.
5. Test, test, test!
It should go without saying, but I’ll say it anyway. Unless you know what you are doing, you should do all of the above in a testing environment. Keep everything siloed in a safe environment because you do not want to be non-compliant!
Testing is a critical part of this process, simply because there are lots of moving parts when it comes to cookie consent. There’s the cookie consent tool itself with all of the other code it has to manage, likely Google Tag Manager and then of course MCAE.
I’ve seen lots of mistakes from companies when it comes to cookie consent. Here are the greatest hits:
The cookie consent banner doesn’t add the MCAE tracking when you accept all.
The cookie consent banner appears as well as the MCAE banner (2 x banners).
The cookie consent banner is branded exactly like the website and sits in the bottom right of the page without blocking scrolling, effectively making it invisible.
Cross-domain problems - no consistency across domains and tracking issues.
Without any action whatsoever, automatically opting people into tracking (non-compliant!).
If all is done correctly, you should see the pi_opt_in set to ‘true’.
- Board index
- All times are UTC
- Delete cookies
- Contact us