Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Programmatic Advertising › Search Ads 360

Moving Paid Search Into Search Ads 360

How to move paid search into Search Ads 360: linking engines and Floodlight, conversion goals, labels and names, the bid strategy handover and reporting.
Tutorialadvanced9 min readUpdated

What moving into SA360 changes and what stays in the engines

The SA360 hub sets out what the layer adds and when it is worth it: more than one engine carrying real spend, Floodlight already measuring other channels, many accounts needing shared governance, campaigns that follow a product feed, or finance wanting one number for search. It also warns that SA360 brings set-up work of its own: engine accounts to link, a Floodlight configuration to connect, sync behaviour to understand, and a second place where a broken setting can hide. This tutorial is that set-up work, in order.

Part of the programmeStays in the enginesChanges with SA360
Campaigns, ad groups, keywords and adsStill live in each engine, which remains the system of recordRead into SA360, reported side by side and editable from it
Account structureEach engine account keeps its native structureGrouped under client accounts, sub-managers and a manager account
Conversion measurementEngine tags can stay in placeFloodlight activities from the linked CM360 advertiser become columns and goals
BiddingEngine bidding stays availablePortfolio strategies can hold campaigns from several engines
Labels and namesNames live on the engine objectsLabels added across engines; names aligned so reports sort the same way
ReportingEngine reports remainCross-engine reports, custom columns and scheduled delivery

The cross-engine management guide explains the relationship: linking an engine account lets SA360 read it and send edits back, the engine is the system of record for what serves, an edit sent to a non-Google engine can be rejected by it, and sync is not instant. Which engines are supported, which features each supports, the sync cadence and which bidding combinations are allowed are set out in the Search Ads 360 Help Centre and change over time, so this tutorial does not list them. The academy capstone on a Google Ads operating plan for a hot tub retailer practises planning a staged move of search into SA360 beside the bidding, measurement and Shopping decisions of the same year.

Before you start

  • The decision in writing: which of the hub's conditions apply, and what the business expects the move to deliver.
  • Admin access to every engine account that will be linked, and the people who manage each one today.
  • Access to the Campaign Manager 360 advertiser that owns, or will own, the Floodlight configuration, and to the site's tag manager.
  • An inventory of conversion tracking: every engine conversion action, every Floodlight activity and which pages each fires on.
  • The current bid strategies on each engine, with their targets and recent results.
  • The naming convention, or the decision to write one, and the dimensions reports must split by.
  • A measurement change log the move can be recorded in.
  • A review calendar with a decision owner for each gate.

The steps

  1. Confirm the case against the conditions the hub sets out

    Write down which of the hub's conditions the business meets and what each should change: one conversion definition across engines, one report for finance, shared governance across markets. Then write down what the move must not make worse, usually the efficiency of the largest Google Ads campaigns. The hub is plain that for a single-engine advertiser with one team Google Ads on its own is the better tool; if the written case rests on nothing more than consolidation, stop here.

  2. Plan the manager, sub-manager and client accounts

    The hub describes the hierarchy: a manager account for administrators, sub-manager accounts for groups such as regions or business units, client accounts holding every engine account for one advertiser along with the CM360 link, bid strategies, labels and conversion goals, and engine accounts beneath them. Draw the tree before creating anything. The client account is the working unit, so decide what one advertiser means for the business: a brand, a market or a business unit with its own conversion tracking. Each Google Ads account inside the tree keeps its own structure, and the Google Ads account structure guide still applies to it. Plan access at the same time, granting at the level each person's work needs, as the cross-engine guide recommends.

  3. Link each engine account and let sync read it

    Link the engine accounts under their client accounts and let sync read them before anyone edits anything from SA360. Check that campaigns, ad groups, keywords, ads and settings appear as they do in each engine, and note anything the engine supports that SA360 only reads or does not show. The cross-engine guide's working rule applies from the first day: sync before any bulk work and before any report that will be acted on. Agree which objects will be edited in SA360 and which in the engine, and never both for the same object.

  4. Link the CM360 advertiser and check Floodlight against engine counts

    Link the client account to the CM360 advertiser that owns the Floodlight configuration. The Floodlight and reporting guide explains how the join works: through the click identifier each engine adds to the landing-page URL, which the Floodlight tag reads when it fires. Check the tags first, then the identifiers: auto-tagging on, tracking templates producing each engine's parameter, no redirect that strips it. Then run Floodlight and engine conversion counts side by side over a complete period and explain the gap cause by cause, using the guide's reconciliation table. Building or redesigning the tags is CM360 work, covered in the Floodlight tags guide; if the configuration was inherited and nobody can explain its activities, the tutorial on cleaning up an inherited Floodlight configuration sorts that out before any bid strategy depends on it.

  5. Choose the conversion goal for each future portfolio

    The bid strategies guide explains that a goal can use Floodlight activities, engine conversions or a combination, and that a goal including both a Floodlight purchase activity and the engine's purchase action counts the same sale twice unless one is excluded. For each portfolio the move will create, choose the activities, confirm the attribution model and lookback window in the Floodlight configuration, and write down the conversion lag to allow for when reading results. The guide is clear that changing any of these later resets what the strategy is learning from, so settle them now. The ROAS calculator helps translate a value goal into the target the portfolio will carry.

  6. Apply labels and a naming convention across engines

    Labels are how SA360 reports, bulk-edits and selects campaigns for a bid strategy across engines. Agree the dimensions that matter, such as brand and non-brand, product line, market and funnel stage, and label every campaign on every engine with them, mirrored campaigns carrying the same label. Align the names too: the naming conventions guide sets out the fields and order, and a naming convention identical on every engine lets the name alone sort and filter consistently. Use bulk routes carefully, syncing immediately before downloading and uploading to one engine account first.

  7. Hand bidding over portfolio by portfolio without two systems on one campaign

    Move bidding in stages, starting where cross-engine bidding and one conversion definition matter most, often non-brand. The bid strategies guide states the rule: a campaign in an SA360 portfolio must not also sit in a Google Ads portfolio strategy, and the Help Centre is specific about which combinations are allowed. So each campaign leaves its engine strategy and joins the SA360 portfolio in the same change, with the target set from what the campaigns achieved before. For Google Ads campaigns SA360 bids at auction time with the signals Smart Bidding uses, as About Smart Bidding and the Smart Bidding guide describe; for other engines it sets bids on a schedule. Expect a learning period after each handover, and do not change the portfolio again until it has passed. Campaigns the business is content to leave on engine bidding can stay there.

  8. Rebuild reports and schedules on the new basis

    Rebuild the reports the business relies on inside SA360: cross-engine reports with engines as rows, custom columns built from Floodlight and engine columns, and scheduled delivery to the people who read them. Define each KPI once, on the same conversion basis on every engine, so that nobody compares a Floodlight figure on one engine with an engine-tag figure on another. Record the expected gap between SA360, each engine and the analytics tool; the comparison of Google Ads and Google Analytics numbers walks through the analytics side, and the same logic applies to SA360 with one extra step for cross-engine attribution. Keep the old engine reports running until the new ones have been checked against them.

  9. Review at agreed gates and record every change

    Treat each stage as a phase-gate review: before it begins, write down what the next review must show for the move to continue, hold, change course or stop, and who decides. Judge each portfolio after its learning period, over a window long enough for Floodlight conversions to have arrived, and on the same attribution basis as its goal. Record every change to tags, goals, attribution, windows, labels and bid strategies in a measurement change log, so that a later step in a report can be traced to the change that caused it rather than to the market.

Once the last portfolio has passed its gate, the programme runs on the routines the SA360 guides describe: sync habits and change history reviews from the cross-engine guide, learning and evaluation from the bid strategies guide, and reconciliation from the Floodlight and reporting guide.

A car leasing broker moves search in stages (illustrative)

Illustrative example — not a real result

Hazquorel Car Leasing moves search into SA360 in stages

Hazquorel Car Leasing, an invented car leasing broker, spends about £85,000 a month on search: £68,000 in Google Ads and £17,000 in Microsoft Advertising, with a separate conversion tag on each engine and different lookback windows. Display already runs through DV360 with Floodlight on the enquiry and credit-check pages.

StageWhat happensGate
Weeks 1 to 21 client account; both engine accounts linked and synced; the CM360 advertiser linkedEvery campaign visible as in the engines
Weeks 3 to 4Floodlight enquiries checked against engine counts for a fortnight: Floodlight 1,140, engines combined 1,290Gap of 150 explained: 95 counted by both engines, 40 from a redirect stripping the Microsoft identifier, 15 from window differences
Week 5Labels for brand, non-brand and vehicle type on all 64 campaigns; names alignedCross-engine report splits correctly
Weeks 6 to 941 non-brand campaigns move from engine bidding to 1 SA360 portfolio with a target cost per enquiry of £58Cost per enquiry within 10% of target after learning
Weeks 10 onwardsBrand campaigns stay on Google Ads biddingReviewed after 3 months

The redirect is fixed in week 4 before any portfolio depends on Floodlight. In weeks 6 and 7 cost per enquiry runs at £66 while the portfolio learns; by week 9 it is £57 across both engines, and Microsoft's share of enquiries has risen from 19% to 23% because the portfolio now bids both engines towards one goal. Every change sits in the measurement change log, and the monthly report that used to take a day of stitching is now a scheduled cross-engine report.

Common mistakes

  • Moving without a written case. For a single-engine advertiser with one team, SA360 is extra work without the gain.
  • Editing before the first sync. SA360 shows only what sync has read; the engine is the system of record.
  • Bidding on Floodlight before checking it. A missing click identifier or a stripped parameter makes conversions invisible to SA360.
  • Counting the same sale twice. A goal holding both a Floodlight activity and the engine's conversion for the same action double-counts.
  • Two bidding systems on one campaign. A campaign leaves its engine portfolio strategy before it joins an SA360 one.
  • Moving every portfolio at once. Stages with gates show which handover worked.
  • Judging inside the learning period. Conversion lag and learning make the first days unreliable.
  • Reports on mixed bases. A KPI defined differently on each engine compares nothing.
  • No change log. Without one, a step in a report cannot be told apart from a change in the market.

Frequently asked questions

Do our campaigns have to be rebuilt to move into SA360?

No. SA360 sits above the engine accounts: linking an engine account lets SA360 read its campaigns, ad groups, keywords, ads and settings and send edits back, while the engine remains the system of record for what serves. The work of the move is in the layer itself, the account hierarchy, the Floodlight link, conversion goals, labels, bid strategies and reports, not in recreating campaigns.

Should every campaign move to an SA360 bid strategy straight away?

No. Hand bidding over portfolio by portfolio, starting where cross-engine bidding and one conversion definition matter most, and judge each stage after its learning period before the next one moves. Some campaigns may be better left on the engine's own bidding. The rule that never bends is that a campaign is not bid by two systems at once, so each campaign leaves its engine portfolio strategy before it joins an SA360 one.

Why do SA360's conversion figures differ from the engines' after the move?

Because they count on a different basis. SA360 can use Floodlight conversions credited across engines under one attribution model and the lookback window set in the Floodlight configuration, while each engine credits its own clicks under its own settings, and Floodlight conversions arrive after a delay. Record the gap during the move, explain it cause by cause, and rebuild reports and targets on one basis rather than mixing the two.

Terms used on this page

Tools to try

Frameworks

Where this page is used

Part of these learning paths

Sources

  1. Search Ads 360 Help — Google
  2. Campaign Manager 360 Help — Google
  3. About Smart Bidding — Google Ads Help

Related