Facebook Pixel & Conversions API Setup
Send every real sale and lead to Meta (and Google) once, matched and proven with test orders, so the ads learn from real buyers.
She bought from your ad on her iPhone. Meta thinks it flopped. Overcome tracking limitations so the algorithm stops learning the wrong lesson.
30 minutes · Google Meet
Your Game Plan Starts With 30 Minutes
- Talk it through with the person who'd lead the work
- Nothing to prepare. No pitch, no slides.
- A written game plan follows, yours to keep
Pick a weekday time that works on the next page. The invite lands in your inbox right away.
Tired of Paying More for the Same Customers?
When the ads can't see your sales, they can't learn from them. Here's how that shows up, and what changes.
Each Sale From the Ads Keeps Getting Pricier
Third quarter in a row. Customers bought on iPhones and behind ad blockers. Meta never heard, so it filed some of your best ads under "didn't work."
"Feed" Meta's AI the Sales It's Been Missing
The Conversions API sends each sale from the server as well as the browser, so purchases hidden by iPhones and ad blockers still reach Meta.
Events Manager Calls Your Match Quality "OK." It Isn't.
The score sits in the middle, under a banner you keep dismissing. Many buyers look like strangers to Meta, and it can't learn much from strangers.
Help Meta Recognize Your Real Buyers
Every customer detail you're allowed to send goes over hashed, with your match score written down before and after.
CAPI Went On. Meta Had a Suspiciously Good Week.
Someone ticked a box in an app, and Meta's purchases jumped overnight. Not one extra box shipped. Meta learned from a week that never happened.
Count Every Sale Once, However It's Reported
Pixel and server share one event ID per sale, so Meta counts it once. Your next great-looking week is actually a great week.
Google Counts Every Form Fill as a Win. Even the Spam.
The spammer and the client who stayed for years. To Google, both are one "conversion." Your CRM knows the difference. Google never hears it.
Show the Ads Which Leads Became Clients
Qualified leads, booked calls and signed clients go from your CRM back to Google and Meta as conversions, so they find more like them.
Two Weeks, and Your Pixel Never Goes Dark
Your part: one conversation, a few minutes of logins and one walkthrough. Your current pixel keeps running the whole time.
- Days 1 to 2
Plan: What Each Platform Hears Today
What Meta and Google receive now, and your match scores, written down. If the browser tracking underneath isn't sound, you hear it now.
- Days 3 to 7
Build: Alongside What You Already Have
Conversions API, enhanced conversions, the CRM connection and a server if it pays. Consent choices carried through. Nothing switched off.
- Days 8 to 10
Verify: Watch a Test Order Land Once
Real test orders, refunded after. Done means GA4, Meta and Google within 5% of your store's orders. Selling leads? Every test lead traced.
- A Week Later
Read: Your Match Score Catches Up
Match scores take a few days to update. Once they do, your final before and after lands in your inbox.
What's Running in Your Accounts Two Weeks From Now
All of it inside your own accounts, handed over in plain English, with a recorded walkthrough for whoever runs the ads.
Pixel and Conversions API, Set Up Right
Sales, leads and checkout steps sent from the browser and the server, hashed, sharing one event ID. Counted once, matched to more buyers.
Google's Version, With the Same Care
Enhanced conversions send Google hashed customer details and the order number, so more buyers get matched and none get counted twice.
Your CRM, Talking Back to the Ads
Qualified leads, booked consults and signed clients sent back to Google and Meta, so the ads chase clients instead of form fills.
A Server, Only If It Earns Its Keep
Server-side Tag Manager in your own cloud account, when you feed several platforms or want control over what leaves the site.
Your Before and After, in Writing
What each platform received before and after, with your match scores, so you see the difference instead of taking it on faith.
Within 5%
Of your store's orders, on every platform, at handover
What "Done" Looks Like on Your Screen
A real test order goes through on your site and gets refunded straight after. You watch it land once in GA4, once in Meta, once in Google. Selling leads? A test lead gets traced from the form into your CRM and back to the ads.
He has a very in-depth knowledge of everything Google and data collection. He restored many issues with our tracking and made sure all was in sync.
Why Now
Ads Can't Learn From Buyers They Never See
Every day, a share of your buyers on iPhones and behind ad blockers goes unreported. The algorithms spend tomorrow's budget based on who they think bought today.
The good part: your "before" is in writing by day two, and the ads start hearing the missing sales in week two. Only a small handful of projects run at once, so start dates fill up.
The Details
What You Get, and When
The exact scope comes out of the 30-minute call, built around your tools and your team.
Delivery About 2 weeks
Get Your Game Plan
Meta Pixel and Conversions API, each sale counted onceQuestions, Answered
Anything else? Bring it to the 30 minutes.
Does this work for lead generation, or only online stores?
Both. Leads and booked calls go from your CRM back to Meta and Google as conversions, so the ads learn which leads turned into clients.
Phone calls count too, once they're tracked. If they aren't yet, that's part of the Measurement Foundation.
Is server-side tracking really needed, or is an app enough?
Sometimes an app is enough, and you'll hear that first. What matters is the setup underneath: counted once, matched well, hashed, consent respected.
A server earns its keep when you feed several platforms or want control over what leaves your site.
Will a server mean a new monthly bill?
Only if a server is worth it. It runs in your own cloud account, sized to your traffic, and you get the number before anything starts.
Everything runs in your own accounts.
The Conversions API is already switched on. Isn't that done?
Switched on isn't the same as set up right. Without the same event ID on both sides, Meta counts each sale twice.
If yours is already right, the day-two check shows it, in writing.
Should the tracking be fixed first?
If it's broken, yes. A server sends whatever your site tells it, so broken tracking goes out broken, just more reliably. The day-two check tells you which.
If it points to something bigger, the Tracking Audit is the place to start.
Find the Customers the Ads Are Missing
Thirty minutes, then a straight answer in writing: server or no server.
Everything stays yours. Only a small handful of clients at a time.