Some of Your Orders Reach Meta but Never Show Up in GA4 — Here Is Why, and How Converlay Now Catches It

A shopper checks out. Converlay routes the order to Meta and Google Ads, and both platforms record the conversion. But GA4 never sees it. Nothing errored, nothing failed to send — the order simply never had analytics consent, so it was correctly withheld from the analytics destinations while still reaching the advertising ones. Multiply that across a store's order volume and you get two conversion counts that quietly stop agreeing with each other, with no obvious cause and no alert telling you it is happening.

Converlay v2.29.0 adds a Data Health Check rule that surfaces exactly this pattern — consent_mismatch — and ships three fixes in the same release that reduce how often it happens for reasons that have nothing to do with what your shopper actually chose.

Why Ad Consent and Analytics Consent Can Legitimately Disagree

Consent isn't one on/off switch. A shopper's cookie banner typically asks about advertising and analytics separately, and it is entirely normal for someone to accept one and decline the other — accepting personalized ads while opting out of being measured, or the reverse. When that happens, Converlay's consent resolution does exactly what it should: the order reaches destinations covered by the granted purpose and is withheld from destinations covered by the denied one.

That is correct behavior, not a bug. But it has a side effect merchants had no visibility into: an order recording ad consent while analytics is denied still reaches your ad platforms, yet can never be linked back to the storefront visit that produced it in GA4. The order looks delivered on your dashboard. The attribution loss doesn't show up until later, as ad-platform conversions that stop matching your analytics numbers — and by then there is nothing pointing you at consent as the cause.

What the New Rule Actually Flags

The Health Check now tracks a purchases_consent_mismatched aggregate and scores it against your total pixel purchase volume — pixel purchases on both sides of the ratio, so a webhook-heavy store's numbers aren't diluted below the threshold by orders the rule was never measuring. Two bands matter:

• Under 10%: stays silent. Some share of shoppers genuinely making different choices for ads and analytics is expected, and flagging it would just be noise.
• At or above 30%: escalates to a warning. A dominant share of your orders splitting this way usually means something in your consent setup — banner configuration, purpose mapping, CMP integration — is causing the split rather than shoppers choosing it.

When the rule fires, the copy explains the mechanism in merchant terms: the orders are still reaching your ad platforms, but attribution is weakening, rather than naming a root cause Converlay can't actually see from the data alone. It's translated across all eight supported locales, same as the rest of the Health Check.

Two Bugs That Were Manufacturing False Mismatches

A detection rule is only as useful as the data feeding it, so v2.29.0 also closes two gaps that were creating mismatches unrelated to anything a shopper actually chose.

Buyer consent lookups were failing silently. When an order webhook arrives, Converlay first tries to resolve the buyer's own captured pixel consent before falling back to a region default. That lookup hashes the buyer's email and phone to match them against consent already recorded from the storefront — but the hashing ran on the raw strings, so an address typed with different casing or spacing than the one Shopify sends hashed differently, and the match almost never succeeded. Nearly every order fell through to the region default instead of the shopper's real choice, which is exactly the kind of gap the new rule would otherwise have to explain away as "unknown." Email and phone are now normalized before hashing on both sides, so the buyer's actual consent resolves correctly far more often.

The pixel could stamp an order before consent had actually arrived. Some consent platforms — Cookiebot is one — push a visitor's choice into Shopify asynchronously, after the pixel has already booted. On an order confirmation page, that race is close: if the purchase event fires before the consent signal lands, Converlay records analytics as denied even though the shopper had, a moment later, consented. The pixel now waits up to one second for a delayed consent signal before sending the event — it never assumes consent, and the event always sends either way, but a visitor who did consent stops being miscounted because of page-load timing.

Together, those two fixes mean fewer orders land in the mismatch bucket for reasons that have nothing to do with what your shopper actually decided — so when the new rule does fire, it's telling you something worth looking at.

What You'll See on Your Dashboard

Nothing to configure. If your store's consent mismatch rate is under 10%, you won't see anything new — that's the expected background rate of shoppers making different choices for ads and analytics. If it's climbing toward or past 30%, the Health Check will surface it as a warning, and you'll have a concrete number to work from instead of a mystery gap between your ad platform dashboards and GA4.

Converlay connects your Shopify store to 26 destinations — including Meta, Google Analytics 4, TikTok, Pinterest, Klaviyo, and more — via server-side event forwarding, and the Data Health Check now watches for the gaps that consent choices create between them, not just the ones caused by a broken integration.

Install Converlay from the Shopify App Store and check your Health Check the next time your ad and analytics numbers don't quite line up.