Should each of my locations have its own Meta ad account?
Keep one ad account per legal entity and separate locations with campaign structure, not with accounts. Multiple accounts fragment your pixel data, your audiences and your learning, and they multiply the number of places a token can break. Separate accounts make sense when locations are separate legal entities, have separate billing, or are franchises with different owners. Reporting separation is a data problem, not a structural one.
What splitting actually costs you
Signal is the asset. Conversion history, audience pools and the optimization learning that comes from them accumulate at the account and pixel level. Splitting a market across accounts divides that history into pieces, each too small to be useful, and none of them can borrow from the others.
The operational cost is quieter. Every account is another set of permissions, another page connection, another token that can expire, another billing method that can decline. Multi-account operators spend a meaningful share of their attention on account plumbing rather than on marketing.
When separate accounts are genuinely right
- Separate legal entities. Different tax IDs and different billing responsibility should not share an ad account.
- Franchise ownership. When an owner may leave the system, their data and assets need to be separable without unwinding yours.
- Independent budget authority. If a location manager genuinely controls spend and can be over budget without affecting others, separate accounts enforce that cleanly.
- Regulatory or contractual isolation. Rare, but decisive when it applies.
Doing separation inside one account
Naming conventions carry more weight than people expect. A disciplined scheme — location, service line, funnel stage, creative concept — makes campaign-level reporting sliceable without any structural separation, and it survives staff turnover in a way tribal knowledge does not.
Geographic exclusions are the other half. Overlapping radii between branches means two of your own campaigns bidding on the same households, which raises cost for both. Define non-overlapping postal code sets once and apply them everywhere, including search.
Roll up the reporting outside the platform
The reason operators split accounts is usually reporting: they want a clean per-location number. That is solvable without fragmenting the media. Pull campaign-level spend and results by location tag, join them to jobs from each branch, and produce both the location view and the enterprise view from the same dataset.
That rollup is standard integration work and it is the only way to compare locations honestly, because it normalizes for the fact that branches have different market sizes and different capacity. Location-level briefs can then go to each manager while ownership sees the consolidated view in one dashboard.
Topics: multi-location · account structure · reporting · governance
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.