Skip to main content

Backlog

6

Under consideration

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

Edit tracking technology when synchronisation is off

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).

Feature Request

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.

Feature Request

Mogelijkheid om PDF-facturen mee te sturen in e-mail vanuit reseller program.

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

Integration with Klaviyo

Next up

1

Committed and queued

In Progress

4

Actively being built

Done

13

Recently shipped

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

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

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

Add Onlineafspraken.nl tracking technologies to database of known tracking technologies

Cookies starting with oa-*. Check https://onlineafspraken.nl. Thanks.

Feature Request

Make VAT number no longer mandatory for Partner Program enrolment in the UK

VAT number is still a mandatory field for UK resellers of Consent Studio when they get started with the reseller program, but this is not needed. We will adjust the self-billing to match the actual legal requirement from now on.

Feature Request

Make it possible to invalidate consent given before a certain date

When a major change is made to your consent banner, your tracking set-up and/or in any other way about how you collect PII from your customers, it might be desirable to invalidate existing consent before a certain date. We will create a new “Danger Zone” in het Consent Studio admin, located under domain management. Here, an option will be added that allows you to select a date in the past before which existing client-side records can be invalidated upon next visit.

Feature Request

Store Consent Log record timestamp client-side

Upon request and as part of our next generation consent banner (v2), we will now also store the Consent Log timestamp client-side. This will enable both ourselves as well as our customers to use it in the JS API.