Check Google Ads Import Collisions in Microsoft Advertising
Before a first Google Ads import, inventory the campaigns in both accounts and compare campaign names without regard to capitalization. If a Google campaign matches a manually created Microsoft Advertising campaign, pause and resolve the possible collision before importing: Microsoft says the campaigns can merge and become permanently linked. That first-import situation is different from a later update to a campaign already linked through an earlier import.
Why a name match needs attention
Microsoft’s What Gets Imported from Google Ads explains that a Google Ads campaign not previously imported can merge with an existing Microsoft Advertising campaign that was not created by an import when their names match. The campaigns are then permanently linked, and later imports of that Google campaign update its corresponding Microsoft campaign. Microsoft documents campaign-name matching as case-insensitive, so capitalization alone does not distinguish two campaigns.
Hypothetical example: Your Google Ads account has a campaign named “Spring Leads,” while your Microsoft Advertising account has a manually built campaign named “spring leads.” Treat these as a possible match, even though the capitalization differs. Pause before the first import and decide how to avoid joining the Google campaign to the existing Microsoft campaign unintentionally.
Microsoft also warns that import effects can include changes to bids, budgets, settings, or campaign status, such as pausing, removal, or renaming. Those are possible effects that depend on the import and its settings—not a claim that every import changes every existing campaign. The same Microsoft Help page recommends reviewing the import summary and checking campaign status, including active, paused, and deleted campaigns.
Preflight the first import
- Confirm the accounts and campaign scope. Identify the Google Ads source account, the intended Microsoft Advertising destination account, and the campaigns you actually intend to bring over. Check the destination account in the import workflow before starting.
- Compare campaign names case-insensitively. Review source and destination campaign lists for matching names, including differences that are only capitalization. Identify which destination matches were created manually.
- Pause on a manual match. Decide whether to resolve the collision before proceeding. Renaming one campaign may be a cautious operational way to make the names distinct, but Microsoft’s cited guidance does not establish a particular renaming procedure as a guaranteed way to prevent a match. After any change, verify the names shown in the import flow and destination account; if the match is still unclear, do not proceed on the assumption that capitalization or renaming alone made the import safe.
- Limit the import to the intended campaigns. Where the chosen workflow allows campaign selection, select only the campaigns needed for this import. Microsoft’s Google Ads Import guide documents selecting campaigns and customizing import options; check the controls actually available in your current workflow, because labels and options may differ.
- Inspect what the import can update or remove. Review the available settings for updating existing items, campaign budgets, and deletion of items removed from Google Ads. In the API guide,
UpdateCampaignBudgets=falseis the documented option for avoiding updates to existing campaign budgets. The guide also documentsDeleteRemovedEntities=trueas an option that deletes items removed from Google Ads. Do not enable deletion or budget updates without understanding how the setting applies to the items in scope. - Choose the run schedule deliberately. Confirm whether you are setting up a one-time or recurring import. A recurring job can run again with its configured options, so inspect the schedule and update behavior before you authorize another run.
Choose a path based on the import history
| Situation | What to check | Decision |
|---|---|---|
| First import into an account with manual campaigns | Case-insensitive name matches, source campaign selection, destination account, and available update, budget, deletion, and schedule settings | Pause on a matching manual campaign. Resolve and verify the collision before importing; limit the scope to the campaigns you intend to import. |
| Recurring import with campaigns already linked by an earlier import | Which linked campaigns will update, whether budgets can change, whether removed Google Ads items can be deleted, and when the next run will occur | Allow the next run only after reviewing its settings and scope. Pause or adjust the job if its next run should not make those changes. |
Microsoft describes selecting “Items not previously imported” for future imports to avoid overwriting existing campaigns. Do not treat that selection as proof that a first-import, same-name match with a manual campaign cannot merge: the cited guidance does not establish it as a safeguard for that situation. Check for the name collision separately.
Verify the result before the next run
After the import, review its summary and any error logs. Then search the destination account’s active, paused, and deleted campaign views. Compare the relevant campaigns’ names and statuses with your pre-import inventory, and check the before-and-after budgets and bids for changes. If you set up a recurring import, confirm whether it remains scheduled, when its next run is due, or whether it has been paused. Microsoft’s API guide notes that results can include multiple runs of a recurring job, so identify which run you are reviewing.
For API-created jobs, Microsoft’s AddImportJobs reference identifies the CustomerAccountId header as the way to specify the destination Microsoft Advertising account. That is an API configuration detail, not a substitute for confirming the destination shown in a UI import workflow.
A sandbox test is not documented here as proof that every production account’s existing-campaign collision conditions have been reproduced. Use it as an additional check if available, not as a reason to skip the production account’s name and settings review. And treat a successful import status as evidence about the import job—not as evidence of campaign performance or business results.
If you want help reviewing a paid-search account workflow and keeping its setup and measurement organized, Splinternet Marketing’s services connect businesses with Brian Bateman’s consulting, supported by DOYJO technology. We can help inspect the import plan, document the intended settings, and track what changed so the next decision is based on account evidence.
Sources
Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.
