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.
Facilitate cross-domain consent sharing
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.
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.