What SA360 adds to the engines
Every search engine has its own interface, its own automated bidding and its own conversion tracking. An advertiser running Google Ads and Microsoft Advertising for the same business therefore has two of everything: two places to build campaigns, two bidding systems that know nothing of each other, and two conversion counts that both claim the same sales. Search Ads 360 sits above the engine accounts and replaces that duplication with one working surface.
Four things come with the layer.
- One hierarchy. Engine accounts are grouped under client accounts, which sit under manager accounts, so a team sees one brand's search activity in one place whichever engine delivers it.
- Cross-engine bidding. A bid strategyThe rule an ad platform follows to set the bid in each auction. can hold campaigns from more than one engine and optimise them towards one goal, which no engine's native bidding can do on its own.
- Floodlight measurement. Conversions recorded by Floodlight tags from Campaign Manager 360 are joined to search clicks from every engine, so there is one conversion definition instead of one per engine.
- Cross-engine reporting. Columns, custom metrics, dashboards and scheduled reports that treat engines as rows in one table rather than as separate exports to be stitched together.
Two things it does not do. It does not replace the engines: campaigns still run inside Google Ads or Microsoft Advertising, and SA360 pushes edits to them and reads their data back. And it is not a programmatic buying tool. It lives in the programmatic hub because it shares the Floodlight and reporting infrastructure of the Google Marketing Platform with Campaign Manager 360, not because search is bought through an exchange.
The current experience is a rebuild on Google Ads infrastructure. The previous version had its own interface, its own vocabulary (agencies and advertisers rather than manager and client accounts) and features that were redesigned or dropped in the move. The help centre documents the current behaviour, and this section describes that version; where a feature behaved differently before, the guides say so rather than carrying the old name forward.
The account hierarchy
The hierarchy is the first thing to understand, because permissions, bid strategies, Floodlight links and reports all attach to a specific level.
| Level | What it holds | Who works there | Nearest Google Ads idea |
|---|---|---|---|
| Manager account | Sub-manager and client accounts, shared users and access | Agency or enterprise administrators | Manager account |
| Sub-manager account | A group of client accounts, such as a region or business unit | Regional leads; finance for roll-up reporting | A nested manager account |
| Client account | Every engine account for one advertiser, the link to a CM360 advertiser for Floodlight, bid strategies, labels and conversion goals | The team running that advertiser's search | A single account, but spanning engines |
| Engine account | One account on one engine: Google Ads, Microsoft Advertising, Yahoo! Japan Ads and the others the help centre lists | Specialists for that engine | The Google Ads account itself |
| Campaign, ad group, keyword, ad | The objects that exist in the engine, read into SA360 and editable from it | Campaign managers | The same objects |
The client account is the working unit. It is where the Floodlight configuration is linked, where bid strategies are created, and where a cross-engine report naturally starts. Engine accounts beneath it keep their native structure, so the advice in the Google Ads account structure guide still applies to each Google Ads account inside SA360; what SA360 adds is a consistent way to see and edit the same structure on every engine. The cross-engine management guide covers sync, what can be edited at each level, labels, templates and inventory-driven campaigns.
Bid strategies in brief
An SA360 bid strategy is a portfolio. It is created once at client-account level, given a goal and optional constraints, and campaigns from any engine account under that client are assigned to it. For Google Ads campaigns the help centre documents that bids are set at auction time with the same signals Google Ads Smart Bidding uses. For other engines, SA360 sets bids through the engine's interface on a schedule rather than inside each auction, a documented difference that matters when results across engines are compared.
The goals are the familiar ones: conversions with an optional target cost per acquisition (CPACost of each conversion.), conversion value with an optional target return on ad spend (ROASRevenue generated per unit of ad spend.), and clicks for campaigns that have no conversion goal. The conversions a strategy optimises towards can come from Floodlight activities, from the engine's own conversion tracking, or from a combination, which is where SA360 bidding differs most from a single engine: one definition of a conversion, applied to campaigns on every engine in the portfolio.
The bid strategies guide covers goals and constraints, how portfolios behave across engines, building conversion goals from Floodlight, the learning period and target changes, and when engine-native bidding is the better choice. The Smart Bidding guide in the Google Ads section is the comparison point.
Floodlight and reporting in brief
Floodlight is the conversion tagging system of Campaign Manager 360. A client account in SA360 is linked to a CM360 advertiser, and the Floodlight activities configured there become conversion columns in SA360 reports and conversion goals for bid strategies. The join works through the click identifiers the engines add to landing-page URLs, so the same tag on an order confirmation page counts a sale whichever engine delivered the click, under one AttributionAssigning conversion credit to touchpoints. model and one lookback window set in the Floodlight configuration. Building the tags is CM360 work, covered in the Floodlight tags guide.
Reporting sits on top of that join. Engine columns and Floodlight columns appear side by side, custom columns are built from them, reports and dashboards span engines, and scheduled delivery sends them out without anyone exporting by hand. Reconciling SA360's conversion count with what each engine reports, and with what the analytics tool reports, is a recurring task with a known list of causes. The Floodlight and reporting guide covers the columns, the reports and the reconciliation.
When SA360 is worth it
SA360 is licensed as part of the Google Marketing Platform and 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. The gain has to justify that. It usually does when several of the following are true.
- More than one engine carries real spend. The cross-engine bid strategies and reports are the core of the product; an advertiser on Google Ads alone uses almost none of them.
- Floodlight already measures the other channels. If display and video run through CM360 or DV360, measuring search with the same tags gives one conversion definition across the whole plan.
- Many accounts need shared governance. Agencies and multi-market advertisers get the manager and sub-manager hierarchy, shared access control and roll-up reporting.
- Search campaigns follow a product feed. Inventory-driven campaigns that generate and pause ads as stock changes are an SA360 feature, not an engine one.
- Finance wants one number for search. A single report across engines, built once and scheduled, removes a monthly stitching job.
Google Ads on its own gives Smart Bidding, conversion tracking, custom columns and scheduled reports without the extra layer, and for a single-engine advertiser with one team it is the better tool; the Google Ads guide covers it end to end. SA360 earns its place when the duplication across engines is the problem, not when it is a trophy. Once the business has decided the move is worth it, the tutorial on moving paid search into Search Ads 360 puts that set-up work in order, from linking engines and Floodlight to the bid strategy handover and reporting.
A retailer deciding whether to move search into SA360
A homewares retailer spends about £140,000 a month on paid search: roughly 85% in Google Ads and 15% in Microsoft Advertising, across the UK, Ireland and Germany. Display and video already run through DV360 with Floodlight tags on the order confirmation page. The team's monthly report takes two days because Microsoft conversions are tracked by a separate tag with a different lookback window, so the two engines' figures are never on the same basis. Moving search into SA360 lets the same Floodlight sales tag count every order whichever engine delivered the click, puts the three markets under one client account with sub-manager roll-ups, and allows a single target ROAS portfolio of 450% to hold both engines' non-brand campaigns. The set-up takes six weeks, mostly spent verifying click identifiers on the Microsoft side; the monthly report then takes an hour.
Further guides
Further guides cover the move itself:
- Moving paid search into Search Ads 360 — a tutorial that sequences the move as decisions rather than a migration of campaigns: the account hierarchy, engine links and a first sync, the link to the Campaign Manager 360 advertiser with a check of Floodlight against engine counts, conversion goals, labels and names that match across engines, a bid strategy handover that never leaves a campaign under two bidding systems at once, rebuilt reports and review gates.
Common SA360 problems
Most SA360 problems show up as one of a few symptoms, and each belongs to one of the core guides.
| Symptom | Usual cause | Guide |
|---|---|---|
| An edit made in the engine is not visible in SA360 | Sync has not run, or the setting is one the engine owns and SA360 only reads | Cross-engine management |
| Microsoft campaigns in a portfolio trail the Google campaigns | Bids pushed on a schedule rather than at auction time; thinner conversion data | Bid strategies |
| A bid strategy spends well below budget | Target too tight for the auctions available; bid limits constraining it | Bid strategies |
| Floodlight conversions lower than the engine's own count | Attribution model, lookback window, click identifier mismatch or tag placement | Floodlight and reporting |
| SA360 and the analytics tool disagree | Different counting rules and attribution on each side | Floodlight and reporting, Google Ads and GA4 comparison |
| Objects named differently on each engine, reports impossible to segment | No label or naming discipline across engines | Cross-engine management |
| Inventory campaign shows ads for out-of-stock items | Feed not refreshing or template rules not matching the feed | Cross-engine management |
The pattern across all of them is that SA360 adds a layer, and a layer adds a place for a mismatch between what the engine does and what SA360 believes it does. The guides are organised around those mismatches: how objects stay in sync, how bids are set per engine, and how conversions are counted.
