Set the waiting period for the "no consents recorded" alert yourself
Problem Consent Studio Monitoring decides per domain how long to wait (between 2 and 30 days) before showing the "No consents recorded recently" recommendation. Some organisations want to set this period themselves. Request A setting per domain where you can choose the waiting period before this alert is triggered. Follow-up to Alert when a site stops receiving consent logs.
Choose the email address for the "no consents recorded" alert
Problem The "No consents recorded recently" recommendation is emailed to every collaborator on a domain. Organisations want this alert to go to one specific address, for example a team mailbox, without adding extra collaborators. Request A setting where you can choose which email address (or addresses) receive this alert. Follow-up to Alert when a site stops receiving consent logs.
Limit an AI connection (MCP) to specific domains
Let users choose which domains an AI connection (MCP) can access, instead of giving it access to every domain on their account. Today a connection made under Personal settings > AI Apps applies to the whole user account. This would make it possible to try the AI connection on a test domain first, without giving it access to production domains, and to keep a connection limited to the domains it is actually needed for.
Split consent statistics by device (mobile, tablet, desktop)
Show the Web CMP consent statistics per device type (mobile, tablet and desktop), so you can see whether visitors on mobile accept or reject more or less often than visitors on desktop. This would help agencies and site owners compare acceptance rates per device in the dashboard and in reports, without exporting the data and splitting it themselves.
Clearer invite onboarding: create account then accept invite
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.
Consent Banner v2: Stretched Theme
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.
First-Party Delivery for Web CMP and Launcher
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.