A Meta dataset is the container in Events Manager that groups your event data from a website, an app, physical stores and business chats under one dataset ID, whether the events arrive through the Meta Pixel, the Conversions API, an SDK or a file upload (Meta Business Help Center). For most website advertisers it’s what the Pixel is called now: if your Pixel was converted into a dataset, the dataset ID is your old Pixel ID.
How a Meta dataset works
Each integration used to have its own ID: a Pixel ID, an app ID, an offline event set ID. Meta now moves each web and app integration into its own dataset automatically, keeps the old IDs, and lets you merge web, app, offline and messaging events into one dataset if you want them together (Meta’s changes article).
Whether you get a new number depends on how the dataset was made. A dataset linked to an existing Pixel keeps the Pixel ID; one created from an app with Create new, or for offline events, gets a new ID. A dataset can receive events from:
- the Meta Pixel (website)
- the Conversions API (website, app, offline, messaging)
- the Facebook SDK, mobile measurement partners and the App Events API (app)
- CSV uploads (offline)
If you only track a website, Meta says you don’t need to create a dataset at all: install the Pixel and use its ID for the Conversions API (dataset creation options).
Which ID goes where
| Where | ID | Source |
|---|---|---|
| Meta Pixel base code | dataset ID, same as the Pixel ID | About datasets (above) |
| Conversions API, website events | /{PIXEL_ID}/events | Using the API |
| Conversions API, app, offline and messaging events | /{DATASET_ID}/events | Offline events |
| Ads Manager, ad-level tracking and website optimization | dataset ID | changes article (above) |
| Dataset Quality API | dataset_id, “the ID of dataset (Pixel)” | Dataset Quality API |
Meta’s Conversions API overview sums it up: server events are linked to a dataset ID and processed like events sent through the Pixel (Meta for Developers).
Where you see it in Events Manager
Open Datasets in the left menu and select your dataset by name and ID. The Settings tab holds Dataset categories and the Conversions API section, where users with developer privileges can generate an access token (get started). Test events shows incoming events while you test, and the Event Match Quality guide covers the quality scores. To give an ad account access, go to Meta Business Suite settings, Data sources, Datasets, then Add assets (add an ad account).
Dataset categories and restrictions
When you create a dataset you can assign it one or more categories. It’s optional, and Meta can assign categories too, which you can’t change yourself (categorize datasets). A restricted category can bring core setup (custom parameters and URL paths dropped), restrictions on certain standard events, or a block on sharing events in some regions or all of them (data sharing restrictions). If you run lead gen in health or finance, check Settings before you wonder why a custom audience stopped filling.
The Lead event is only as useful as the dataset it lands in. DropCPL sends each landing page lead to Meta server-side through the Conversions API, with event_id for deduplication and fbc/fbp, to the Pixel you select for each client subaccount. Start free →
Datasets in lead generation
Send the browser and the server copy of a Lead to the same ID. Meta’s get started guide asks for the same Pixel ID on both, and its deduplication rules only discard a duplicate when both copies are sent to the same Pixel ID within 48 hours (Handling duplicate events). Send them to two IDs and Meta can’t tell they’re the same lead; Pixel + CAPI deduplication covers the rest.
For agencies, my rule is one dataset per client, shared with that client’s ad account and nobody else’s. A dataset that mixes two businesses mixes their events, their audiences and their optimization signal.
Related terms
- Meta CAPI: the API that posts events to a dataset ID
- Conversions API Gateway: a no-code way to feed a dataset from a server
- Server-side tracking: the general pattern
- Custom audience: website audiences take their events from your Pixel