What Is Meta Core Setup? What It Does to Your Shopify Pixel and Conversions API Events

Meta Core Setup is a set of data sharing restrictions that Meta, or you, can apply to a Pixel or Conversions API dataset. It blocks custom parameters and anything in a URL after the domain. Purchase and other standard events keep flowing with value and currency, but URL-based audiences, automatic advanced matching and pixel catalog updates can stop working.

Core Setup is the lightest of the three tiers in our guide to Meta's health and wellness restrictions, which also covers the fix. This post goes deeper on Core Setup alone: what it does to a Shopify store's events field by field, which features break, the four ways a dataset lands in it, whether it reaches beyond health and wellness, and how to confirm it in Events Manager. We checked every Meta detail against Meta's Business Help Center and developer documentation on October 24, 2026.

What is Meta Core Setup?

Core Setup is a restriction Meta can place on one of its Business Tools, or that you can place on it yourself (About core setup). The Business Tools include the Meta Pixel and the Conversions API, so the restriction sits on the dataset and applies whichever way your events reach it.

It does two things. It stops custom parameters from being shared, and it cuts every URL down to the domain. Everything else in an event is outside its scope, and that matters more than it sounds, as the next section shows.

It's the mildest of Meta's three restrictions by data source category: Meta says most campaigns should keep running as expected under it, while the stricter tiers restrict specific mid and lower funnel events or all events. Meta also says Core Setup doesn't replace your own compliance checks, so what you send stays your responsibility.

---

What does Core Setup remove from Shopify events?

Meta's own example: https://jaspersmarket.com/clothes/summer/dresses?item=10 becomes https://jaspersmarket.com/. On a Shopify store, the same rule turns https://yourstore.com/products/joint-support-gummies?variant=4471&utm_campaign=joint-pain into https://yourstore.com/. The product handle, the variant and every UTM go.

For parameters, Meta draws the line at its standard list: any parameter that isn't on it counts as custom. Here's how that plays out on a typical store's events:

The unclear row is the one that catches health and wellness brands. Meta's Pixel reference lists content_name and content_category among its predefined object properties. Its Conversions API standard parameters table, updated November 17, 2025, lists neither. Meta doesn't say which list Core Setup applies, so don't count on it to strip a product title or a "Supplements" category.

search_string is standard in both, so Core Setup's rule doesn't cover a Search event carrying the term a shopper typed, even when that term is a condition.

"Kept" means Core Setup's rule doesn't remove the field. Meta's separate filters can still detect and remove prohibited information in any field, which is where notifications come from.

Our take. Core Setup filters two kinds of field. It doesn't review your payload. A product title that names an ingredient or a condition, or a search term, can still be in the event. Meta's prohibited information page tells advertisers to check product IDs, content names, custom properties and URL parameters themselves, and those are the fields to start with when Meta sends a prohibited information notification.

---

Which Meta features break under Core Setup?

Meta lists the side effects in its Core Setup article. Here they are with what to do about each on a Shopify store:

How do you confirm custom events?

In Events Manager, click Datasets, select your dataset, open Settings, scroll to Data controls and click Review in Manage event blocking. Pick the events in the Action required tab, then confirm or block them (Meta's steps). Confirmed custom events work in campaigns, custom conversions and custom audiences. Blocked ones work in none of them.

Two limits matter. You may not be able to confirm a custom event that Meta detected and blocked itself, and if Meta turns down your review request for one, you can't ask again. Meta also says the names you give events, conversions and audiences must not reflect or imply prohibited information, so a name like SleepQuizComplete is a bad start.

Upstack's new-customer events are custom events too, which is why our NC Purchase setup guide starts with confirming them in Events Manager.

---

How does a dataset end up in Core Setup?

Meta lists four routes in its Core Setup article. Whether you can undo it depends on which one applies:

The second route has a catch. Removing a self-assigned category lifts Core Setup only if you didn't also opt in to it separately and Meta hasn't placed the pixel in Core Setup itself.

Can you turn off Core Setup?

Only when you or a colleague turned it on. You need to be an admin of the business portfolio or the ad account that owns the dataset. Then:

1. Open Meta Events Manager and click Datasets.
2. Select your dataset and open the Settings tab.
3. Scroll to Data restrictions and find the Core setup section.
4. Click Turn off.

If Meta turned it on, Meta says you won't be able to turn it off. What's left is a category review: under Manage data source categories, click View details, then Request review (Meta's steps), and Meta emails its decision. In the accounts we work with, these reviews rarely change a health and wellness category, so plan as if Core Setup will stay.

Does Core Setup only apply to health and wellness?

No. Health and wellness is one of the data source categories Meta says may carry data sharing restrictions. The others it lists are financial services, unsuitable content, politics, race, religion, sexuality and gender identity, gender identity, nationality, trade unions, personal hardship and economic vulnerability. Meta adds that the list isn't exhaustive and may change.

Meta doesn't publish which restriction goes with which category. It says the restrictions can differ by category and by country or region.

Two of the four routes don't depend on a category at all. A store in any category that collects repeated prohibited information notifications can be placed in Core Setup, and any advertiser can switch it on. Meta's notification troubleshooting guide even suggests turning it on yourself as a precaution.

---

How do you know if your dataset is in Core Setup?

Work through these in order. None of them needs a developer.

Meta describes the URL and Sampled Activities views in its guide to viewing pages, parameters and URLs, which covers events from both the Pixel and the Conversions API.

The URL view is the quickest tell. If ViewContent shows only your domain while you know the pixel fires on product pages, something is truncating the URL: Core Setup, or a sender that already strips paths. Outside Events Manager, check Ads Manager for website audiences built on URL rules that stopped growing.

---

What should you send to a dataset in Core Setup?

Core Setup cuts two kinds of field and leaves the rest to you. These changes cover the gaps on a Shopify store. For every field to keep out of Meta's events, use the field-by-field table in our hub.

1. Remove what Core Setup may leave behind. Product titles in content_name, values such as "Supplements" in content_category and search terms in search_string. Use opaque content_ids rather than SKUs that spell out an ingredient.
2. Send identifiers yourself. With automatic advanced matching possibly gone, hashed email and phone, fbc, IP address, user agent and external_id have to come from your own setup, ideally from your server. Our Event Match Quality guide covers each one.
3. Optimize on standard events. Standard events and their standard parameters keep flowing, while custom events wait for review. Purchase with value and currency is the event to optimize on.
4. Rebuild URL-rule audiences on standard events before the old ones stop updating.

Our take. Core Setup on its own rarely calls for a new pixel. Meta says most campaigns keep running under it, and Purchase still arrives with value and currency, so start by cleaning up what you send. The clean pixel setup on our health and wellness page is for brands whose purchase events Meta restricts, or whose category follows them to a new pixel on the same domain. If that's you, our guide to moving Meta campaigns to a new pixel covers the switch.

Upstack applies field rules per destination, so Meta gets a filtered payload while your analytics keep full product data. It doesn't change a category Meta assigned or a Core Setup Meta applied. This isn't legal advice.

---

Frequently asked questions

Can you turn off Meta Core Setup?

Only if you or someone on your account turned it on, either directly or by assigning a restricted category. In Events Manager, open your dataset's Settings, find Core setup under Data restrictions and click Turn off. If Meta applied it, you can't turn it off; you can only request a review of the category.

Does Core Setup block Purchase events?

No. Purchase is a standard event, and value and currency are standard parameters, so they keep reaching Meta. Restricting specific mid and lower funnel events is a separate, stricter tier that Meta notifies advertisers about by email and in Events Manager.

Does Core Setup apply to the Conversions API?

Yes. Core Setup sits on the dataset, and the Conversions API is one of the Meta Business Tools that sends to it. A custom parameter sent from your server is still a custom parameter.

How long does Core Setup last?

Meta gives one duration: at least 90 days when it applies Core Setup after repeated prohibited information notifications. For Core Setup that comes with a category, Meta publishes no end date, and a Meta-assigned category can be reviewed but not edited.

Does Core Setup remove product names from events?

Don't count on it. Core Setup removes custom parameters and URL paths, and Meta's Pixel reference treats content_name as a predefined property rather than a custom one. Remove product titles that name an ingredient or a condition from Meta's events yourself.

---

Key takeaways

• Core Setup removes custom parameters and URL paths from Pixel and Conversions API events alike; standard events and parameters keep flowing.
• Product titles, categories and search terms may survive it, so remove them from Meta's events yourself.
• URL-rule audiences, automatic advanced matching and pixel catalog updates can break, and custom events need review.
• You can turn it off only if your account turned it on. After repeated notifications, Meta can apply it for at least 90 days.
• It isn't limited to health and wellness: Meta lists eleven other categories, and notifications can trigger it in any of them.

Request a demo and we'll check what Core Setup is cutting from your events today.