DocsOpen Henkan Chat
Connectors

Didomi

Connect Didomi with private API keys. Prerequisites, steps, example questions, consent notice audit against CNIL and Google Consent Mode, limits and troubleshooting.

Up to date with v1.5.4Updated 26 October 20262 min read

Henkan reads your Didomi consent notices and their live settings, and audits them against CNIL and Google requirements. It only reads: nothing changes in Didomi.

Before you start#

FieldWhere to find it
API key and API secretDidomi Console › your organization › Settings › Private API keys › create a key. Didomi generates the key and its secret together.
Organization ID (optional)Leave empty to use the first organization of these keys.

Connect#

Connecting Didomi with a private API key.
1
Name. Helps you recognise this connection.
2
Help text. Where to create the private API key in Didomi.
3
Test and save. Checks the key before storing it.
  1. Open Tools In the sidebar, select Tools, then select Didomi and Connect.
  2. Enter the key Paste the API key and API secret, and the Organization ID if needed.
  3. Select Test and save The key is checked, then stored encrypted.

What you can ask#

  • "Audit our consent notices: is refusing as easy as accepting? Are durations within CNIL guidance?"
  • "Is Google Consent Mode v2 enabled with denied defaults on the FR notice?"
  • "Which vendors use legitimate interest?"
  • "What did the last compliance scan find on maison-exemple.com?"

What Chat can and can't do#

ToolWhat it doesRead or writeAsks first?
FindFinds consent notices by name across your Didomi connections.ReadNo
List organizationsOrganizations these keys can read, with premium features.ReadNo
List notices, get noticeLive settings: platform, domains, refuse button, consent durations, Google Consent Mode, GPP, per-regulation settings, deployments.ReadNo
Audit noticesChecks every live notice: refuse as easy as accept, consent duration (CNIL: 6 months recommended, 13 maximum), Google Consent Mode v2 with denied defaults, disabled or never-deployed notices.ReadNo
List vendorsVendors with IAB TCF v2 id, purposes and hosts.ReadNo
Compliance reportsCompliance scans per website: score, trackers and vendors found, errors. Needs the compliance monitoring add-on.ReadNo
Dashboard linksLinks to your Didomi analytics dashboards.ReadNo

Limits and good to know#

  • Compliance scans need Didomi's compliance monitoring add-on.
  • Costs and who pays. Your Henkan plan covers the AI requests: each question counts towards your organisation's requests (see Usage and limits). Any API costs on Didomi's side fall under your contract with Didomi.

Troubleshooting#

Error or symptomFix
Didomi rejected the credentialsCreate a new private API key in the Console and connect again.
The wrong organization is usedEnter the Organization ID when you connect.
Compliance reports are emptyThe compliance monitoring add-on isn't enabled on your account.

Sources#