Your Meta Pixel
is leaking conversions.
We fix it in 4 days.
Apple's iOS 17 and iOS 18 changed how the Meta Pixel works — and most sites haven't caught up. If your audit score is below 85, you're losing 30-70% of attribution and paying Meta higher CPAs than you should. We rebuild the full stack — server-side CAPI, eventID matching, Advanced Matching, fbclid capture, Consent Mode v2 — for one flat fee.
We ran it on
ourselves first.
Foreground.agency was scoring 28/100 in February 2026 — no Pixel, no domain verification, no CAPI, no eventID dedup, no Consent Mode. We rebuilt the stack and the same audit returns 100/100 today.
Don't take our word for it — run the auditor on foreground.agency yourself. Same audit, same 10 fixes, on your site next.
- ✕Meta Pixel not installed
- ✕No domain verification
- ✕No Advanced Matching
- ✕No eventID deduplication
- ✕No Consent Mode v2
- ✕No fbclid first-party capture
- ✓Pixel + Advanced Matching wired
- ✓Domain verified in MBM
- ✓eventID dedup at fire-time
- ✓Cookiebot Consent Mode v2
- ✓fbclid captured server-side at landing
- ✓Apple Privacy Manifest reviewed
The browser Pixel
is broken by design.
Apple iOS 17 (2023): Link Tracking Protection strips fbclid from URLs in Mail, Messages, and Safari Private. Conversions you paid for stop attributing to ads.
Apple iOS 18 (2024): Hide My Email rotates email aliases per visit, breaking email-based Advanced Matching. Match rates collapse for logged-in flows.
The fix: server-side. Conversions API mirrors browser events from your server, captures fbclid before iOS can strip it, sends hashed external_id as a stable identifier. Meta dedupes against the browser Pixel using eventID. Get it right and you recover 30-50% of lost attribution. Get it wrong and you double-count every conversion.
Most agencies don't fix this because most agencies don't know how. The work is well-documented in Meta's developer docs — but you need PHP fluency, a server access token, and the discipline to test every event end-to-end. That's what we do.
10 fixes,
one flat fee.
Same checklist the free CAPI Auditor runs against — only this time we do the fixing.
Pixel installation + firing
Audit and fix the Meta Pixel install. Verify PageView, ViewContent, AddToCart, Lead, and Purchase events fire on the right pages with the right parameters.
Domain verification
Add the facebook-domain-verification meta tag and complete verification in Meta Business Manager. Without this, Meta drops all iOS 14+ events.
Advanced Matching wired
Turn on Automatic Advanced Matching or hand-wire it. Meta's own data shows EMQ from 5 → 8.5 cuts CPA ~18%.
Server-side CAPI
Build the Conversions API endpoint that mirrors browser events server-side. Recovers ~30% of conversions iOS 17/18 blocks at the browser layer.
eventID deduplication
Generate a unique ID per event and pass it to both the Pixel and the CAPI call. Without this, every conversion logs twice.
fbclid first-party capture
Catch the fbclid query param server-side at landing and set the _fbc cookie before iOS strips it on the next page hop. The deterministic-attribution layer.
external_id for iOS 18 HME
Add stable hashed user_id to Advanced Matching. The only field that survives iOS 18 Hide My Email aliasing.
Consent Mode v2
Wire a GDPR-compliant cookie banner with Consent Mode v2. EU/UK visitors firing Pixel without consent is a real compliance risk.
Test Events validation
Run live test events through Events Manager → Test Events tab. Every conversion event verified end-to-end before handoff.
Documentation
You get a one-page brief: what was broken, what we fixed, how to verify it stays green. So your next agency can't break it.
Day-by-day,
nothing hidden.
- Day 0
You book a call
Free 20-minute intro. We look at your current setup, agree on scope, you pay the $497.
- Day 1
Audit + access
You give us access to WP admin, Meta Business Manager, and your hosting panel. We run our full 12-check audit and confirm the gap list.
- Day 2
Build
CAPI endpoint deployed, eventID matching wired, Advanced Matching turned on, fbclid capture in place, Consent Mode v2 connected.
- Day 3
Test
Live test events through Events Manager. Verify EMQ climbs in real-time. Fix anything that doesn't.
- Day 4
Handoff
Documentation delivered. Score re-run via the audit. Green padlock on every check we promised.
One price.
One scope.
We've done this for so many clients we know exactly what it takes. No surprises, no hourly creep.
Full Meta Pixel + Conversions API setup. Delivered in 4 business days. 30-day warranty.
- ✓ All 10 fixes above
- ✓ Live test event validation in Events Manager
- ✓ One-page documentation brief on handoff
- ✓ 30-day warranty — anything we fix that breaks, we re-fix free
- ✓ Audit re-run via the free plugin to verify green
Common
questions.
What if my site is not on WordPress?
+
We work with Shopify, Webflow, custom PHP, Next.js, and Magento. The Pixel + CAPI fixes are the same regardless of CMS — only the implementation surface changes. Price stays $497 flat.
Why a flat fee?
+
Because the work is well-scoped and we've done it a hundred times. Hourly billing rewards slow consultants. We'd rather charge for the result.
What's NOT included?
+
Building you a new theme, redesigning your funnel, writing ad creative, or fixing things outside the Meta tracking stack. If we find issues outside our scope during the audit, we tell you — we don't silently expand the bill.
Do I get ongoing maintenance?
+
Not as part of the $497. You get a 30-day warranty: if anything we fixed breaks, we fix it again free. After that, ongoing monitoring is a separate retainer ($199/mo) or you handle it yourself with our free WordPress plugin.
How do I know if my Pixel is actually broken?
+
Run the audit on /tools/meta-capi-auditor first — free, no signup. If your score is below 65, you almost certainly have iOS 17/18 attribution loss. We'll quote against the gap list it produces.
Can I do this myself?
+
Yes. The free WordPress plugin shows the full DIY steps for every failing check. Most of the easy fixes you can handle in an afternoon. The hard ones (server-side CAPI endpoint, eventID dedupe, fbclid capture) require PHP + a Meta access token + a few hours of careful work. We charge $497 because that's what 4 days of senior dev time costs.
Stop paying Meta
for lost conversions.
Not sure if you need it? Run the free CAPI Auditor first. If your score is below 65, the math pays for itself in the first week of recovered attribution.