Once Meta flags a health store, your Add to Cart and Purchase events stop reaching it. This kit sends them back, with the health data removed and more ways to match each buyer.
A ready-made setup you install once in your own Shopify and Cloudflare accounts, with a video for every step.
Meta publishes how it treats each store’s pixel, and any browser can read it. We read that public setting for your domain and tell you if you’re in restricted mode. No login, no access to your accounts.
We use your email to follow up on your result. No spam, no list sharing.
The fix takes about an hour: your sales data goes back to Meta from a clean source, without the health details.
If you sell anything close to health, Meta treats the data your store sends as sensitive and stops letting its algorithm learn from it. It happens in four steps, and most owners only notice at step four.
Meta’s pixel sends every page address and product name it sees.
“Joint Pain Relief Capsules”One health word can be enough. A notice shows up in Events Manager.
Data sharing restrictions appliedAbout 30 days later, Add to Cart and Purchase stop reaching Meta.
Purchase: blockedBudget still goes out. Meta no longer knows who bought, so it can’t find more people like them.
Sales: fallingMeta still counts the visits. The events that tell it who buys never arrive, so it keeps spending on people who only browse.
The restriction follows where your data comes from. Any fix that keeps sending from the same flagged source gets blocked the same way.
The events still come from the same flagged source. The new account gets the same restriction.
Shopify’s server events come from the same flagged source and carry the same product data. Meta blocks them too.
A custom name doesn’t change where the data comes from. It also restarts your optimization from zero history.
You wait for a review while your ads keep spending blind. When the product really is health-related, an appeal has little to argue.
Your own pixel records each visit, cart and purchase. A small program in your free Cloudflare account, your relay, removes the health data, adds the details Meta uses to recognize a buyer, and sends each event from a clean source. Nothing runs on our side.
Records views, carts, checkouts and purchases, with the ad click and browser IDs Meta needs to match each one.
Shopify, pasted onceProduct names, page addresses and categories stay in your relay. Only the event, its value and hashed customer details go out.
Your relayEmail clicks identify customers you already know. “Buy now” orders get tied back to the ad click. IP adds city, state and ZIP.
Your relayEvents reach Meta through its official Conversions API, from a source that isn’t flagged.
Meta Conversions APILeft: what a standard pixel sends. The red lines are what gets a store flagged. Right: what your relay sends instead.
"event_name": "Purchase", "event_source_url": "yourstore.com/products/ joint-pain-relief-capsules", "content_name": "Joint Pain Relief Capsules", "content_category": "Supplements › Pain", "content_ids": ["jpr-60ct"], "value": 49.00, "currency": "USD", "user_data": { "em": "…", "client_ip": "…" }
"event_name": "Purchase", "value": 49.00, "currency": "USD", "user_data": { "em", "ph", "fn", "ln": hashed, "ct", "st", "zp", "country": hashed, "fbc": ad click ID, "fbp": browser ID, "external_id": visitor ID, "client_ip", "client_user_agent" }
No server. No developer. No terminal. Every step is a button, a copy or a paste, and every one is on video. Most of the hour goes to waiting for pages to load and events to show up.
One button sets it up in your free Cloudflare account. Nothing to maintain after that.
Paste the code we give you into Shopify. You don’t edit a single line.
Follow the checklist, watch your events arrive in Meta, then move your campaigns.
Meta’s pixel sees one page at a time. Your relay sees more: the order, the email your customer clicked, the ad they came from, and roughly where they are. It attaches all of that to every event before sending it.
emailhashedemail clickphone · namehashedpast orderad click IDwhich adad clickbrowser IDsame browserbrowservisitor IDsame visitorbrowsercity · state · ZIPhashedIP locationnetwork · deviceIP, browserrelay“Buy now” orders never touch the cart. Your relay still ties them to the visit and the ad that brought them.
Someone clicks your email, then browses. Every page view and cart now carries who they are, along with the final purchase.
No email yet? Their city, state and ZIP still go out with each event, so Meta has something to match on.
On every event your relay sends to Meta.
Email, name and address on every purchase.
Tied back to the visit and the ad click.
On every page, from the first click.
Measured in Meta Events Manager on a store running the kit, October 2026.
A monthly tool is easy to start and never ends. The kit costs more on day one and less from month six.
And if you stop paying a monthly tool, your tracking stops with it. The kit keeps running.
Monthly prices are typical of tools sold for this problem. Hosting: Cloudflare is free up to 100,000 requests a day and $5/month above that. We used $5/month to stay conservative.
Stays in your own Cloudflare database. We never see it.
Copied to your own GitHub. Read it, change it, keep it.
No subscription. If we closed tomorrow, your setup would keep running.
One license = one Shopify store. Paid upfront. All sales are final: the kit is delivered as code and videos the moment you pay.
No. Every step is a button, a copy or a paste, and each one has a video. If you’d rather not touch anything, choose Done for you and we install it on your accounts.
Yes. Give them access to Shopify, Cloudflare and Meta Business and they follow the same videos. Everything stays in your accounts.
A Shopify store, admin access to your Meta Business account, a free Cloudflare account and a free GitHub account. The videos show how to create the last two.
No. It works on any Shopify plan.
Those events still come from your flagged source and still carry your product data. Meta blocks them the same way.
You stop paying every month, and the setup lives in your accounts instead of someone else’s. If you cancel the tool, your tracking stops. The kit keeps working.
Cloudflare’s free plan covers 100,000 requests a day. Above that, Cloudflare charges $5 a month.
No, it goes up. Purchase match quality is 7.8/10, the browser ID is on every event, purchases carry full customer details, and returning customers are recognized from email clicks.
They show up in Meta’s Test Events tool as soon as setup is done.
Yes, better matching helps any store. If your tracking isn’t restricted, though, the gain is smaller and Shopify’s built-in integration may be enough.
You send standard events through Meta’s official Conversions API, with no health information in them. Meta’s rules can change, and nobody can promise how Meta will treat an ad account. We don’t make that promise either.
Installed within 48 hours after payment and access to your Shopify, Cloudflare and Meta accounts.
For life, and they install themselves. Every time Meta changes something, the fix reaches your relay automatically.
One license covers one Shopify store. For more stores, buy one license per store.
No. The kit is code and videos you receive the moment you pay, so all sales are final. If you’re unsure you can install it yourself, choose Done for you.
There’s nothing to stop paying. You pay once. The code and the data live in your accounts.
One hour of setup, or none if we do it. One payment. Your sales back in front of Meta, running in your own accounts.