Didomi + Shopify integration

What Didomi is

Didomi is a consent management platform used to show cookie notices and record visitors' consent choices, often across several sites and markets.

How we would approach Didomi with Shopify

Didomi records consent by purpose; Shopify reads consent through three signals: analytics, marketing and preferences. We map one to the other, then test every tag on the store with consent given, refused and not yet answered, in each market where the notice behaves differently.

What the work involves

• Map Didomi purposes and vendors to Shopify's consent signals
• Check that Shopify pixels, app pixels and custom pixels respect each choice
• Confirm the behaviour in markets where the notice is not shown
• A repeatable test for new apps and tags

Ways to connect Didomi and Shopify

• Built in

  Didomi's Shopify integration (beta)

  Didomi documents a Shopify integration, currently labelled beta, that maps the purposes in your Didomi notice to Shopify's consent categories. IAB purposes are mapped by default.

• Custom build

  Customer Privacy API bridge

  Where the integration doesn't fit, a theme script can pass Didomi's consent state to Shopify with the Customer Privacy API and update it when the visitor changes their choice.

Where these projects go wrong

• Default purpose mapping is accepted without checking what each tag on the store actually needs.
• Tags added as custom pixels or in the theme run before consent is known.
• The notice is excluded in some regions, but tracking there isn't checked.
• A Content Security Policy blocks the requests the Customer Privacy API makes to Shopify.

Questions

Is Didomi's Shopify integration production-ready?

Didomi labels it beta in its documentation. We'd test it on a development theme with your real tags before switching it on.

Which consent categories does Shopify use?

Shopify's Customer Privacy API takes analytics, marketing and preferences when consent is set. Your Didomi purposes have to be mapped onto those.

Can you advise on what our notice must say?

No. That is a legal question for your counsel. We make sure the choices visitors make are applied on the store.

Before we scope the work

• Which data or customer journey needs to connect, and which system owns it?
• What access, plan features or API permissions are available?
• Does an existing connector cover the requirement, including failures and updates?
• Who will maintain the connection, and how will you know it is working?

Send your current setup and one real example of the flow you need. We'll tell you whether it can be done and what it would take.