Skip to main content

Backlog

5

Under consideration

Feature Request

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.

Feature Request

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.

Feature Request

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.

Feature Request

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.

Feature Request

Integration with Klaviyo

Next up

1

Committed and queued

In Progress

2

Actively being built

Done

22

Recently shipped

Feature Request

Shopify scanner blocked: consider supporting signatures for access

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.

Feature Request

Offer more yearly plans

By popular demand, we will start offering yearly plans also for the generally available plans listed below: Consent Studio Essential Partnered Monthly Consent Studio Professional Consent Studio Professional Partnered Monthly

Feature Request

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.

Feature Request

Transparent User Consent Log on Banner

I want a way to configure the banner to transparently show the user's own consent log directly to them. This is important because a privacy-focused developer suggested that without this, there may be GDPR violations in Germany.

Feature Request

Improve toggle attributes for agentic browsing

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.

Feature Request

Monitoring: indicate on which page a tracking technology has been found

Feature Request

An Automatic - This content has been blocked message

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.

Feature Request

Notify when a Consent Log export is complete

How much time an export takes may vary depending on the workload that the platform has to process at a given moment; It would be useful for a customer to be notified pro-actively when an export is complete, per e-mail, so they do not need to check manually for progress updates.

Feature Request

Consent Banner v2

We are working on a new variant of the Consent Studio Web CMP consent banner. This major update will include: In-banner consent log information: as suggested per https://improve.consent.studio/p/transparent-user-consent-log-on-banner Themes: switch between themes in your consent banner Performance: a smaller banner loading profile and better core web vitals scores Various improvements and customer feedback implementations This update will create breaking changes. Therefore, we will keep existing customers on the legacy banner system by default. They will be allowed to access the new banner by switching from the Web CMP settings dashboard. New customers will fall under the new regime by default.

Feature Request

Allow non-Latin characters in the Privacy Policy URL

The Privacy Policy URL field under Web CMP > Translations rejects addresses that contain non-Latin characters, such as Japanese or Cyrillic paths (for example /jp/プライバシーポリシー/). Customers currently have to use a relative path or a percent-encoded URL as a workaround. The field should accept these addresses as typed.