Meta consolidated the pixel into the broader dataset structure, but the operational question hasn't changed: how many datasets do you need, who should own them, and how do you share them cleanly across a multi-Business-Manager setup without breaking attribution. Get this wrong and you end up with fragmented data that makes optimization decisions unreliable.
One dataset per domain, not per campaign
The core rule: a dataset should map to a domain or a coherent business entity, not to a campaign or a creative test. Creating a new pixel for every campaign fragments your event history and starves each one of the volume Meta's optimization needs to work well.
For a single-domain business, one dataset shared across every ad account that advertises that domain is almost always correct. For a multi-brand operation, each distinct domain typically warrants its own dataset, owned by the entity that owns the domain.
Ownership and sharing across Business Managers
Datasets live inside a Business Portfolio and get shared to ad accounts, including ones in other Business Managers via partner access. When you receive shared agency ad accounts, you'll typically connect your own existing dataset to the new account rather than creating a new one — this keeps all your conversion history and optimization signal unified in one place regardless of which ad account is spending.
Be deliberate about who owns the dataset. If an agency creates and owns the dataset on your behalf, make sure you retain admin access to it directly, not just view access — losing dataset ownership when an agency relationship ends is a real and recoverable-but-painful problem.
CAPI as the resilience layer
Server-side event tracking via the Conversions API (CAPI) should be treated as standard infrastructure now, not an advanced option. Browser-side pixel tracking alone misses a meaningful share of events due to browser restrictions and ad blockers, and CAPI, deduplicated correctly against the browser pixel, recovers that signal.
Set CAPI up once per dataset, not per ad account, and verify event deduplication is working correctly in Events Manager before trusting the combined data for optimization decisions.
- Map datasets to domains or business entities, not campaigns
- Share one dataset across multiple ad accounts rather than fragmenting
- Retain direct admin access to any dataset an agency sets up on your behalf
- Implement CAPI per dataset and verify deduplication
Troubleshooting cross-Business-Manager attribution
When ad accounts across different Business Managers all feed into one shared dataset, event matching and attribution windows still work the same way — the dataset doesn't care which Business Manager the spending account lives in. Most attribution confusion in this setup actually comes from domain verification mismatches or duplicate, unshared pixels created accidentally by a new team member, not from the multi-BM structure itself.
Audit Events Manager periodically to confirm you don't have duplicate datasets receiving fragments of the same traffic — a common byproduct of onboarding a new ad account provider without checking whether a dataset already exists for that domain.
Getting this right during onboarding
This is exactly the kind of technical detail that should be handled explicitly when new agency accounts come online, not left to chance. Power Ads' onboarding process connects new agency ad accounts to your existing dataset rather than encouraging a new one, so your conversion history and optimization signal stay unified as your account footprint grows.
Key takeaways
- One dataset per domain or business entity, shared across ad accounts, not fragmented per campaign
- Retain direct admin access to any dataset set up on your behalf by an agency or partner
- Treat CAPI as standard infrastructure and verify deduplication
- Audit Events Manager for accidental duplicate datasets as your account count grows
FAQ
Should a new agency ad account get its own pixel?
No — connect it to your existing dataset for that domain so conversion history and optimization signal stay unified rather than fragmented.
Is CAPI necessary if my pixel is already firing correctly?
Yes. Browser-side tracking alone misses events due to ad blockers and browser restrictions; CAPI recovers that signal and is standard practice at any meaningful spend level.
