Migrate to Didomi Consent String (DCS)

Note: Consent notices created after June 17th, 2025 will have the Didomi Consent String (DCS) enabled by default (i.e. didomi_dcs will be utilized to store end-user consent). Previously created message will need to migrate to the Didomi Consent String (DCS) no later than June 2026. After this date, Didomi will enforce the Didomi Consent String (DCS) on all consent notices and fully deprecate support for the didomi_token format.

The Didomi Consent String (DCS) is a compact and modern consent string format that is designed to offer full flexibility in representing an end-user's privacy choices. It is fully supported on both web and mobile platforms includes all of Didomi SDKs for websites, iOS, and Android applications.

The Didomi Consent String (DCS) is stored in didomi_dcs and replaces the deprecated didomi_token which was typically stored in a browser's cookies or local storage. In this article, we will cover how to manually upgrade a consent notice so that it leverages the Didomi Consent String (DCS)

Please contact the Didomi support team if your organization wishes to bulk migrate all of your consent notices to the Didomi Consent String (DCS).

From your Didomi console, click Consent Notices on the left-hand panel and select a consent notice from the list.

Select Customization and then click Cookies & storage on the subsequent page.

Navigate to Didomi Consent String panel and enable the checkbox.

Before publishing a migrated consent notice, please ensure that your organization have satisfied the following:

• If your organization's website or app accessed the deprecated didomi_token in JSON format that it is updated to handle the binary format of didomi_dcs . Click here for more information.

• If your organization is integrated with third-party vendors that expect the didomi_token you may need to coordinate format updates with these partners

Continue publishing your migrated consent notice when finished.