Pixel

The reason our numbers are different from Meta's.

Consequential's own pixel collects server-side, stitches identity across sessions and devices, and reconciles every platform-claimed conversion against your actual orders. The customer graph it builds stays in your account.

Installs on Shopify without a developer. SOC-2 certified.

Reconciliation · last 30 daysIllustrative
Meta
3.68x claimed0.66x actual
Google Ads
4.12x claimed2.87x actual
TikTok
2.90x claimed1.44x actual

Return on ad spend as claimed by each platform, compared with the figure measured against actual orders. Every claimed conversion checked against an order in Shopify.

Server-side collectionSOC-2 certifiedInstalls on Shopify without a developerBuilt on Blotout EdgeTag, running across 5,000+ omni-channel brands

Every ad platform grades its own homework.

The browser pixel is the grading instrument, it sits on the platform's side of the desk, and signal is lost on the way: blocked, consent-declined, cross-device, or stranded between a click and an order placed four days later.

What's going wrong

Events never arrive

Blocked by ad blockers, declined at the consent banner, or lost between a click on one device and an order placed four days later on another. The platform optimizes on what reached it, not on what happened.

What's going wrong

The grader owns the instrument

The browser pixel sits on the platform's side of the desk. It reports the platform's version of your performance, on the platform's attribution window, and there is no second opinion in the room.

What's going wrong

Tracking breaks silently

A theme update, a checkout change, a competing app install. Nothing errors. The numbers just quietly stop being right, and the first symptom is a CAC line that drifts for three weeks.

Claimed is not delivered. The distance between the two is where your budget decisions are actually being made, and nothing in the platform's own reporting will ever show it to you.

Collect it yourself. Check it against the orders.

Pixel does two things the category treats as one. It recovers the signal the browser loses, and then it checks what the platforms claim about that signal against the orders in your Shopify admin.

Now you can see the difference between claimed and delivered, because we collect the events ourselves and reconcile them against your order record, so the number you optimize against is the number that actually sold.

That second half is the part nobody else does. Everyone in this category recovers signal and sends it back to the ad platforms. Recovering signal makes the platform's report better. It does not make the platform's report true.

What it collects, and where it sends it.

Built on Blotout EdgeTag, a first-party data infrastructure running across 5,000+ omni-channel brands, with order reconciliation layered on top.

Server-side collection

Events leave your domain, not the browser's ad-blocker. The collection point is infrastructure you control rather than a script the platform ships you.

Meta CAPI+

Conversions API forwarding built for event match quality, so Meta optimizes on signal it would otherwise never receive.

No-code GA4

EdgeTag handles the GA4 wiring. No tag manager surgery, no developer ticket.

Order reconciliation

Every platform-claimed conversion is checked against an actual order in Shopify, not against a modelled one and not against the platform's own attribution window.

Identity graph

Sessions and channels resolved to a single customer record, so a first touch and an order four days later belong to the same person.

Retention metrics

Repeat rate, active buyers and cohort behavior computed on the same reconciled record as everything else.

Standing rules are the memory you can see. This is the rest of it.

Every event, every stitched identity, every order it reconciles accumulates into one record of how your customers actually behave: which channels start a relationship rather than claim it, which cohorts come back, what a customer is worth by the source that found them.

That record is why the system's answers get better on your brand specifically. A competitor starting today starts from zero on you.

One brand, one record.

It is never merged into a shared graph, and it is never used to improve anything that serves another brand.

Memory that only reports is a database.

Back to the platforms

Better signal out

Recovered events forwarded through Meta CAPI+ with match quality as the objective, so the platforms optimize on more of what actually happened.

Into the funnel view

Conversion and retention

Funnel performance, drop-off and retention computed on reconciled events rather than on platform-reported ones.

Up

Feeds NorthStar

The same record is what the targets, pacing and reports are computed against, so the number you act on and the number you're held to come from one source.

Why not the native pixel, or a server-side GTM container you build yourself?

This is the fair question and almost nobody in this category answers it on the page. Three honest reasons.

The input

Changing the transport doesn't fix the signal

A native pixel and a DIY server container send the same degraded browser-side event to a different address. Moving where it's sent from doesn't recover what the browser never captured. The recovery has to happen at collection.

The maintenance

A container is a thing you own forever

Every event depends on the container config staying correct through theme changes, checkout updates and app installs. It's not the build that costs you, it's the quarter where it silently drifts and nobody notices.

The second opinion

Neither one reconciles

A DIY setup can get events to Meta. It cannot tell you whether Meta's claim about those events matches the orders in Shopify. That comparison is the entire reason this page exists.

How it works

Step 1

Install the Shopify app

No developer, no tag manager work. Collection starts on the next session.

Step 2

Connect your channels

Meta, Google Ads, TikTok, GA4, Klaviyo. Events start forwarding with the identifiers each one needs to match.

Step 3

Run alongside what you have

Keep your existing tracking during the overlap. Events are deduplicated on a shared event ID, so nothing is counted twice while both are live.

Step 4

Compare and cut over

Watch claimed against delivered side by side for a period, then turn the old setup off once you can see the difference for yourself.

How it's priced.

Pixel ships inside the Professional plan, $1,499/mo, plus $1 per 5,000 events. An event is a single tracked action forwarded to a single channel, so your monthly volume is roughly your pageviews multiplied by the channels you forward to.

ItemProfessional
Server-side pixelIncluded
Meta CAPI+ event match quality improvementIncluded
EdgeTag with no-code GA4Included
Identity graphIncluded
Retention metricsIncluded
Events$1 per 5,000
Above 10M events / monthVolume discounts apply

Volume discounts apply above 10M events a month. If you're forwarding at that scale, the rate is a conversation rather than a line on a page.

See the full pricing page →

What we don't do with it.

Never pooled

Your data is never merged into a shared graph. One brand, one record, yours.

Never trained on for someone else

Your record is not used to improve anything that serves another brand.

SOC-2 certified

Independently audited controls on how the data is stored, accessed and handled.

Install today. Reconciliation starts on the next session.

Install the Shopify app, no developer and no tag manager work. Connect your ad accounts. Your first reconciled report follows. We find $10K+ in recoverable spend in your first week, or you don't pay.

Frequently Asked Questions

No. It runs alongside GA4 and your existing pixels. Most brands keep both for a period and compare, which is the conversation that ends the argument.
Not if they share an event ID, which is how the platforms deduplicate. Events sent server-side carry the same identifier as the browser event they correspond to, so Meta and Google collapse the pair rather than counting both. If you leave Shopify's native Meta integration running as well, that's a third source and worth turning off once you've finished comparing.
Week one your numbers will look different, because you're seeing events the browser pixel was never capturing. That's the point, and it is also the week the change is hardest to read. Run both setups in parallel, compare claimed against delivered at the end of the period, then cut over. Anyone who tells you the transition is invisible is selling you something.
It carries the part that matters for measurement: server-side collection, an identity graph, and reconciliation against actual orders. It differs from a standalone CDP in one way, which is that the same record is what your targets and forecasts are computed against, so the number you act on and the number you're held to can't disagree.
Those recover signal and send it back to the ad platforms. So do we. The difference is what happens next: the recovered signal is reconciled against your orders and becomes the basis for a target you're pacing against, not just a better input to the platform's own reporting.
Because the collection layer is a solved problem, and we'd rather run on infrastructure with 5,000+ brands of production hardening behind it than rebuild it. What isn't solved, and what isn't buyable anywhere else, is reconciling what that infrastructure collects against your actual orders and holding a target against the result. That's the part we built.

Built to Replace Reactivity

If you're tired of reacting to revenue drops after the fact, Consequential gives you the edge.