Consent tracking: why some events don't reach Meta and how Restricted mode works
Overview
When a shopper declines marketing cookies in your store's cookie banner, consent policy blocks the browser pixel for that session. Browser events from that session — mainly Add to cart and Checkout — are never sent to Meta. This is not a tracking error. By default, Omega Facebook Pixel follows your shoppers' consent choices — browser events from sessions where consent was declined are not sent to Meta.
Meanwhile, Purchase is always fully tracked because it's matched from your Shopify orders, not from the browser. Your revenue data is not affected — only the top of your funnel appears lower than it really is.
Omega Facebook Pixel helps you in two ways:
- It shows you exactly how many events couldn't be sent, at which funnel step, and in which markets — through an alert on your dashboard and the Consent coverage report.
- It gives you a choice — Restricted mode (Scale plan) — to keep sending those events through the server, if you decide to.
The consent alert on your dashboard
When at least one event is blocked by consent in the date range you're viewing, an alert appears inside the Add to cart / Checkout / Purchase block:
A few things to know about this number:
- It counts all blocked events for the date range and pixel you've selected, and updates when you change filters.
- It explains why Add to cart and Checkout are lower than you'd expect. Purchase is not part of this number — Purchase is always complete.
- It's a report, not a promise that these events can be brought back.
The alert gives you two paths:
- View report — opens the Consent coverage tab for the full breakdown.
- Go to settings — takes you to the Consent settings, where Restricted mode lives.
If you don't see the alert: no events were blocked in the period you're viewing, or your store hasn't collected consent data yet. In both cases there's nothing to fix. If your store sells in consent-required markets and you still see no data after a while, contact support and we'll check it for you.
The Consent coverage report
Where to find it: Tracking analytics in the left menu → the Consent coverage tab.
The date range picker, timezone, and Refresh button sit on the tab row. The date range and timezone apply to all three Tracking analytics tabs; Refresh reloads only the tab you're on.
The report answers three questions, in order:
1. Report metrics
Three summary cards at the top:
Card | What it tells you |
|---|---|
Purchase fully tracked | Your revenue data is not affected — Purchase is matched from Shopify orders |
Missing from Meta | Total events that couldn't be sent, with their share of all Add to cart and Checkout events |
Funnel visibility | How much of your funnel Meta can actually see |
The Missing from Meta number always matches the alert on your dashboard for the same date range. |
2. Which funnel steps are affected?
The funnel chart splits each step into two parts: what reached Meta and what didn't. You can read both numbers for every step directly — no math needed. The Purchase row is always complete, with a note explaining why it's different from the rows above.
Note: the "would have been sent" portion for declined sessions is an estimate, not a direct measurement — the report labels it as such.
3. Which markets are driving it?
The consent rate table lists your countries by traffic, highest first — the markets with the most visitors matter most. Markets with a low consent rate are highlighted, and a summary line names the specific markets pulling your rate down.
Low consent rates in the EU, the UK, and some other regions reflect the law in those markets (shoppers must actively opt in before they can be tracked). It doesn't mean anything is wrong with your store.
When no events were blocked in the period, the report shows a clean state confirming every event reached Meta — no empty charts, no rows of zeros.
Restricted mode (Scale plan)
Before you enable it
Restricted mode requires Scale plan. It keeps sending Add to cart and Checkout events from shoppers who declined, using your store data, through the server. These events carry fewer details than browser events — so you get more funnel data, not the full picture.
The restricted mode is off by default and only changes anything when you choose to turn it on. Whether sending events from shoppers who declined fits the consent rules in your markets (such as GDPR) and Meta's Business Tools terms depends on where you sell and how your consent setup works. Omega can't make that call for you — you are responsible for having a legal basis for these events if you enable it. If you're unsure, check with your legal advisor first.
How to turn it on
- Go to Settings → Consent.
- Turn on the Restricted mode switch.
- A confirmation dialog, Before you turn this on, explains what the app will do and what you're responsible for. Read it, then select I understand, turn on. Selecting Cancel (or closing the dialog) leaves the switch off — nothing changes.
- Once enabled, Restricted mode applies to all shoppers who declined, in every market.
You can turn it off at any time by switching it back off — no confirmation needed. You can turn it off at any time by switching it back off — no confirmation needed. The app goes back to its default behavior: Add to cart and Checkout events from shoppers who declined are no longer sent.
FAQ
Am I losing orders?
No. Purchase is recorded from your Shopify orders, so it's always complete regardless of cookie choices. Only the funnel data sent to Meta (Add to cart, Checkout) is affected.
Will Restricted mode bring back all the missing data?
No. Server events carry fewer details than browser events. Restricted mode gives you more funnel data, not the full picture you'd have if every shopper accepted cookies.
Why is my consent rate so low in some countries?
In the EU, the UK, and some other regions, the law requires shoppers to actively opt in before they can be tracked, so consent rates there are much lower than in markets like the US. That's a market characteristic, not a setup problem.
I don't see the alert, and the report says everything reached Meta — is that normal?
Yes. It means no events were blocked in the period you're viewing (or your store has no consent data yet). There's nothing you need to do.
Is it legal to turn on Restricted mode?
That depends on where you sell and how your consent setup works. Omega can't answer that for you — consider it carefully and consult your legal advisor if you're unsure.
How do I keep my tracking aligned with consent?
Leave Restricted mode off — that's the default. If you'd like help understanding how the app handles consent in your store, contact our support team.
Disclaimer: This article is for general information only and isn't legal advice. For questions about your store's compliance obligations, consult your legal advisor.
Updated on: 05/10/2026
Thank you!