Your banner buttons, your way, and PixelYourSite finally waits for consent.
Hey everyone 👋
This release gives you full control over your banner buttons, adds consent support for PixelYourSite, and closes several gaps where trackers could run before a visitor said yes. Let’s get into it.
What’s new
This release lets you change your banner buttons, adds support for PixelYourSite, and fixes several cases where tracking could start before a visitor said yes. Let’s get into it.
What’s new
Change your banner buttons in one place
Go to Banner > Content to reorder the buttons, hide the ones you don’t need, and write your own button text. The buttons for managing preferences and saying no always stay visible, so visitors can always opt out.
PixelYourSite now waits for consent
Its tracking stays off until the visitor says yes. Once they do, it starts right away on the same page.
See new versions on your dashboard
Your dashboard now tells you when a new version of SureCookie or SureCookie Pro is ready, with a link to update.
Choose who can manage SureCookie
Agencies can now limit who is allowed to change SureCookie settings on a site. Nothing changes unless you set it up. Your developer can do this for you.
Better than before
The default banner message is shorter. It fits phone screens better and helps your page speed score reflect your content instead of the banner. If you write your own message, nothing changes.
Fixed
- Visitors who had turned on a privacy setting in their browser to opt out of tracking could still be counted as saying yes. Their choice is now respected.
- Asking visitors for consent again didn’t fully clear their old choices. It now does, so nothing tracks them until they choose again.
- Google’s reCAPTCHA and Google Fonts could load before a visitor said yes. They now wait.
- Pages saved by caching plugins could sometimes apply the wrong Google privacy settings to visitors.
- HubSpot tracking wasn’t blocked for portals hosted in the EU.
- Microsoft Clarity wasn’t told when a visitor said yes, so it didn’t work properly.
- Rules for EU and EEA visitors didn’t apply in every country they cover.
- Scripts that rely on each other could start in the wrong order after consent, which could break features.
- Your cookie policy listed services your site doesn’t use.
- The banner could break on sites using W3 Total Cache.
- Screen readers didn’t always read out the button names correctly.
Before you update
If you use Google Consent Mode and have Google’s “I’m not a robot” check (reCAPTCHA) on login or checkout forms, test those forms once after updating. reCAPTCHA now waits until the visitor says yes, so the form may not work until they accept. You can allow it manually if you need to.
As always, support is one click away if anything feels off.