Shopify app · Meta Conversions API

Meta is running blind. And you don't even know.

Meta spends your money finding people like the ones it thinks bought. Dave fixes the plumbing so it sees who actually bought.

No spam. One email when it ships. · Install on Shopify: soon

Want the full reasoning? Read the deeper logic ↗

SHOPIFY DAVE META
01 / The problem

Here's how blind.

Safari and ad blockers kill the pixel. Since iOS 14, Meta loses most of the people who clicked your ad and can't tell which ones bought. So it bids on guesses.

What Meta sees

A click. No idea who.

What it should see
  • email · hashed✓
  • phone · hashed✓
  • event_id · paired✓
  • click · tied to the order✓

A person. Who bought.

02 / The catch

Meta's business is your spend, not your efficiency.

You're paying rent. The system is tuned to take as much as it can while giving you just enough success to keep coming back.

How the rent goes up

Blind data means higher bids, wider swarms, and repeat impressions on people who already scrolled past.

  • — It bids on lookalikes of guesses, so you pay for the wrong audience.
  • — It reads a stray tap as "high intent" and swarms them at premium prices.
  • — It re-shows the same ad to the same person. You pay twice.
03 / The fix

Fix the plumbing.

Browser and server, one event ID, real identity attached to unknown clicks. That's what Dave does. A few clicks in Shopify.

Sent Paired Withheld
Transparent

See every event

Every purchase, checkout and page view — where it came from, what fields it carried, whether Meta got it, and why not.

BROWSER SERVER blocker event_id
Resilient

Browser + server

Browser cookies get wiped in days and blockers drop pixels. Server-side events from your own pipeline do not — and both share one event ID so nothing is counted twice.

view cart checkout email
Enriched

Identity stitching

Once a shopper identifies at checkout, their earlier anonymous browsing is tied to them — first-party, consented, no fingerprinting. Meta finally learns whose browser it was.

04 / Two numbers

Watch these two. Ignore the rest.

Meta's dashboards are noise. Two numbers tell you whether it knows who's buying and whether it's wasting your money. The deeper logic ↗

Events Manager · Event Match Quality
↑6.5EMQ floor

Below 6.5, your pixel doesn't know who is buying.

Fix this first. Dave shows the score Meta gives you and the coverage you actually sent, so you know which side the gap is on.

Ads Manager · Frequency
↓1.7Frequency ceiling

Above 1.7, you're paying to re-show people who already swiped away.

Fresh, correctly matched buyers keep frequency down. That only happens when Meta gets real data to find them.

05 / The result

Meta finally sees who buys.

So it spends finding more of them, instead of swarming. Two scores, every event, every gap accounted for.

Before

A black box.

You don't know what data Meta is grabbing, when it's broken, or whether it's accurate. By design.

After

A transparent box.

Every event, where it came from, what it carried, whether Meta got it, and why not. Own your data plumbing.

admin.shopify.com/store/…/apps/dave-the-plumber

Overview

Updated 4 minutes ago
Purchase matching needs attention — Phone and external ID are missing from 38% of purchase events sent in the last 7 days. Meta may match fewer purchases to the people who made them.

At a glance

Last 7 days
  • Purchase matching Needs attention Phone and external ID missing from 38% of purchase events
  • Event delivery Healthy 1,284 events sent, paired on one event ID
  • Orders reaching Meta 19 withheld 412 of 431 orders forwarded, every gap accounted for
  • Server-side gateway Not connected Optional. Browser and webhook events are flowing without it
Event Match Quality · Purchase Measured by Meta
6.1/ 10
−0.4 vs previous 7 days
14 daily readings
Customer data coverage · Purchase Estimated by Dave
72%
of fields Meta can match on were present
  • Email94
  • Name88
  • Phone61
  • External ID40

Example data · not a live store

06 / Plans

Priced by orders. Nothing hidden.

Identity stitching from Starter, server-side gateway from Growth. At the cap, forwarding pauses; orders stay in Shopify.

Free

$0/mo

300 orders / mo

  • Pixel + Conversions API
  • Two-score overview
  • Identity stitching
  • Server-side gateway
Join the waitlist

Starter

$39/mo

1,500 orders / mo

  • Pixel + Conversions API
  • Two-score overview
  • Identity stitching
  • Server-side gateway
Join the waitlist

Scale

$249/mo

30,000 orders / mo

  • Pixel + Conversions API
  • Two-score overview
  • Identity stitching
  • Server-side gateway
Join the waitlist
Free tool

Scan your store for what ADA trolls sue over.

Serial accessibility lawsuits target the same handful of things: product images with no alt text, unlabeled search boxes, icon buttons with no name, low contrast, no accessibility statement. Our free scan checks up to five pages of your store and tells you exactly what to fix, in plain English, with the code.

  • Score out of 100, graded A–F
  • Plain-English fixes with copy-paste code
  • A ready-to-paste accessibility statement
Scan my store — free No account needed · not legal advice
07 / Get started

Stop spending more on ads and Meta running blind.

The Shopify App Store listing is not live yet. Leave your email and we will tell you the day it is.

Install on Shopify Soon

No spam. One email when it ships.