Problem When synchronisation is turned off for a tracking technology so the fields can be overridden locally, some fields (notably Expiry) stay non-editable. Saving then fails with a validation error that Expiry is required, even though a value is already shown. That blocks editing Category, Vendor, Platform, Privacy Portal URL and related fields for cookies, third-party requests and service workers. Requested improvement With synchronisation off, all overrideable fields should be editable and saveable without a false “required” error on Expiry (or similar locked fields).

Problem Organisations with multiple sites may stop receiving consent logs for a site (for example after a CSP or install issue) without noticing quickly. Requested improvement Optional alert when no consent logs arrive for a site during a configurable period, sent to a chosen email address.

Problem When a collaborator is invited to a Consent Studio domain, the invite often lands them on a login screen asking for email and password. Invited users who do not have an account yet do not understand that they must first use New to Consent Studio? create an account, create a password, and only then accept the pending invite. Context Partners hit this repeatedly while onboarding end customers. They end up coaching people through the create-account step manually. Requested improvement Make the invite / accept-invite path obvious for new users: a clear create-account route when no account exists, then accept the invite, without requiring partner hand-holding.

Shopify customers, report that the Consent Studio scanner is blocked from accessing their website. They are being shown an error message in the Consent Studio dashboard stating: "Site access blocked Our scanner cannot access your website. Please whitelist our IP addresses or disable security features that may be blocking our scanner." The customer is unable to whitelist the Consent Studio IP addresses (51.15.69.167, 51.15.75.157) due to Shopify's security settings. They propose an alternative solution involving a Shopify crawler signature for access.

Instead of only providing cross-subdomain consent, also allow root domains within a whitelisted group to share consent state with each other to prevent the amount of times a consent banner is shown.

We will introduce an edge to edge theme of our consent banner for customers to experiment with. It can either be on the left, right, top or bottom of the screen.

Optie om in Toestemmingsbanner v2 de knoppen op mobiel onder elkaar of naast elkaar te tonen.

Please can you automatically insert an onscreen message to viewers when content is not viewable on-screen due to blocked cookies. For example if an Embedded video uses tracking cookies, can you add a message (populated from the Translations section within the Admin control panel) to ask the visitor amend their cookie consent to view the content. The intention is that this will speed up deployment of the platform to reduce the time needed to manually check every single page for blocked/hidden content and reduce the number coding tweaks on the front end our devs need to make.

We will make it possible to serve your Consent Studio consent banner (Web CMP) and tag management container (Launcher) through your own path, increasing the chance of it being presented to your site’s visitors. Only current possibility: https://consent.studio/[domain]/banner.js New possibility: https://[domain]/lorem/ipsum.js This feature will be made available to Consent Studio Essential Plus (only purchasable through when using Consent Studio in collaboration with our of our Partners) and Consent Studio Professional.

As provided by one of our customers, the ARIA role should be improved for the banner v1 toggle for “Functional” consent in the Web CMP consent banner.