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

Glossary term

SA360

Enterprise search campaign management.
Search Ads 360Ad TechtechnologyUpdated

Definition

Search Ads 360 is described in its help centre as a platform for managing search campaigns across multiple engines and media channels from a single interface. The core distinction is between an engine account, the Google Ads or Microsoft Advertising account where the campaign actually runs, and the SA360 client account that links to one or more engine accounts, synchronises their campaigns, ad groups, keywords and ads, and lets changes be made in either place. Above client accounts sit manager accounts, and sub-manager accounts beneath them, which give an agency one view across its clients. The registry one-liner covers the purpose: managing and bidding across multiple search engines at scale. The SA360 hub covers the platform and the cross-engine management guide explains the day-to-day workflow.

How it works

SA360 synchronises with each engine on a schedule, pulling in structure and performance data and pushing edits made in SA360 back to the engine. On top of that mirror it adds four capabilities. Bid strategies are portfolio strategies that can span campaigns across engines, bidding toward a target such as cost per action or return on ad spend using conversions that SA360 measures itself or imports. Floodlight conversion tracking, shared with Campaign Manager and Display & Video 360, gives one conversion definition across search and programmatic, with the option to import engine conversions or offline data. Budget management plans and paces spend across campaigns. Reporting places engines side by side, adds custom columns and formulas, and feeds scheduled reports and the platform's data exports. Inventory-driven campaign templates, labels and bulk editing handle large accounts.

CapabilityThe engine aloneWith SA360
Campaign managementOne engine per interfaceSeveral engines, one interface, bulk edits
BiddingEngine strategies within one accountPortfolio strategies across engines and accounts
Conversion trackingEngine's own tag or importFloodlight shared with display and video, plus engine conversions
ReportingEngine reportsCross-engine reports, custom columns, platform exports
BudgetsPer campaign in the engineBudget plans and pacing across campaigns

Google documents which engines are supported, how often sync runs, which campaign types sync fully and what each bid strategy optimises toward; the help centre is the reference for the current lists rather than this page.

In practice

The value of SA360 scales with the number of engines and accounts. A single Google Ads account gains little beyond Floodlight consistency with a display programme; an agency running search for many clients across Google and Microsoft, with offline conversion data to feed back, gains a bidding layer that treats the engines as one market and a reporting layer that needs no spreadsheet stitching. Clients that use Campaign Manager for display usually adopt SA360 so that search conversions and display conversions are counted by the same Floodlight tags. The Google Ads hub covers what happens inside the engine itself; SA360 is the layer above it.

Illustrative example — not a real result

One bid strategy across two engines

A travel agency runs 42 campaigns in Google Ads and 38 mirrored campaigns in Microsoft Advertising. In SA360 it links both engine accounts to one client account, defines a Floodlight activity for completed bookings with the booking value, and creates a portfolio bid strategy with a target ROAS of 650% across all 80 campaigns. Over the first month the strategy shifts budget towards Microsoft on weekday mornings, where bookings are cheaper, and SA360's cross-engine report shows a combined £412,000 in booking value on £61,000 of spend, a ROAS of 675%, against 610% the previous month when each engine ran its own target. Offline cancellations are imported weekly so the strategy bids on net bookings, not gross.

What it is not

SA360 is not a search engine or an ad network: it owns no inventory and serves no ads; every impression is still bought in Google Ads, Microsoft Advertising or another supported engine. It is not Google Ads Editor or a bulk-upload tool, although it does bulk editing; the difference is the persistent sync, the bidding and the measurement. It is not a replacement for engine-native features, which SA360 reports on but configures only to the extent the help centre documents for each campaign type. It is not Campaign Manager or Display & Video 360, though it shares Floodlight with both, and it is not a bid management tool that works without conversion data: its strategies need a conversion signal, from Floodlight or from the engines, before they can do anything useful.

CM360 is the measurement sibling: a Floodlight configuration created in Campaign Manager is the conversion source SA360 bid strategies use, and the two products appear together in most platform contracts. The targets those strategies optimise toward are the familiar efficiency metrics: CPA for lead and sign-up objectives, and ROAS for revenue objectives where Floodlight passes the transaction value. Google Ads and Microsoft Advertising are the engines beneath; their own automated bidding exists in parallel, and an account should not run both an engine strategy and an SA360 strategy on the same campaign. Display & Video 360 is the programmatic sibling whose audiences and conversions SA360 can share, which is what lets a search campaign bid on users who were first reached by a display flight.

Common mistakes

  • Running engine bidding and SA360 bidding on the same campaigns. Two optimisers fight; pick one.
  • Launching a bid strategy without enough conversions. It needs a signal; start with manual bids or a less ambitious target until data accumulates.
  • Editing in both the engine and SA360 without a rule. Sync resolves conflicts in ways teams do not expect; agree where edits happen.
  • Mixing conversion sources. Floodlight and imported engine conversions count differently; the strategy's goal should name one.
  • Adopting SA360 for one small account. The overhead outweighs the gain; it is built for scale.
  • Treating the sync as instant. Changes and data take time to flow; reports and engine screens will disagree for a while.
  • Leaving engine conversions and Floodlight both counting in reports. The same booking appears twice; pick the column the business reads.

More terms to look up

Where this term is used

Sources

  1. Search Ads 360 Help — Google

Related