Shopify
How to configure Shopify at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service, Support marketing analytics, Customise online ads
Overview
This guide explains how to implement different privacy configurations for the tracking that Shopify itself controls on a storefront (Shopify analytics, pixels, audiences and checkout) and how to reflect them in the Consenter Manager. Shop hosting, cart and checkout functions are strictly necessary and are out of scope.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Shopify-managed tracking surfaces on the storefront and checkout. Third-party apps and pixels (e.g. Meta, Google) need their own entries.
What the service does in this scope. The Customer Privacy API applies consent decisions to Shopify-managed surfaces such as pixels, audiences and checkout, with the purposes Preferences, Analytics and Marketing. A CMP sets them with window.Shopify.customerPrivacy.setTrackingConsent({...}). Shopify advises never reading or modifying Shopify cookies directly and links to its full cookie list.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Consenter passes Analytics and Marketing choices to the Customer Privacy API; both stay false until consent. |
| Configuration B — Higher risk | No consent signal passed; Shopify analytics and marketing surfaces run on Shopify's regional defaults. |
⚠ Recommendation. Merchants report that some Shopify analytics cookies still appear before consent when the default consent status is passed incorrectly. Test your storefront after setup and have your DPO review any cookies set before consent.
Step 1 — Configure Shopify
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service; Support marketing analytics; Customise online ads | Improve the service; Support marketing analytics; Customise online ads |
| 2 | Consent signal | Customer Privacy API, setTrackingConsent | Analytics / Marketing / Preferences set from Consenter; false until consent | Not called |
| 3 | Checkout | Customer Privacy API in checkout UI extensions | Same signal applied in checkout | Not applied |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Check Shopify's DPA and sub-processor list for the contracting entity and hosting locations; list the United States where US providers are involved.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service, Support marketing analytics, Customise online ads | Improve the service, Support marketing analytics, Customise online ads |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Browsing and interaction data, Device identifiers, Device characteristics, e-commerce Activity, Aggregated site statistics, Privacy choices | Browsing and interaction data, Device identifiers, Device characteristics, e-commerce Activity, Aggregated site statistics |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | Group based (behaviour) | Group based (behaviour) |
| Maximum storage duration | Per Shopify cookie list | Per Shopify cookie list |
| Processing location | Per Shopify DPA; United States possible (CLOUD Act) | Per Shopify DPA; United States possible (CLOUD Act) |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on