apointoo.
Request access
Google Ads for Healthcare

Where Should Clinic Conversion Actions Live: Client or Manager Account?

cmsapointoo··9 min read

A clinic conversion action can live in the individual client account or in a Google Ads manager account used for cross-account conversion tracking. That placement decision is not the same as deciding who owns the clinic’s data, who can access the client account, or which account a Data Manager request names. Treating all four questions as “ownership” makes offboarding harder than it needs to be.

For most clinics with one advertising account, keeping clinic-specific actions in the client account is the simpler portability default. This is editorial guidance, not a Google requirement. Manager-level actions suit groups that need shared tracking. The clinic Data Manager architecture covers the policy gate before any event is sent.

Which decision does the clinic need to make?

The first decision is where Google Ads creates and manages the conversion action. Google documents two models. An account-specific action is created in an individual client account and applies only there. A cross-account action is created in a manager account and can be used by selected managed accounts. A client account can use one model or the other, not both simultaneously.

Placement sits beside three other decisions: durable clinic access, limited agency permissions, and the correct Data Manager destination. A written offboarding plan explains how tracking changes when the relationship ends.

Question Google Ads object What it decides
Where does the action live? Client account or manager account Who creates and manages that conversion action
Who can work in the account? User and manager access Which people and linked accounts can administer it
Who owns client data? Client account The client’s continuing data rights and ability to unlink
Where does the API send? Data Manager destination The receiving account, action ID, and credential path
What happens at exit? Unlink and conversion configuration Which tracking path continues after the relationship changes

An “agency-owned” label is too vague. A manager may own a cross-account action without owning client data, or be linked without administrative ownership. Name the account, object, and permission instead.

When should conversion actions stay in the client account?

Account-specific conversion actions fit clinics that need a durable setup inside one client account. Google says these actions are created and managed in the individual account and apply only there. If the clinic changes agencies, the conversion objects, settings, and existing conversion statistics remain attached to the same client account. That supports a cleaner handoff, provided the clinic has direct administrative access.

This model also keeps the action boundary easy to audit. The client account is the conversion account, the action ID belongs there, and the Data Manager operating account points there. The agency can still work through a linked manager account. Access through an MCC does not require moving the action into that manager account.

A group with several serving accounts may need cross-account actions. Even one clinic loses the portability benefit without direct administrative access. Confirm a clinic-controlled administrator and a current action inventory. The offline conversion outbox report keeps delivery evidence separate from account configuration.

When does manager-level cross-account tracking make sense?

Manager-level tracking fits a real multi-account measurement design. Google lets a manager account create cross-account conversion actions and select managed accounts that will use them. This can centralize action definitions and reporting across a group. It is not simply a convenience switch for agency access, because the managed accounts stop using their own account-specific actions while the manager conversion account is selected.

The design needs an explicit scope. List every managed account that uses the action, the goal settings affected, the sites or applications carrying the relevant tags, and the team responsible for changes. Google warns that switching conversion accounts can change which default conversion goals campaigns use. Campaigns targeting specific actions need a review after either direction of change.

Choose this model for a documented shared-tracking need, not because an agency has an MCC. Managed accounts cannot share actions directly; the manager is the sharing point. If an external agency controls it, document that dependency and exit path first.

Does MCC ownership mean the agency owns the clinic’s data?

No. Google distinguishes manager administrative ownership from ownership of client data. An owner manager receives broad administrative and data-access privileges, which can include access to personally identifiable information in the client account. Google also states that this status does not take data ownership or administrative rights away from the client account. The client keeps its data and can remove manager ownership access by unlinking.

Linking alone does not automatically make a manager the administrative owner. A client administrator must enable that status for an existing linked account, and Google recommends granting it only when the manager needs those privileges. Agency operating documents should therefore record three facts separately: whether the MCC is linked, whether it has administrative ownership, and which individual users have administrative access.

Use least privilege and keep a clinic-controlled administrator active. Do not call the MCC “the owner” without naming the Google status. That shorthand hides permissions over users, security, manager links, and data.

What continues after a manager account is unlinked?

The client account keeps its own campaign history and access to Google Ads features after unlinking. Conversion tracking continuity is narrower. In documentation reviewed on August 16, 2026, Google says a cross-account tag stops recording conversions for clicks that occur after unlinking. It can continue recording conversions from earlier clicks for the remaining conversion window, typically 30 days.

If an older client-account tag remains, Google says it may resume unless another manager tag replaces it. Teams still need to identify the replacement action, confirm its tag or server destination, review goals, respect the conversion window, and reconcile both paths.

Removing the MCC ends that manager’s access. It does not create replacement actions, rewrite destinations, or validate bidding goals. The clinic booking outcome taxonomy keeps event meanings stable while account objects change.

How does Data Manager represent account ownership and access?

A Data Manager Destination records where data goes and how credentials reach it. Its operatingAccount is the account that receives the events. For Google Ads offline conversions, Google’s Send Events guide says this must be the Google Ads account that owns the conversion action. The productDestinationId is the conversion action ID within that operating account.

The loginAccount has a different job. It identifies the account where the credential’s Google user has access. In a manager-access scenario, this can be the manager account while the operating account is a child account that owns the action. A linkedAccount applies to documented partner-link scenarios. None of these fields transfers a conversion action between accounts.

Store a destination map per clinic with both account IDs, the action ID, source, status, and verification time. Never reuse another clinic’s destination because both sit under one MCC. Google supports several destinations per request, but per-clinic isolation remains an editorial security recommendation.

A practical governance default for clinics

For one clinic account, default to client-account actions and give the agency limited manager access. Use cross-account actions when several accounts need one framework and the clinic accepts the dependency. This remains governance guidance, not platform policy.

  1. Confirm the clinic has direct administrative access to the client account.
  2. List every conversion action, its owning account, source, goal, and primary or secondary role.
  3. Choose account-specific or cross-account tracking and document why.
  4. Record MCC link status separately from administrative ownership.
  5. Map each Data Manager operating account, login account, and action ID.
  6. Keep each clinic’s credentials, destination map, outbox, and audit evidence isolated.
  7. Write and test the unlink migration before the agency relationship changes.

The inventory must also say whether outbound delivery is permitted. Account placement cannot cure an ineligible health-data use. Review the clinic form eligibility boundary before sending.

Frequently asked questions

Does every clinic need conversion actions in its own account?

No. Google supports both account-specific actions and manager-level cross-account actions. For a clinic with one account, client-account placement is often the simpler editorial default for portability. A multi-account group may have a valid reason to centralize actions in a manager account.

Can an agency MCC access a client-owned conversion action?

Yes, if the manager link and user permissions provide the required access. Access through a manager does not mean the conversion action must live in the manager account. Record link status, administrative ownership, and user access as separate facts.

Does unlinking erase the clinic’s Google Ads history?

No. Google says the individual account keeps its campaign history and access to features. Cross-account conversion tracking can change after unlinking, so the team still needs a planned action, tag, goal, and Data Manager destination migration.

Does loginAccount own the Data Manager conversion action?

Not necessarily. It identifies the account used by the credential path. For Google Ads offline conversions, operatingAccount must be the account that owns the conversion action, and productDestinationId identifies that action.

References

Related articles