- Published
- Oct 30, 2026
- Reading time
- 11 min read
Google Ads Cross-Account Conversion Tracking: A Migration Audit
Check Google Ads conversion ownership, manager tags, GA4 imports and campaign goals before moving client accounts to cross-account conversion tracking.

In this guide (11 sections)
Before moving Google Ads conversion tracking to a manager account, identify the current conversion owner, the replacement action and its collection method, and the goals each campaign will actually use afterward. A manager link by itself does not establish those three things.
The useful acceptance test is a documented handoff: the intended action receives eligible activity, the intended client uses the correct conversion account, and its campaigns retain the intended business outcome. Do not declare success because the new action appears in a list or a tag fires once.
Google's cross-account overview describes shared actions created in a manager account. Its setup instructions require necessary tracking to be in place before the conversion-account switch and warn against removing old actions or tags before the chosen conversion window has passed. Treat this as an ownership and reporting migration, with an implementation test attached.
The real questions behind this audit#
In an older two-account tracking discussion, an advertiser sending ecommerce and service traffic to one website asks whether existing tags can be reused at manager level. Later replies question the suggestion that an existing client action can simply be shared upward. The author also asks about importing the same GA4 outcome into both accounts.
A separate older account-to-MCC migration question asks how to transition existing clients without disrupting tracking. A visible reply proposes a fixed 30-day secondary period. That is community advice, not a universally documented migration requirement.
These are evergreen implementation questions. The answer below uses current official documentation rather than treating the threads' replies as an instruction set.
Check which account owns the conversion action
Cross-account tracking depends on manager links and the selected conversion source. Discuss the account path and reporting scope for your setup.
Discuss a measurement questionA short inquiry to scope relevant options; no campaign access is needed.
Separate the account link, conversion owner and campaign goal#
Use three rows in your audit, even if one person administers everything:
| Layer | Question to answer | Evidence to save |
|---|---|---|
| Account relationship | Which manager is linked to this client? | Client and manager identifiers, with the account context visible |
| Conversion ownership | Which account supplies this client's conversion actions? | Google Ads Conversion Account setting and action owner |
| Campaign goal selection | Which outcomes does each campaign use? | Effective goal selection and action membership |
An agency's manager access is not, by itself, evidence that the agency's manager owns conversion tracking. Conversely, viewing an action from a client does not mean the client can edit it. Google's overview distinguishes visibility in the client from management of shared actions in the manager.
Cross-account tracking is also different from cross-domain measurement. Two domains raise questions about continuity between sites; two advertising accounts raise questions about conversion authority and reporting scope. Write down which problem you actually have before changing either implementation.
For the broader difference between a platform's conversion credit and independently measured delivery, use our platform-versus-independent measurement guide.
Step 1: Build an action inventory before touching tags#
Make one row per action, including actions with identical display names. Record:
- Owning account and action identifier.
- Source: website tag, GA4-based conversion, app or another supported source.
- Business outcome and its exact trigger.
- Count setting, value/currency policy and applicable conversion windows.
- Primary/secondary setting and campaign goal membership.
- Collection destination, deployment version and person responsible for testing.
Names are a convenience, not an identity key. A client-owned purchase and a manager-owned purchase may have the same name while remaining different actions. A GA4 import and a native website action can also describe the same business outcome through different collection and attribution paths.
Mark each action retain, replace, or investigate. Do not remove a confusing action merely to make the list shorter. Preserve a report export and the configuration that explains its historical counts.
If the immediate issue is an inactive website action, start with the inactive-conversion diagnostic. Moving ownership will not repair a broken form trigger or a destination that never receives the event.
Step 2: Verify the active conversion account#
In the manager, inspect Accounts → Sub-account settings → Google Ads Conversion Account. Google's setup reference explains the displayed values: Client means no manager has been chosen for conversion tracking; This Manager identifies the manager you are viewing; another name identifies another manager.
Save that setting for every affected client. Being linked under several managers does not create several simultaneous conversion authorities: the documented arrangement uses one manager's conversion actions for that client, or the client's own actions.
Use this read-only checkpoint to catch a common error: preparing a replacement action in one manager while the client still uses another. An action can exist and a tag can send requests while the intended client is not configured to use that action set.
Do not make a bulk switch until you can identify each client's current state, proposed state and responsible approver. This is especially useful when a manager contains unrelated businesses whose conversion definitions should remain separate.
Step 3: Test the collection path that actually applies#
For a native website action, use the manager-owned action's actual implementation instructions and destination identifiers. Compare the deployed tag configuration with those instructions. Verify the business event triggers once under the intended conditions, with the required parameters, rather than checking only that a tag is installed somewhere.
The documented manager setup creates manager-owned actions. Do not assume that relabeling an existing client action, or changing an ID without checking its destination and trigger, completes the migration. Whether an existing Google tag installation can support the new destination is an implementation check; it does not turn the old action into the new one.
For a GA4-based action, audit the property link and selected conversion destination separately. Current GA4 linking instructions support links to manager accounts, require appropriate access, and explain that linking makes data available between the products. Linking is distinct from creating a Google Ads conversion based on an Analytics event.
Google's conversion-creation reference describes selecting the destination Ads account in Analytics, notes eligibility differences, and says pre-import historical data is not included. Record the actual available interface and destination instead of assuming an old client's import automatically becomes the manager's action.
Some manager-linking help pages still mention Analytics views and Universal Analytics. Use the current GA4 property workflow for GA4; do not recreate a legacy view-based procedure. If permissions or eligibility prevent selection, preserve the exact blocker and ask the account administrator to resolve it.
Step 4: Preserve the transition window without adding everything together#
Create a cutover record with an exact timestamp and timezone. Attach the old and new action identifiers, deployment version, conversion-account setting and relevant windows.
Google's migration instructions retain old tags/actions for the chosen window so conversions associated with earlier clicks are not lost. That is a continuity precaution. It is not permission to add every old and new action count into a new “total purchases” metric.
A universal waiting period is inappropriate: Google's window definition ties eligibility to time after an ad interaction. Your action's configured window and collection source matter. A recommendation to wait 30 days does not prove that all of your relevant windows are 30 days, or that all data is final then.
Keep separate columns for old-action observations, new-action observations and the business-event ledger where you have one. Use restricted, appropriate identifiers in private QA records. Public reporting needs aggregate definitions, not customer-level data.
Step 5: Recheck campaign goals after the switch#
The official cross-account documents warn that switching ownership can move campaigns targeting specific actions onto the manager's default goals. Check the effective goals after the change; a successful collection test does not verify this selection.
For each campaign, answer: does its current goal set still represent the intended business outcome? Have an intermediate action and a completed outcome become mixed? Is a duplicate measurement path now eligible?
Google's primary/secondary reference makes the relevant distinction: primary actions enter the Conversions column and bidding when their standard goal is used; secondary actions ordinarily support observation through All conversions. A secondary action in a custom goal is an exception and can be used for bidding. A secondary label alone is therefore insufficient proof of a safe observation-only setup.
Save the action membership and campaign selection. Keep this audit separate from a recommendation to change bidding strategy or budget; ownership QA cannot establish that such changes will improve results.
A worked reconciliation example#
The following is hypothetical, not an AdProof customer result.
An internal order ledger contains 23 completed orders in an agreed seven-day conversion-time window. A private reconciliation, using legitimate matching evidence, finds 17 observations under an old action and 12 under a new action. Six orders appear in both sets.
| Reconciliation item | Count | Meaning |
|---|---|---|
| Old-action observations | 17 | Matched orders in the old set |
| New-action observations | 12 | Matched orders in the new set |
| Overlap identified independently | 6 | Orders found in both sets |
| Union of matched orders | 23 | 17 + 12 − 6 |
| Naive sum of action observations | 29 | Counts overlapping observations twice |
The overlap is known because this example supplies a matching ledger. You cannot derive six duplicated orders from two aggregate Google Ads totals alone.
Nor does the 23-order ledger prove Google Ads should attribute 23 conversions. Action eligibility, attribution, counting policy and reporting date basis still apply. Keep the business-event union separate from platform conversion credit. Record unresolved unmatched activity rather than forcing the two measures to agree.
This worksheet helps distinguish a migration overlap from an actual increase in completed orders. It does not demonstrate sales uplift or establish that either action is the correct bidding signal.
Step 6: Compare reports on the same basis#
Google directs cross-account users to attribution reports in the manager. Use the selected action set and report controls deliberately. An attribution report's lookback control is distinct from an action's conversion window.
For a before/after export, preserve the account scope, included action IDs, metric column, date basis, timezone, filters and retrieval timestamp. A new manager report may include different accounts or actions than the old client report. A total changing after a switch does not isolate the reason it changed.
Use saved snapshots rather than memory. If counts continue to develop, compare cohorts at equivalent maturity as explained in the measurement reconciliation guide. If offline imports are involved, retain their separate upload-processing and reporting checks.
Acceptance checklist and rollback preparation#
Before declaring the migration complete, retain evidence that:
- Every affected client uses its intended conversion account.
- The correct replacement action receives eligible activity through its actual source.
- Campaign goals were inspected after the ownership change.
- Old and new observations have separate reporting definitions.
- Required transition tracking remains available for the relevant window.
- Any return to client-owned tracking has a tested collection path ready.
A rollback is another ownership change, not just a dropdown reversal. Preserve the prior configuration and check that its required tags still exist before returning to it. Write the retirement date only after reviewing the applicable window and outstanding investigation items.
For a separate delivery baseline, the anonymized fashion-retail measurement case illustrates why measured impressions need their own defined scope. Its delivery finding does not prove conversion attribution or sales performance.
To review supported campaign-delivery evidence alongside your own conversion-account records, discuss the scope with AdProof. Bring campaign identifiers, dates, metric definitions and comparable exports. Google Ads ownership, Analytics imports and campaign-goal configuration must be verified in their owning systems.
Frequently asked questions#
Does linking a client to an MCC automatically migrate its conversions?
No. Audit the client's conversion-account setting, the manager-owned actions and their collection paths, and effective campaign goals. A manager relationship alone does not prove conversion ownership changed.
Can a client use its own conversion actions and a manager's actions simultaneously?
Google documents account-specific or cross-account conversion tracking as alternative arrangements for a client, with one manager supplying its cross-account actions. Preserve existing historical data and treat the transition separately from summing action counts.
Is keeping the new action secondary for 30 days always safe?
No universal 30-day recipe is established by the migration instructions. Inspect the relevant conversion window, source and campaign goals. A secondary action included in a custom goal can still be used for bidding.
Will moving to a manager import all previous GA4 conversion history?
Do not assume that. Google states that historical data from before an Analytics conversion import is not included. Preserve existing reports and verify the actual property link, destination account and creation date for the replacement action.
Check which account owns the conversion action
Cross-account tracking depends on manager links and the selected conversion source. Discuss the account path and reporting scope for your setup.
Discuss a measurement questionA short inquiry to scope relevant options; no campaign access is needed.
