Multi-Location Clinics: Ad Account Structure

The right ad account structure for a multi-location clinic group is one business manager or MCC at the group level, separate ad accounts per location only where budget or entity boundaries require it, and a single measurement layer underneath all of them so location detail and group rollups come from one dataset. Curve is the HIPAA-compliant tracking and attribution layer that makes that split possible, tagging every event with its location while keeping patient data out of platforms that do not sign BAAs. Structure follows measurement, not the other way around.

Decide the measurement model first

Most agencies structure ad accounts first and then discover the reporting cannot be assembled. Reverse it. Three questions settle the structure.

Who owns the budget? If each location controls its own spend and can turn it off, that location needs a separable budget container. If the group allocates centrally, it does not.

Who owns the P and L? Separate legal entities, franchise agreements, or joint ventures with local partners usually force separate ad accounts for billing and access reasons, regardless of what is optimal for the algorithm.

How much data does each location generate? This is the question that decides whether granular structure helps or hurts. A location producing a handful of conversions a week cannot support its own campaigns with their own optimization. Splitting it out starves the learning phase and produces expensive noise.

The structure that works for most groups

One business manager, one MCC

Group level, agency-managed, owning the assets. Pages, pixels or server-side connections, catalogs, and conversion actions live here. Locations get access to what they need rather than owning it, which is what makes offboarding a location, or a location's local marketing hire, a permissions change instead of a recovery project.

Insist on the client owning the business manager and granting the agency partner access. Agency-owned assets look convenient at onboarding and become a hostage negotiation at the end of the relationship. It is also the cleaner compliance posture, since the client stays the data controller of their own advertising assets.

Ad accounts: fewer than you think on Meta, more on Google

The platforms reward opposite instincts here.

On Meta, consolidation usually wins. Meta optimizes on volume, and splitting fifteen locations into fifteen ad accounts fragments the conversion signal fifteen ways. A single ad account with location-based campaigns or ad sets, geo-targeted, generally outperforms fragmented accounts on the same total budget. Split only when billing entities, market separation, or a location's insistence on controlling its own spend force it.

On Google, the calculus shifts because search intent is already segmented by query and geography, and because Google's account structure carries more administrative weight. Separate accounts under one MCC make sense when locations have genuinely different service mixes or budget owners. Where the service lines are identical, campaign-level separation inside one account keeps the conversion history together.

Campaign layer: one axis of separation, not three

The most common structural failure is stacking separation axes: location, then service line, then funnel stage, then device, until each campaign has a budget too small to leave learning. Pick the axis the client actually manages the budget on, and use targeting or asset variation for the rest.

For most clinic groups that axis is location, because that is where the budget conversation lives and where the geography differs. Service line becomes ad set or ad group, and creative carries the rest.

Conversion actions: defined once, at the group

Every location reports the same conversion definitions. A booked consultation means the same thing at every site, sends the same neutral event name to the platform, and appears once in the conversion action list. Location distinction lives in the event's location attribute and in campaign structure, not in a proliferation of conversion actions named after individual practices.

This is also the compliance-sensitive layer. Conversion action names travel into shared reporting, and a conversion action named for a specific procedure discloses clinical intent to a platform with no BAA attached to it. Keep the descriptive names internal.

The naming convention that survives twenty locations

Fixed order, fixed delimiter, no free text. A workable pattern is brand, location code, channel, objective, service category, and audience type, in that order, with a hyphen or underscore between segments and nothing else.

Two rules make it durable. First, use stable location codes rather than location names, since practices get renamed and acquired sites change branding while the code stays the key that joins ad platform data to your measurement layer. Second, use neutral service categories in anything the platform stores. The internal mapping from category to actual service line lives in your documentation.

Enforce the convention with a stored template and a monthly audit, because conventions decay at the exact rate that new people join the account.

Where multi-location structure creates compliance risk

Structure is usually treated as a performance topic. In healthcare it is also a disclosure topic, in four specific places.

Campaign and ad set names. Names encoding the condition or procedure sit in the platform permanently and appear in every shared report and screenshot.

Location-level conversion counts. A single-clinician location with two conversions in a narrow service category is close to identifying. This matters in reporting, and it matters in any audience built from that segment.

Custom audiences per location. Uploading a location's patient list to build a lookalike is a disclosure of PHI to a platform that has not signed a BAA. It is the most common serious mistake in multi-location healthcare advertising, and it is usually made by someone trying to help.

Shared pixels across sites. A group pixel firing on every location's site, including the acquired one that still runs a legacy booking flow with the procedure in the URL, spreads one site's exposure across the whole group. Related reading: why client-side pixels create HIPAA exposure.

Geo-targeting and the overlap problem

Two locations twenty minutes apart will bid against each other unless someone decides they should not. On Meta, overlapping audiences inside one ad account raise costs and produce delivery that looks random. On Google, two campaigns targeting overlapping radii compete in the same auction with the group paying both sides.

Draw the catchment boundaries deliberately, using drive time rather than radius, and let them meet without overlapping. Where overlap is unavoidable in a dense urban market, consolidate those locations into one campaign and let the landing experience route the patient to the nearer site. The reporting still separates them, because the conversion carries a location attribute regardless of which campaign paid for the click.

Watch for the asymmetry that comes with a strong organic footprint. A flagship location that ranks well locally often absorbs paid clicks that a nearby weaker site needed, which shows up as one location looking efficient and its neighbour looking hopeless. Location-tagged conversion data is what makes that visible rather than mysterious.

How Curve supports multi-location account structure

Curve is HIPAA-compliant ad tracking, attribution, and analytics for healthcare, and multi-location groups are a core use case. The point of the integration is that account structure and reporting structure stop being the same decision.

• One install, location-tagged events. The tracking script installs once per domain in place of the Meta Pixel and Google tag, and each event carries a location identifier as an attribute. Practice-level and group-level views come from the same dataset.
• Per-destination field mapping. Only explicitly mapped fields forward to a given destination, so what each ad account receives is a deliberate, inspectable configuration.
• Neutral event aliases. The platform sees a neutral event name; your reporting keeps the descriptive one.
• Identifier hashing. SHA-256 per each platform's conversion API requirements before anything leaves.
• Bridge tokens. Attribution survives the handoff to a separate booking or intake tool, which multi-location groups use constantly.
• Incoming webhooks and offline conversion uploads. Outcomes from heterogeneous practice management systems return and match on email, click ID, or bridge token, so acquired locations with different back ends still roll up.
• PHI-pattern detection as a monitoring layer, which is how you find the one location whose legacy form is sending something it should not.
• Signed BAA on every plan.

Curve forwards server-side to Meta CAPI, Google Ads Enhanced Conversions, TikTok, Microsoft, LinkedIn, and GA4. For groups running dental or DSO structures specifically, see attribution across multiple dental practices and the DSO marketing technology stack.

Adding and removing locations without breaking history

Groups change shape constantly, and the structure has to absorb it.

When a location joins, assign the location code before anything else, then create its campaign container inside the existing account rather than a new account wherever billing allows. Inventory whatever tracking the acquired site carries and remove legacy pixels before pointing spend at it. Run parallel for one full reporting cycle so variance can be explained rather than argued about.

When a location leaves, pause rather than delete, revoke user access the same day, and export what you need for the final report. Deleting campaigns to tidy up destroys the conversion history the remaining locations' benchmarks were built on.

Frequently asked questions

Should each clinic location have its own Meta ad account?

Usually not. Meta optimization benefits from consolidated conversion volume, so separate ad accounts per location fragment the signal. Split only when separate billing entities, genuinely separate budget owners, or market separation require it, and keep measurement consolidated regardless.

How many conversions does a location need to justify its own campaign?

Enough to leave the learning phase and stay out of it. If a location cannot sustain that on its own budget, group it with nearby locations into a regional campaign and report on it separately using location-tagged events.

Can we name campaigns after the service they promote?

Use neutral service categories in the ad platform. Names travel into shared reports, screenshots, and any exported data, and a name that discloses the clinical intent of a targeted audience is a disclosure to a platform that has not signed a BAA.

What about locations on separate domains after an acquisition?

Track them all into the same measurement layer with their own location identifiers, and keep the acquired domain's legacy pixels off. Cross-domain and multi-domain tracking handle the technical side. The reporting question is answered by the location attribute, not by which domain the visit happened on.

Who should own the business manager, the agency or the client?

The client, with agency partner access. It is cleaner at offboarding, it keeps the client as the owner of their own advertising assets, and it avoids the situation where a group's entire conversion history sits inside an agency-owned container.

Do we need separate conversion actions per location?

No. Define conversion actions once at the group level and let location live as an attribute on the event and in campaign structure. Per-location conversion actions multiply maintenance and make group rollups a reconciliation exercise.

Where to start

Map the group's budget owners and legal entities on one page. That map, not platform best practice, determines how many ad accounts you actually need. Then make the measurement layer location-aware so structure can stay as simple as the budgets allow.

Curve provides that layer for multi-location healthcare groups: one install, location-tagged events, per-destination field mapping, bridge-token attribution, outcome matching from mixed practice management systems, and a signed BAA on every plan. Run the free compliance scanner against a group site and a recently acquired location, or visit curvecompliance.com to plan a rollout across the group.

Reviewed August 2026. Ad platform conversion APIs and healthcare advertising policies change frequently. Verify current requirements before implementation.