> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/technical-integration-guides/shopify-plugin-consent-management-explained.md).

# Shopify Plugin Consent Management Explained

impact.com’s [Shopify plugin](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/e-commerce/integrate-with-shopify) manages tracking and customer consent together:

* **Better privacy compliance** — Stay compliant with evolving privacy standards and respect customer consent.
* **Reliable rewards tracking** — Conversions from your loyalty/cashback partners are always captured.
* **Visibility into lost conversions** — See the effect of customers declining consent in impact.com reporting.
* **Quick to enable** — No need to re-integrate your Shopify store with impact.com; just update a setting.

Make sure your Shopify settings are configured correctly to avoid gaps in tracking. See the [*Configure your Shopify Customer Privacy settings*](#configure-your-shopify-customer-privacy-settings) section below.

{% hint style="success" %}
**Note:** If you’re using impact.com’s Shopify plugin, do not enable [Consent Mode](/brand/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/ensure-gdpr-compliance-using-consent-mode.md) as the two are not yet compatible.
{% endhint %}

## How it works

impact.com’s Shopify consent management is configured to honor the consent signals set up in your Shopify store — it doesn’t set consent rules of its own. The impact.com Shopify Web Pixel detects consent status by checking your store’s `customerPrivacyStatus.marketingAllowed` value (`true` or `false`) to decide whether to fire tracking flows.

### When tracking happens

Conversion tracking only happens when one of the following conditions is met:

* A customer gives consent to be tracked by accepting the privacy/cookie pop-up on your site.
* A customer lands on your Shopify store after opening a link from a cashback or loyalty partner’s site — in this case, consent is already understood from their participation in the referral.
  * To ensure tracking continues in this scenario, the `im_rewards=1` parameter must be included in your landing page URL when customers are referred by your cashback or loyalty partners. Contact your CSM or [Support](https://app.impact.com/support/portal.ihtml) for help setting this up correctly, or see [Track Cashback & Loyalty Traffic with Shopify](/brand/what-would-you-like-to-learn-about/technical-integration-guides/track-cashback-and-loyalty-traffic-with-shopify.md) for more information.

### When the Page Load API fires

Whether the Page Load API fires depends on your store’s Customer Privacy settings and your page load default setting:

* If `customerPrivacyStatus.marketingAllowed` is `true`, the Page Load API fires.
* Depending on your settings, it may fire immediately on landing, or only after the customer grants consent.

## What the Conversion API sends when consent is denied

If a customer denies consent, personally identifiable information (PII) is stripped from the conversion request before it’s sent to impact.com. `ClickId` and `CustomProfileId` are not removed, but they won't show any values if they weren’t already captured before consent was denied.

*Omitted (returned as `null` and removed from the request):*

* `CustomerEmail` (SHA1 hash)
* `CustomerEmailSHA256`
* `CustomerId`
* `IpAddress` (client IP)
* `FirstPartyCookie`

*Still sent to impact.com:*

* `OrderId`
* `ClickId` (if already stored before consent was withdrawn, or passed via URL parameter)
* Order details (`CurrencyCode`, `ItemSku`, `ItemSubtotal`, `ItemQuantity`, `ItemCategory`)
* `OrderPromoCode`
* `IntegrationSource`
* `CampaignId` / `ActionTrackerId`

## Configure your Shopify Customer Privacy settings

1. In your Shopify store, in the bottom-left corner, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FG7Zr5cOHUYjH8vUdZvaB%2Fcog-solid.svg?alt=media\&token=b522fb12-36b9-49e6-8a9e-f07a2859acda) **\[Settings].**
2. From the left navigation menu, select **Customer privacy**.
3. Select **Privacy policy** to ensure you have a privacy policy.
   * A privacy policy must be published before the cookie banner and data sharing opt-out page will work correctly.
4. Both **Cookie banner** and **Data sharing opt out page** have their own **Use automated settings** toggle, under *Regions and content* on each page:
   1. If **Use automated settings** is ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggled on]**  (on by default for new stores), Shopify keeps both pages aligned with its current recommendations, and handles the EEA opt-in / US opt-out split for you, without you having to reason about it region by region.
5. To require opt-in in all regions instead of following Shopify's automated logic, complete the following steps:
   1. Select **Cookie banner** and  ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FACIoqj1Ayhx8QzL9aqYB%2Ftoggle-off-solid%20\(1\).svg?alt=media\&token=a85366cd-4b70-41a6-83df-319f89597ede) **\[Toggle off]** **Use automated settings**. Don't clear the region lists on this page if you're running a third-party consent management platform (CMP) and assume they only govern Shopify's own banner. These lists control which consent regime applies to everything reading the Customer Privacy API, including impact.com.
   2. Select **Data sharing opt out page** and  ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FACIoqj1Ayhx8QzL9aqYB%2Ftoggle-off-solid%20\(1\).svg?alt=media\&token=a85366cd-4b70-41a6-83df-319f89597ede) **\[Toggle off]** **Use automated settings**. Global Privacy Control (GPC) is only honored in regions where this page is configured. Skipping it means no GPC enforcement in that region.
      1. Enabling it manually (if it isn't already automated) requires 3 staff permissions:
         1. *Store settings: Manage settings*
            1. *Online store: Blog posts and pages*
            2. *Content: Menus*

{% hint style="success" %}
**Note:** If you're using a third-party CMP instead of Shopify's original cookie banner, confirm with the third-party vendor that it calls Shopify's `setTrackingConsent` API. A banner that renders its own UI but never calls this API leaves the Customer Privacy API reporting default values — and impact.com reads those default values.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/technical-integration-guides/shopify-plugin-consent-management-explained.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
