Solution · Meta Conversions API

No more missing Meta ad conversions.

iOS privacy and ad blockers stripped 30-40% of your purchase conversions out of Meta Ads Manager. Ordinary sends them back — server-side, privacy-preserving, in real time.

Get started See all solutions

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.

How Ordinary fixes it

Ordinary forwards every Shopify purchase event server-to-server to Meta using the Conversions API (CAPI), matched back to the original ad click through a hashed customer identifier. Browser-side pixel blocked? The server-side event still fires. iOS user on a network that strips tracking? The server-side event still fires. Events are deduplicated against the pixel using a shared event ID, so there's no double-counting — only the conversions the pixel missed get added back.

How it works

  1. Step 1

    Connect your Meta ad account

    One-click OAuth. Pick the ad account and pixel you want events forwarded to. No code, no tag manager, no developer.

  2. Step 2

    Ordinary forwards every purchase

    Every Shopify order fires a server-side Purchase event to Meta within minutes. Hashed identifiers only. Deduplicated against your pixel.

  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.

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

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 .

Ready to light up the conversions you're missing?

Connect your Meta account in under five minutes.

Get started