Main-domain category
- Before
- Health & wellness – other
- After
- removed, review accepted
Health and wellness (Shopify)Client work
Core Still Showed On: Getting a Written Answer on Purchase After a Meta Category Review
A Shopify health and wellness store had both domains classed as Health & wellness. I took the main domain through Meta's review, then got a written answer on whether Purchase was still filtered.
The brief
Context
A Shopify store selling health and wellness products advertises on Meta. Both of its data sources, the main domain and the store’s myshopify subdomain, were classified as Health & wellness – other. In that category Meta can limit which events and details it uses, so the store needed to know what the classification meant for Purchase, the event its ads optimise for.
The owner asked for the restriction to be resolved without third-party domains or workarounds that could put the ad account at risk.
Sounds familiar?
Symptoms
The investigation
How I diagnosed it
I started with the setup itself: the native Shopify and Meta connection, the event sources, the parameter names Meta received and the deduplication indicators. An extra legacy Meta base tag was still loading through Google Tag Manager, so I paused it before any review.
-
I separated the objects that were being treated as one. The main domain, the myshopify subdomain and the dataset each carry their own status. A category review is decided per domain; Core is a dataset setting. An accepted review on one domain says nothing about another, and a label on the dataset says nothing about how one domain’s Purchase is treated.
-
When Core stayed On after the accepted review, support replies pointed in different directions. I supplied native screenshots, followed the question through six recorded support references and asked for one specific thing: a check of the enforcement record for the main domain, with the domain and the time of the check named.
Handover
What I changed
Delivery noteDelivered Nov 2026
- Paused the extra legacy Meta base tag in Google Tag Manager.
- Submitted category reviews for both sources through Meta’s own process and recorded their outcomes separately.
- Blocked only the rejected myshopify subdomain in the dataset’s traffic permissions and kept the main domain allowed. The Shopify domain itself was not removed from the store.
- Kept the support trail: every reference, every answer and the screenshots behind them.
No replacement pixel was installed. No third-party domain or workaround was used.
Screenshots
The evidence
Native captures from Meta Events Manager and the support conversation. Domains and identifiers are masked; nothing else is edited.
Before → after
Results
Client work Done for real clients. Client details are anonymised.
Server-side Purchase from the main domain filtered on category grounds
- Before
- unclear while Core showed On
- After
- no, per Meta's enforcement-record check
Rejected myshopify source in the dataset's traffic permissions
- Before
- allowed
- After
- blocked, main domain still allowed
The full results table
| Check | Before | After | Read on |
|---|---|---|---|
| Main-domain category | Health & wellness – other | No category, review accepted | 3 Nov 2026 |
| myshopify subdomain category | Health & wellness – other | Kept, review rejected; source blocked | 3 Nov 2026 |
| Server-side Purchase from the main domain | Unclear while Core showed On | Not filtered on category grounds, per the enforcement-record check at 12:50 PM CET | 3 Nov 2026 |
| Core label | On | Still On: universal monitoring, not an active category restriction on the main domain | 3 Nov 2026 |
What this case does not claim
Core was not switched off, and the myshopify subdomain kept its category. Nothing here guarantees how a future review goes or rules out a new restriction. No change in Event Match Quality, ROAS or revenue is claimed: this is a category and event-treatment result.
A note from Daniilbefore you decide
What this means for a similar business
A review status and a Core label answer different questions from the one your ads depend on. After a category review, ask two things: which domain does the decision cover, and is Purchase from that domain filtered? Get the answer in writing, checked against the enforcement record, with the domain named.
Treat the main domain, the subdomain and the dataset as separate objects. Each can carry its own status, and blocking one source does not change another’s classification.
— Daniil
Situations this case answers
Read another case
Orders in Shopify, None in Google Ads: Proving a Purchase Repair With One Paid Click
A Shopify pet accessories store had orders but no purchases in Google Ads or GA4. I rebuilt the purchase sender and proved it with one paid click traced to its order.
Hi, I’m Daniil.
I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian; written correspondence in Spanish with translation support.
Have a similar task?
Describe your taskThe first answer is free, within one working day. Or write directly: next@taskfordaniel.com