> ## Documentation Index
> Fetch the complete documentation index at: https://6f524b4-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://6f524b4-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://6f524b4-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://6f524b4-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Choose your consent banner (/docs/using/consent)

<!-- agent-signals: reading_time_min: 3 · est_tokens: 1553 · updated: 2026-11-16 -->
Related: [Start your Product Metrics subscription](/docs/using/billing.md), [Check tracking works](/docs/using/check-tracking.md), [Create conversion actions and custom conversions](/docs/using/conversion-actions.md), [Add your additional costs](/docs/using/costs.md), [Create a workspace](/docs/using/create-a-workspace.md), [Connect Merchant Center](/docs/using/merchant-center.md)

> Tell Product Metrics which cookie banner your store shows, so tracking follows each visitor's choice.

Product Metrics' storefront script reads the visitor's choice from **one consent banner** you name, per store. Name the wrong one, or leave it unset on a store that shows a banner, and Product Metrics can't read the choice and treats it as not given.

The choice itself is made in the app: an assistant can read it back, not change it.

## Prerequisites

* A [connected store](/docs/using/overview) that is live: the setting unlocks once the store is.
* Write access to Tracking (editor or admin): see [Before you start](/docs/using/overview).

## Set it up with AI



Paste the prompt into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "Check which consent banner Product Metrics follows on my store. Ask me which banner my store shows, and tell me exactly what to choose in Tracking → Configure consent."

**Claude Code or Codex:** "Check which consent banner Product Metrics follows on each of my stores, and tell me what to choose in Tracking → Configure consent for the banner each store shows. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first)."

## In the app

### 1. Open Configure consent

Open **Tracking**. Under **Complete your tracking setup**, open **Configure consent**.



![The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.](/docs/_assets/eb2d6e767cb722a4f9fc28ca607791b9b73c69ea9e416f3e8d76cb286dec18d6)

*Figure: Configure consent: choose the banner your store shows visitors.*

### 2. Choose the banner

Choose the banner your store shows: **Shopify Customer Privacy**, **OneTrust**, **Cookiebot**, **Usercentrics** or **Osano**. **Not configured** means none of these.

| Platform                              | Choose                                                                                                                               |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| [Shopify](/docs/platforms/shopify)         | **Shopify Customer Privacy**, unless your store shows one of the four other banners                                                  |
| [WooCommerce](/docs/platforms/woocommerce) | Your banner. After changing it, clear any full-page cache on your site                                                               |
| [Magento](/docs/platforms/magento)         | Your banner. Magento's cookie restriction notice does not count. Another banner needs a developer: see [Magento](/docs/platforms/magento) |
| [Lightspeed](/docs/platforms/lightspeed)   | Your banner                                                                                                                          |
| [Shopware](/docs/platforms/shopware)       | **Not configured** to use Shopware's own cookie manager, or your banner if it is one of the four                                     |
| [Cloudflare](/docs/platforms/cloudflare)   | Your banner                                                                                                                          |

You should see **Configure consent** name the banner your store shows.

## What each choice lets through

| Visitor allowed                   | Google Ads                                | Meta                                            | Customer lists            |
| --------------------------------- | ----------------------------------------- | ----------------------------------------------- | ------------------------- |
| Nothing                           | Order sent without customer data or click | Nothing sent                                    | Not added                 |
| Ad user data                      | Order with hashed customer data           | Events sent (custom events also need analytics) | Not added                 |
| Ad user data + ad storage         | Order with customer data and the ad click | Events plus Meta's browser IDs                  |                           |
| Ad user data + ad personalisation |                                           |                                                 | Added to Google Ads lists |

* A visitor who withdraws consent after checkout: the order isn't sent.
* Meta and ChatGPT Ads have no consent mode, so nothing goes to them without marketing consent (ad user data).
* After a privacy request erases a shopper's data, their unsent events are never sent.

### ChatGPT Ads

For ChatGPT Ads, Product Metrics applies the choice per piece of data:

| Visitor allowed          | What OpenAI gets                                                                                     |
| ------------------------ | ---------------------------------------------------------------------------------------------------- |
| Ad user data (marketing) | The event at all, with hashed customer data, IP address and user agent. Without it, nothing is sent. |
| Analytics storage        | Also needed for the revenue, profit and LTV events                                                   |
| Ad storage               | OpenAI's click references. Without it, neither cookie is written.                                    |
| Ad personalisation       | Without it, the event is sent marked as opted out, so OpenAI doesn't use it for personalisation      |

## Where next

* [Consent](/docs/concepts/consent): the concept
* [Check tracking works](/docs/using/check-tracking)
* [Google Ads](/docs/channels/google-ads) and [Meta](/docs/channels/meta)
* [Overview](/docs/using/overview)

Developers: read the chosen banner with the [CLI](/docs/cli/commands#stores-and-tracking) or the [API](/docs/api/stores-and-tracking/tracking-get-configuration), and set it with `productmetrics tracking update-installation-features --cmp-adapter …` ([API](/docs/api/stores-and-tracking/tracking-update-installation-features)).
