Shopify Customer Privacy

What it does. Calls Shopify's Customer Privacy API so Shopify's built-in tracking, and any app that reads consent through it, sees the visitor's choice.

Consent category. analytics and marketing.

How it works

Shopify takes all three flags in one call:

window.Shopify.customerPrivacy.setTrackingConsent({
  analytics: true,
  marketing: true,
  preferences: true
}, callback);

The bridge fills them from the resolved consent state on each update. analytics comes from analyticsStorage and marketing from adStorage.

One thing to know before you rely on it: preferences is currently set from the analytics value, not from a preferences category. If you use Shopify's preferences flag to gate anything meaningful, check that it's behaving the way you expect, because a visitor who accepts analytics and declines preferences will still be reported to Shopify as having allowed preferences.

Setup

On by default. Toggle it under Vendor Consent Signals on the banner's App Integrations page, then publish.

The API has to be present on the page for the call to land, which on Shopify means the customer privacy script Shopify injects. On a storefront where that script isn't loaded, the bridge has nothing to call.

Testing

Read the current state back from Shopify:

window.Shopify.customerPrivacy.currentVisitorConsent()

Make a choice in the banner and call it again. The returned flags should match what you chose, allowing for the preferences behaviour above.