> ## Documentation Index
> Fetch the complete documentation index at: https://82616d6-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://82616d6-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://82616d6-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://82616d6-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Consent (/docs/concepts/consent)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 2271 · updated: 2026-11-16 -->
Related: [How Product Metrics works](/docs/concepts/how-it-works.md), [Conversion values](/docs/concepts/conversion-values.md), [Profit](/docs/concepts/profit.md), [New and returning customers](/docs/concepts/new-and-returning-customers.md), [Conversion actions and events](/docs/concepts/conversion-actions-and-events.md), [Server-side tracking](/docs/concepts/server-side-tracking.md)

> How Product Metrics reads your cookie banner as Consent Mode v2 signals, and what it sends to Google Ads, Meta and ChatGPT Ads with and without consent.

**Product Metrics follows the choice each visitor makes in your cookie banner. Consent starts denied, and getting through ad blockers never overrides it.**

The tracking script reads the banner as the four Consent Mode v2 signals and stores them with the visit. When the order is confirmed, those signals decide what may go to each channel. The rest of the pipeline is [How it works](/docs/concepts/how-it-works).



![A matrix of the visitor's consent choice against Google Ads, Meta and ChatGPT Ads. Everything allowed sends the full conversion everywhere. Ad user data without ad storage sends customer data without the ad click. Ad storage alone sends only the Google Ads order with the click. Marketing without analytics drops the custom events on Meta and ChatGPT Ads. Nothing allowed sends nothing.](/docs/_assets/cfe7b679758a0f358dde86b20b0a855c2a24208ca921ec164dc21283e4fcbdd0)

*Figure: What each consent choice lets through, per channel.*

## The four signals

| Signal               | Banner category | What it allows                                                                                                                                                                               |
| -------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `ad_user_data`       | Marketing       | Hashed customer data with the order; any Meta or ChatGPT Ads (OpenAI) event at all                                                                                                           |
| `ad_storage`         | Marketing       | The ad click: Google's gclid, gbraid or wbraid; Meta's `fbp` and `fbc`; ChatGPT Ads' `__oppref` and `__obref`                                                                                |
| `ad_personalization` | Marketing       | Adding the customer to Google Ads customer lists; without it, ChatGPT Ads events carry `opt_out: true`                                                                                       |
| `analytics_storage`  | Analytics       | The Google Ads profit, new and returning customer and LTV conversions, and the Product Metrics custom events on Meta (profit, new and returning, LTV) and ChatGPT Ads (revenue, profit, LTV) |

Each signal is `granted` or `denied`. Anything your banner doesn't set stays denied.

## With and without consent

| Visitor allowed              | Google Ads                                                                      | Meta                                                                 | ChatGPT Ads                                                                    |
| ---------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Everything                   | The order with hashed customer data and the ad click                            | `Purchase` and the custom events, with customer data and `fbp`/`fbc` | `order_created` and the custom events, with customer data and `oppref`/`obref` |
| Ad user data, not ad storage | The order with hashed customer data, no click                                   | Events with customer data, no `fbp`/`fbc`                            | Events with customer data, no `oppref`/`obref`                                 |
| Ad storage, not ad user data | The order with the click, no customer data                                      | Nothing                                                              | Nothing                                                                        |
| Marketing, not analytics     | **Product Metrics - Revenue** only, no profit, customer type or LTV conversions | `Purchase` only, no custom events                                    | `order_created` only, no custom events                                         |
| Nothing                      | Nothing                                                                         | Nothing                                                              | Nothing                                                                        |

```text
Visitor A   ad_user_data, ad_storage and analytics granted
  → Google Ads: order + hashed email + gclid
  → Meta: Purchase, PMOrderProfit, PMNewCustomer, …
          with hashed email, fbp, fbc
  → ChatGPT Ads: order_created, pm_order_profit, pm_revenue_ltv, …
            with hashed email, oppref
Visitor B   ad_storage granted only
  → Google Ads: order + gclid
  → Meta: nothing
  → ChatGPT Ads: nothing
```

Each Google Ads conversion also carries the visitor's ad user data and ad personalisation choices.

## Rules

1. **Denied until the banner says otherwise.** Before the visitor chooses, every signal is denied.
2. **The banner you choose is the one read.** If **Configure consent** names a banner your store doesn't show, Product Metrics can't read the choice and treats it as not given.
3. **Withdrawal wins.** If a visitor withdraws consent after checkout, their unsent conversions are dropped.
4. **Erasure wins.** After a privacy request erases a shopper's data, their unsent events are never sent.
5. **Customer lists need more.** A customer joins a Google Ads list only with ad user data and ad personalisation. Removals are always sent.
6. **Meta and ChatGPT Ads have no consent mode.** So nothing goes to Meta or ChatGPT Ads without ad user data.
7. **Profit needs analytics too.** Google Ads gets the profit, new and returning customer and LTV conversions only when the visitor allowed analytics and ad user data, as Meta's custom events do. Otherwise the order goes to **Product Metrics - Revenue** alone.

## Banners per platform

| Platform                                          | Banners Product Metrics reads                                                                                                                                     |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Shopify](/docs/platforms/shopify)                     | **Shopify Customer Privacy**, or OneTrust, Cookiebot, Usercentrics or Osano                                                                                       |
| [WooCommerce](/docs/platforms/woocommerce)             | OneTrust, Cookiebot, Usercentrics or Osano. Clear your full-page cache after changing it.                                                                         |
| [Magento](/docs/platforms/magento)                     | OneTrust, Cookiebot, Usercentrics or Osano, or your own banner through `ProductMetrics.setConsent()`. Magento's cookie restriction notice does not grant consent. |
| [Lightspeed](/docs/platforms/lightspeed)               | OneTrust, Cookiebot, Usercentrics or Osano                                                                                                                        |
| [Shopware](/docs/platforms/shopware)                   | Shopware's own cookie manager (leave **Not configured**), or OneTrust, Cookiebot, Usercentrics or Osano                                                           |
| [Any website (Cloudflare)](/docs/platforms/cloudflare) | OneTrust, Cookiebot, Usercentrics or Osano                                                                                                                        |

### Your own banner

With a banner Product Metrics doesn't read itself, pass every choice explicitly: once the script is ready, and again whenever the visitor changes it.

```js
await ProductMetrics.whenReady()
ProductMetrics.setConsent({
  analytics_storage: 'granted',
  ad_storage: 'denied',
  ad_user_data: 'granted',
  ad_personalization: 'denied',
})
```

All four keys are required, each `granted` or `denied`.

## Try it

Open **Tracking** and look under **Configure consent**: it names the banner your store's tracking reads, or **Not configured**. Choose the banner there to change it.

**Ask your assistant:** "Which consent banner does Product Metrics read on my store?"

## Where next

| If you need…                      | Go to                                                  |
| --------------------------------- | ------------------------------------------------------ |
| Set the banner step by step       | [Consent setup](/docs/using/consent)                        |
| What customer data is sent        | [Enhanced Conversions](/docs/features/enhanced-conversions) |
| Why ad blockers don't change this | [Server-side tracking](/docs/concepts/server-side-tracking) |
| Lists of your customers           | [Customer lists](/docs/features/customer-list)              |
