Does a new domain fix a Meta health restriction? (And why a redirect domain is the worst idea)
Short answer
Sometimes, as a last resort. A new domain is classified separately, but the same content gets the same result, and Meta can link domains through accounts and payment. Never send ad traffic through a redirect from a clean domain to a restricted one.
This comes up in every restricted account conversation, usually in week two, so here is the straight answer.
A new domain is a new data source, and Meta classifies data sources one by one. So in principle a new domain starts without the old classification. In practice it only helps if what Meta reads there is genuinely clean, and it carries real risk.
There are two versions people consider. One is a separate store with a narrower range: for the maternity store we worked with, that would have meant fashion only, with the support products and anything making a claim staying on the original store. The other is a second domain on the same Shopify store. The second is simpler, but if the content is the same, the classification is likely to follow, because Meta reads the same titles, alt text and claims on both.
The risks: Meta can link domains through the same ad account, business portfolio or payment method. A new domain that carries the same words will be classified the same way. And you lose the history of the old pixel. Nobody can promise a new domain stays clean.
Now the redirect idea, because someone always suggests it: point your ads at a clean-looking domain that sends visitors straight on to the restricted store. Do not do this. Meta sees one page and the customer sees another. That is the practice most likely to get an ad account closed, and an ad account is much harder to replace than a domain. It was the one idea we refused outright for our customer.
If you do go the new domain route, do it in this order. Clean the original first and ask for one review. Only if that fails, build the new store properly: check every page for condition words before a single ad points at it, use a new pixel and dataset, send cleaned events from day one, and keep the original domain running for organic search, Instagram, email and returning customers.
Has anyone moved to a new domain after a restriction and stayed clean for six months or more? What did you change about the content?
For reference, if you build a new store, turn DataCops Health mode on from the first day so nothing sensitive is ever sent from the new domain.
DataCops in short
For this question: Health mode sends Meta a fixed list of fields only: the click ID, hashed email and phone, value, currency, IDs and the homepage address, under a neutral event name, and the delivery log shows exactly what left.
DataCops is a tool that keeps condition details out of what your ad platforms see: Health mode cuts page links to the domain, uses neutral event names and leaves out anything that describes a condition, while a bot verdict on every visit and a delivery log show what left and what was real.
How DataCops does it
- Health mode. Page links are cut to the domain, event names are neutral, and anything that describes a condition is left out before an event leaves.
- A log of exactly what left. A delivery log row per conversion, sent, held, skipped or failed, with the reason, which is the record you want when explaining yourself to a reviewer.
- Real people only. Every visit gets a bot verdict against 360+ billion IPs and 350+ monitoring points, with a Real people only switch per ad platform, off by default.
- One script, one DNS record. Collection runs on your own domain, and conversions go server-side to Meta, Google Ads, TikTok and LinkedIn, counted once against the pixel.
- The booking after the form. HighLevel natively, any CRM by webhook, sent as neutral events so a booked consultation still teaches the ads who converts.
Best for: clinics, telehealth and wellness brands, and agencies running health ads, who want conversions to keep counting without condition details in the data.
Ads Warmup: tell the ads who pays
Ads Warmup, DataCops' flagship feature, sends customers you already have to Meta, Google Ads and TikTok before a new campaign spends: upload a CSV (only email is required, up to 20,000 rows), see a 0 to 10 match score per person, pick the event, and send. Rows are dated when you send, and Google Ads credits only people who clicked a Google ad. Preview is free; sending needs a paid plan. Check your own consent basis for the list first. See Ads Warmup.
Ways to do this job
| Option | Best for |
|---|---|
| DataCops | Health mode, neutral events and a delivery log, server-side to four ad platforms |
| Manual event cleanup in your site and tag manager | Teams with an engineer who will maintain it |
| Turning conversion tracking off | Accounts that cannot risk any event |
When not to use DataCops
- You need legal or compliance advice. DataCops is not legal advice and does not make an ad account compliant. Your own advisers decide what you may send.
- You need a regulated setup with a signed agreement. That is the Enterprise plan: talk to the team.
Sources and further reading
More on this: The full case and recovery guide, and the complete guide to offline conversion tracking.
Not legal advice, and not something we recommend lightly. It is a last resort after a clean review has failed.