Meta Events Manager settings: what to check on a Shopify store

Open your dataset in Events Manager, go to Settings, and check nine things. The four that matter most are advanced matching (should be fully on), first-party cookies (on), automatic code-less event tracking (off if you already send proper events), and the domain allow list (should exist at all).

Almost every store we look at has the first two right, because Shopify's Facebook channel sets them up. Almost none has the last two right, because nothing sets them up and nothing complains.

Settings tab of the dataset, top to bottom. This takes about five minutes once and rarely needs revisiting.

"Track events automatically without code" lets Meta infer events from your page metadata and button text - it will decide, on its own, that a button reading Add to basket is an AddToCart. It exists for stores with no proper instrumentation, where an inferred event is better than nothing.

On a Shopify store whose channel already sends real standard events, it is not better than nothing. It is a second source of the same events, inferred rather than measured, with no shared event id - so Meta cannot deduplicate it against the real one. You get inflated upper-funnel counts and a bidding model optimising against them.

It defaults to on. Nothing warns you. If your AddToCart count has always looked flattering relative to your actual cart adds, check this first.

With no allow list, your dataset accepts events from any domain that references your pixel id. Events Manager will eventually surface this as a prompt to confirm domains that recently started sending data, and the list usually contains more entries than people expect.

On a Shopify store the legitimate ones typically include your storefront domain, your myshopify.com domain, and two that look wrong but are not: shop.app and native_document, which are the Shop app's in-app browser. Add those rather than blocking them, or you will lose real Shop app conversions.

Anything you do not recognise is worth understanding before you allow it. A pixel id is not a secret - it is visible in your page source - so an unfamiliar domain sending events is a real possibility, not a theoretical one.

The Actions tab is where Meta reports quality problems, and two of them are worth treating as real rather than as advisory noise.

"Server sending expired fbclid value in fbc parameter" means something is sending a click id older than the 90 days Meta still attributes. It is almost always a sender taking the click id from a shopper's FIRST visit rather than the one that converted - a long consideration window turns a recent order into an expired click. The fix belongs in the sender: drop the parameter past 90 days rather than sending it, since the event still carries every other match key and an expired click id buys no attribution while costing dataset quality.

A low rate of deduplication means your browser and server events are not collapsing into one. That number is the single best early warning that two tools are both sending, and it moves before your reported conversions look obviously wrong.

Vibel reads the dataset's own quality signals and compares reported conversions against the Shopify order ledger, so a gap between what a platform claims and what actually sold shows up as a number rather than a suspicion.

It does not change these settings for you. They live in your Meta account, they affect data you are responsible for, and several of them are judgment calls about what you are willing to share - so they stay a decision you make, with the list above to make it quickly.