Meta Conversions API for Shopify

No more missing Meta ad conversions.

iOS privacy and ad blockers are hiding 30-40% of your real conversions from Meta Ads Manager. Ordinary lights them back up — so the campaigns you wrote off come back into focus, your real ROAS finally shows, and your budget stops getting cut on ads that were quietly working all along.

Get started See all solutions

Under-reporting

The problem

Since iOS 14, the Meta browser pixel has been unable to record a growing share of your real conversions. Between Apple's Intelligent Tracking Prevention, ad blockers, and shoppers who decline cookie consent, the average Shopify store sees 30-40% under-reporting in Ads Manager. Your campaigns are working — the dashboard just can't see it. When conversions disappear, ROAS looks bad, and budget gets cut on campaigns that are actually profitable.

The fix

What changes in Ads Manager

Even when shoppers block, refuse, or browse in ways the Meta pixel can't catch, your purchases still reach Meta — accurately, and without doubling up against the conversions the pixel did record. Campaigns that looked dead come back into focus. Budget decisions start matching reality. The "complete the Conversions API connection" warning in your Meta Events Manager goes green and stays green.

The workflow

How it works

  1. Step 1

    Connect your Meta ad account

    Sign in with Meta. Pick the ad account you want connected. That's it — no code, no tag manager, no developer needed.

  2. Step 2

    Every order reaches Meta — even the hidden ones

    Every Shopify purchase counts towards Meta's optimization, no matter what blocked or hid the pixel for that shopper. Customer identifiers are hashed before they leave; conversions Meta already saw from the pixel stay single-counted.

  3. Step 3

    See restored ROAS in Ads Manager

    Campaigns that were dark come back into focus. Event Match Quality scores in Meta climb. Budget decisions start matching reality.

Transparency

What data is sent to Meta

We believe merchants — and their customers — deserve to know exactly what leaves the server. Per purchase event, Ordinary transmits:

Sent

  • Email, hashed with SHA-256
  • Phone, hashed with SHA-256 (if present)
  • First and last name, hashed with SHA-256 (if present)
  • Purchase amount and currency
  • Event timestamp
  • Event ID (for deduplication against the browser pixel)

Never sent

  • Raw (unhashed) personally identifiable information
  • Payment card, bank, or other financial account data
  • IP addresses beyond what Meta already observes from its pixel
  • Line items, product details, or SKUs

Your data, your account

Privacy

Events are forwarded only to the merchant's own Meta ad account — never pooled, never resold. Merchants can disable the integration at any time in Settings → Integrations → Meta, and individual customers can request removal via our data deletion process . Full details in the Privacy Policy .

Go deeper

Once your conversions are honest, the analytics get honest too

CAPI fixes what Meta sees. The next question is what to do with that clearer picture — which creative is pulling weight, which placements are bleeding, which audiences are buying, which campaigns build a real customer base. That all lives on the Meta ad analytics page.

See what's actually working in your Meta ads

Ready to light up the conversions you're missing?

Connect your Meta account in under five minutes.

Get started