Short answer: Meta flagged a healthcare client's site as a health business and blocked the URL based custom conversion every Ad Set optimized to. We replaced it with a custom event with a neutral name, sent from the server through the Conversions API with hashed contact info. Then cost per lead looked like it doubled. The order log showed why: the developer only sent orders that had a Meta click ID, so Meta was hearing about a fraction of the leads. Sending every order fixed the reporting.
Client name changed. Everything else is what happened.
Northline Medical helps patients get medical equipment covered through their insurance. Patients fill out a short form, Northline handles the paperwork with the insurance company, and the device ships. Meta ads drive most of those form submissions. For two years the account ran on a simple setup: a Meta pixel on the site and a custom conversion that counted anyone who landed on the thank you page. Every Ad Set optimized to it. Cost per lead was steady and the client was scaling into new states.
Then Meta decided the site was a health business.
What Meta changed
In 2024 Meta started classifying data sources into categories. If your site looks like health care, Meta restricts what it will accept from your pixel. It strips URLs, blocks custom parameters, and on the stricter tier blocks standard events like Lead and Contact outright. It also blocks custom conversions built on URL rules, because a thank you page address can reveal something about a person’s health.
Northline’s notice came with a 30 day countdown. The custom conversion every Ad Set depended on would stop counting on a set date. After that, Meta would have no idea when a lead happened, which means it couldn’t optimize, couldn’t report, and couldn’t learn who to show the ads to.
Meta’s reasoning is legal, not technical. It got sued for receiving health data through pixels on hospital sites and it doesn’t want that data anymore. The restriction is on the business, not the pixel ID. Creating a fresh pixel doesn’t help. We checked.
What we tried first, and why it was wrong
Our first plan was to switch the Ad Sets to the standard Lead event. Lead is a Meta native event, not a URL rule, and on most restricted accounts it still works. We wrote the developer brief, the client’s dev built it, and the first server events landed.
Meta dropped them. On this account Lead and Contact were both blocked by category. That cost us two days.
The fix: a custom event Meta had never seen
The way through was a custom event with a neutral name. Meta can’t block an event for being health related if the name says nothing about health. We called it OrderSubmit. The dev’s system fires it to Meta’s Conversions API every time a real order is created, with the customer’s email, phone, first name, last name and zip, each scrambled with SHA-256 so Meta can match the order to a person without ever receiving the raw data. No URL path. No form fields. No insurance information. Nothing about the order except that it happened and who it happened to.
That’s the part non technical people miss. Meta doesn’t want your customer’s medical details. It does want the scrambled email and phone, because that’s how it figures out which ad click led to the order. Those are two completely different kinds of data. The first stays on your server forever. The second is what makes optimization work.
The part that took four days
The build itself was one event name in one payload. What ate the time was that nobody could see what the developer was sending. Attempt one went to an old pixel ID. Attempt two was named Lead and got blocked. Attempt three had a space in the event name. Attempt four was named correctly, Meta said received, and still nothing showed up.
That one turned out to be the key. On restricted accounts, new custom events don’t go live. They sit in a screen in Events Manager called Event Statuses, under Action Required, marked Blocked by Meta, until someone on the advertiser side clicks confirm. Every one of the dev’s test events had landed. They were waiting on a checkbox.
We confirmed OrderSubmit, the dev resent one order, and it counted within minutes. Match quality started at 6.9 out of 10 and reached 8.3 once IP, last name and zip were added. The old Lead event had been sitting at 4.7.
Then cost per lead doubled anyway
We duplicated every active Ad Set, pointed the copies at OrderSubmit, paused the originals, and watched reported cost per lead roughly double.
Some of that was expected. Every Ad Set was back in learning at reduced spend. But the number didn’t come down as the feed cleaned up. Email coverage went from 48% to 100%. Delivery went from a day late to real time. Match quality hit its best ever. Cost per lead stayed high.
So we asked for the one thing Meta can’t give you: the client’s own order log. One row per order, with the date and the landing URL. Every click from a Meta ad arrives with an fbclid in the URL, so you can count Meta sourced orders per day without depending on what Meta managed to credit.
What the order log showed
Over fourteen days the store took about 2,300 orders. Only 22% of them had an fbclid in the landing URL. And Meta had received almost exactly that many OrderSubmits.
The developer was only sending Meta the orders where the person clicked an ad and landed directly on the form. Everyone who clicked an ad, went to the main site first, and then filled out the form had no fbclid on the form page, so they were filtered out before the event ever left the client’s server. Everyone who saw an ad and came back the next day, same thing. Meta was crediting 94% of what it received. The matching was fine. It was being starved.
Under the old setup none of this mattered. The thank you page fired for every order and Meta matched people with its own cookie. Nobody was deciding which orders Meta got to hear about.
Rerun the math with the full order count and the picture flips. Give Meta credit for 80% of orders and cost per lead is about a quarter of what Ads Manager showed. Give it credit for only half and it’s still back to the pre restriction number. The ads hadn’t broken. The reporting had.
The fix for that
Send every order. No filter on the click ID. Include fbc when the URL has one and leave it out when it doesn’t. Meta already knows who clicked and who saw the ad. It takes the hashed email, finds the person, sees they clicked three days ago, and credits it. The click ID is a nice to have. The email is what connects the order to the click.
What to take from this
If you run ads for anything Meta might consider health, assume the restriction is coming. Get off URL based custom conversions now. Build a custom event with a bland name, send it from the server with hashed contact info, and confirm it in Events Manager.
Then check two things most people never check. First, that the developer is sending every order, not just the ones with a Meta click ID in the URL. Second, that you have a count of orders per day from the client’s own system, so when Meta’s number moves you can tell whether the business moved or the reporting did.
And when the developer says the event was sent and you can’t find it, open the Test Events tab before you open a new ticket.
FAQ
Why did Meta restrict the pixel?Meta classifies some sites as health businesses and then limits the data it accepts from them, including URLs and URL based custom conversions, because those can reveal something about a person's health.
What replaced the custom conversion?A custom event with a neutral name, sent from the server through the Conversions API with hashed contact info, then confirmed in Events Manager.
Why did cost per lead look like it doubled?The developer only sent orders that had a Meta click ID in the URL. Meta never heard about the rest, so reported leads dropped while real leads didn't.
Do I need the fbc click ID on every event?No. Send every order and include fbc when the URL has one. The hashed email is what lets Meta connect the order to the click.
Running Meta ads for a health brand? We do a free Meta audit: a full account audit plus net new reach and cumulative reach reports. Reach out on our contact page.
Check what you learned
Tap an answer to see if you got it right.
1. What can Meta block when it classifies a site as health related?
2. What's the way through?
3. Why keep your own count of Meta sourced leads?
Ready for the full test? Take the Measurement exam and get certified. Want this run on your account? Get my free audit.
Module 3: Measurement · article 6 of 15
Previous: Remarketing Is a Reminder, Not a Sale: Reach vs Conversion Objective on Meta
Next: Spending $300K+ a Month on Meta? You're Probably Wasting 25% of It
About the author
Jake Mehani, founder of Creative Analytics
Jake has spent 15 years running Meta and paid social ads for consumer brands. Meta published his RBX Active Advantage+ case study, he taught the DMAnc Meta and TikTok ads masterclass, and he spoke at Motion's 2024 Creative Strategy Summit. His senior team runs media buying, creative and measurement like an in house team.