OneTrust + Shopify integration

What OneTrust is

OneTrust is a privacy and consent management platform. On a store it shows the cookie banner and records what each visitor agreed to, so analytics and marketing tags only run with consent.

How we would approach OneTrust with Shopify

A banner that shows is not the same as consent that works. We map each OneTrust category to Shopify's consent signals, then test every tag and pixel on the store with consent given, refused and not yet answered. Custom pixels and scripts outside the app store need their own handling, because they don't read Shopify's consent state automatically.

What the work involves

• Map OneTrust categories to Shopify's analytics, marketing and preferences signals
• Check Shopify's own pixels, app pixels and custom pixels against each consent state
• Cover checkout as well as the storefront
• A short test script your team can rerun after each new app or tag

Ways to connect OneTrust and Shopify

• Existing app

  OneTrust Consent Management (Shopify app)

  OneTrust's own app for existing OneTrust customers. You connect a OneTrust domain by its Domain ID and map OneTrust categories to Shopify's privacy signals. It lists checkout support. The app is free; OneTrust bills its platform separately.

• Custom build

  Consent bridge in the theme

  If the app can't be used, a small script can read OneTrust's consent state and pass it to Shopify with the Customer Privacy API. It has to update when the visitor changes their choice, not only on page load.

Where these projects go wrong

• Every category is mapped to "allowed" during setup and never re-tested, so opt-outs are ignored.
• Custom pixels added under Customer Events don't follow the app's mapping. OneTrust recommends reading its own consent cookie or JavaScript API for those.
• Consent works on the storefront but not at checkout.
• The app's only public review reported a Domain ID error. Test the install on a development theme before relying on it.

Questions

Does OneTrust work with Shopify checkout?

OneTrust's Shopify app lists checkout among the surfaces it works with. Test it on your own checkout, because a consent setup that only covers the storefront is a common gap.

How do we check that consent is really passed to Shopify?

Change your choice in the OneTrust banner, then check Shopify's consent state in the browser console. If it doesn't change, the mapping isn't working.

Do we need OneTrust, or is Shopify's own banner enough?

That depends on your markets and your legal advice. If you already run OneTrust across other sites, connecting it keeps one consent record. We don't give legal advice on what your banner must say.

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.