The copied campaign appears in the destination account, but its market, budget, or shared settings may not match.
Fastest fix: Google Ads Editor 2026 can copy campaigns across accounts, but confirm the copy method and destination account first. Then check budget currency, location targeting, shared resources, and the pending-change list before uploading.
This runbook is for cross-border sellers managing campaigns in multiple markets, ad operators who copy and publish in batches, and team leads who need review records that colleagues can pick up across time zones.
Before copying: lock the source, destination, and market
Start with the business decision, not the account name. A familiar account label does not prove that it is the right destination, that it uses the right currency, or that its campaigns target the market you intend to enter.
Write down these items before opening the copy workflow:
- Source account: the account that currently contains the campaign you want to reuse.
- Destination account: the exact account that should receive the copied objects.
- Target market: the country or region the campaign is intended to reach.
- Copy purpose: whether you need to reuse a structure, duplicate a full campaign, or copy only selected settings.
- Reviewer: the person responsible for checking the destination configuration before upload.
How do you copy a campaign to another Google Ads account? Add or open both the source and destination accounts in Editor, select the intended campaign objects, and use the cross-account copy workflow described in Google’s instructions. Before pasting, verify the destination account shown in Editor. If you cannot confirm the target account or market, stop and resolve that ambiguity before copying.
A campaign structure can be reused without making the original targeting or content suitable for a new market. Record the purpose of the copy so a reviewer can distinguish a deliberate market adaptation from an accidental duplicate.
From source download to a reviewable baseline
Download current account data before selecting campaign objects. Otherwise, your local Editor view may not reflect the latest online changes. Google’s account download instructions explain how to download account data into Editor.
Then create a compact baseline that another operator can audit:
- Record the source account and the date you downloaded its data.
- Note the campaign name and the campaign objects selected for copying.
- Capture the relevant campaign and ad group names, ads, and assets.
- Save a screenshot of the account tree and selected objects, with customer or business-sensitive details hidden.
- Record any source settings you already know will need market-specific changes.
This baseline is also useful if you need to undo or investigate a copy. Without it, a reviewer may be unable to tell whether a setting was already present in the destination or introduced by the current change.**Review note:** A screenshot of the selected account tree can help identify what was copied, but it does not prove that the destination settings are correct. Keep a written source-to-destination record as well.
Choose the copy mode before pasting
The copy method affects what arrives in the destination. Decide whether you need a full campaign copy or only a settings shell, then check the result instead of assuming that both methods carry the same configuration.
| Copy choice | Use it when | What to verify in the destination |
|---|---|---|
| Full campaign copy | You need campaign objects such as ad groups and ads as a starting point for a market-specific version. | Confirm that each copied object is intended for the destination, then review targeting, budgets, bidding, assets, and URLs. |
| “Copy shell” or settings-only copy | You want to reuse a campaign framework without treating its original targeting and content as ready to publish. | Rebuild or confirm omitted settings, especially location targeting, and check which objects were actually created. |
| Selected-object copy | You only need specific campaign or ad group objects. | Confirm the selection boundaries and check for dependencies on shared or account-level resources. |
Does Google Ads Editor retain location targeting when you copy a campaign? It depends on the copy method. In particular, location targeting is not included when you use “Copy shell,” so you must inspect and set the intended destination locations yourself. Google also documents how location targeting is handled in Editor.
After pasting, use the destination account as the source of truth. Check that the objects you wanted are present and that the ones you did not intend to copy are absent. If you copied only settings, do not assume ads, assets, or location settings were included.
In the destination: review budget, currency, and bidding
Check the destination account’s currency before comparing any budget with the source. Google Ads Editor does not automatically convert a copied budget amount when you copy between accounts with different currencies; the numeric amount stays unchanged. The official cross-account copy instructions document this behavior.
That means a source budget of one amount in one currency can appear as the same numeric amount in another currency. It is not an exchange-rate conversion or a recommendation for the new market. Recalculate the intended spend separately, then enter a destination-appropriate amount.
What should you check when copying into a Google Ads account with a different currency? Confirm the destination currency, compare the copied budget’s numeric value with the planned spend in that currency, and review campaign and ad group budget settings where applicable. Then verify the bidding strategy and its settings in the destination account. Do not approve the copy just because the copied number matches the source.
Also review bidding rather than assuming the source strategy remains appropriate. Check the strategy selected in the destination, its associated settings, and whether the destination campaign has the information or configuration required for your intended approach. If the visible strategy differs from the plan, pause the upload and get the campaign owner’s decision.
Shared and account-level resources deserve a separate pass. Review any shared budgets, labels, conversion-related choices, or other resources your campaign depends on. Their availability and suitability may be different in the destination account. If a resource cannot be confirmed in Editor, note it as unresolved and continue the review in the online account before publishing.
Before upload: inspect market settings and the change list
Review the target market as a complete bundle. A campaign can have a valid structure but still be wrong for the intended audience because its locations, language, creative, or final URLs were carried over without adaptation.
Use this sequence before uploading:
- Confirm the destination country or region in location targeting. Compare it with the campaign brief, not with the source campaign.
- Check the language settings against the audience and the destination market.
- Review ad text, images, and other assets for source-market references, unsupported claims, or content that needs localization.
- Open the final URLs and verify that they lead to the intended market or store experience.
- Recheck budget currency, amount, and bidding settings after any edits.
- Run Editor’s Check changes function and read the resulting change list, errors, and warnings.
- Correct, cancel, or explicitly approve each proposed change before uploading.
How can you confirm what will upload? Run “Check changes,” inspect the listed additions, edits, and removals, and resolve any errors or unexpected items before you publish. If the list does not match your recorded scope, cancel or correct the operation rather than uploading to discover the difference later.
Use this acceptance matrix to make the upload decision:
| Review item | Pass condition | Hold condition |
|---|---|---|
| Destination account | Account identity matches the handoff record. | Account is uncertain or selected by a similar name alone. |
| Copy scope | Copied objects match the stated purpose and selection. | Unexpected campaigns, ads, or settings appear. |
| Budget and currency | Destination currency and planned spend have been checked. | Source amount has been accepted without destination review. |
| Location and language | Settings match the intended market. | Targeting is missing, inherited, or not confirmed. |
| Assets and URLs | Content and final destinations have been reviewed for the market. | Source-market content or URLs remain unverified. |
| Change list | Every proposed change is understood and approved. | Errors, warnings, or unexplained changes remain. |
**Stop condition:** If the destination account, location targeting, or change list is unclear, do not upload. Save the review record, ask the account owner to resolve the uncertainty, and rerun the check after changes.
After upload: verify the online result and hand off
Uploading changes from Editor does not establish that every item was successfully applied, approved, or shown to users. Check the upload result, then return to the online account to verify the campaign configuration and record anything that still needs attention.
- Read the upload report and identify successful, failed, and pending items.
- Open the destination account online and compare the campaign with the approved change list.
- Recheck the campaign’s location targeting, budget, currency, and bidding settings in the online account.
- Note errors or items that require further action in Editor or the web interface.
- Record the source account, destination account, reviewer, upload outcome, and unresolved issues for the next operator.
For cross-time-zone teams, include a clear handoff: what was copied, what was changed, what was uploaded, what remains unresolved, and who owns the next check. If an item needs online review, state that directly instead of marking the task complete based only on the Editor screen.
If your team repeatedly uses a local laptop or a shared workstation, sleep settings, network changes, and handoffs between operators can interrupt a review or make the working environment less consistent. A remote Mac can provide a managed macOS desktop for temporary campaign work and cross-time-zone handoffs, but it will not correct account settings or replace the checks in this runbook. If you need that setup for a defined period, review MACGPU’s remote Mac access options and the Silicon Valley Mac option to compare available access details before deciding whether a rental fits the work. A rented Mac is less suitable than a dedicated purchase for continuous, heavy workloads or tasks that require physical ports. The Mac’s network location also does not set campaign location targeting; you must configure that in the account and verify it before upload.