Skip to main content

Introduction

Google Search Ads 360 (SA360) is Google’s enterprise search-management platform for running and reporting on paid search campaigns across multiple search engines. The connector imports campaign, ad group, ad, and keyword architecture along with performance reports through the SA360 Reporting API. The SA360 Reporting API is a relatively new API, so occasional changes or unexpected behavior originating from Google’s side are possible. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect Google Search Ads 360 to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets (ad groups), ads, and keywords. It refreshes twice daily, at 4:00 PM UTC and 5:00 AM UTC.

Reports data

Reports include daily performance for ad accounts, campaigns, ad sets, and ads. Real-time. Report data is fetched from Google on demand when a dashboard loads, so the latest values are always visible. On top of that, scheduled cache refreshes keep historical data consistent across multiple time windows. Refresh schedule. Reports refresh on three overlapping schedules, each covering the ad account, campaign, ad set, and ad levels:
  • 5:00 PM UTC daily — syncs the last 9 days
  • 11:40 PM and 6:40 AM UTC daily — syncs the last 3 days
  • 7:30 AM UTC on the 1st and 15th of each month — syncs the last 30 days

Architecture levels

Ad account → Campaign → Ad set (ad group) → Ad → Keyword Keyword-level architecture is not currently available — the connector does not yet fetch keyword rows, and keyword-level conversion reports are skipped to limit data volume. Performance Max campaigns are campaign-level only. At the ad set and ad levels, Adriel creates synthetic rows by copying the campaign-level Performance Max data down, so Performance Max campaigns appear consistently alongside standard ad-set and ad rows.

Date range limits

To keep query sizes manageable, the connector enforces these maximum look-back windows per time breakdown:

Metrics

How to read the columnsThe API Key column shows where a value comes from. Code style like metrics.clicks is the literal SA360 API field name. Italic text describes how a value is produced when it does not map cleanly to a single API field — Adriel-computed rates, cross-connector fallbacks, or aggregated values. The Data type column indicates how the value is formatted.

Reach & impressions

Click performance

Cost & spend

Currency conversionEach ad account’s currency comes from its SA360 settings. When an ad account’s currency differs from the workspace currency, costs are automatically converted using the current day’s exchange rate.

Conversion performance

Any conversion event tracked in the ad account is imported automatically, but it only appears on the dashboard when the underlying event is active in the account.

Custom conversion events

For each imported conversion event, Adriel auto-generates a set of KPIs: These metrics appear in the field picker as Google Search Ads 360: [event_name] and only surface data when the underlying event is active in the account.

Floodlight custom columns

SA360 Floodlight custom columns are user-defined and vary per account, so they cannot be predefined. Adriel discovers them dynamically across the full account hierarchy and exposes each one as a metric under the SA360 Custom Columns category (listed last in the field picker). A Floodlight metric and a Floodlight breakdown cannot be used together in the same query. See Limitations.

Video & engagement

These metrics appear for cross-connector consistency. They are not natively meaningful for search campaigns and typically surface zero for Google Search Ads 360.

Budget & schedule

UTM tracking

Campaign structure metadata

Breakdowns

Standard hierarchy

Demographics

Geographic

Time & device

Floodlight breakdowns

Time & date grouping

The API returns daily records; Adriel groups them into these views for reporting.

UTM tracking

UTM values are parsed by Adriel from each ad’s configuration and landing URL, not returned by SA360.

Limitations

Based on the current connector, Google Search Ads 360 has the following limits:
  • Relatively new API — the SA360 Reporting API is relatively new, so occasional changes or unexpected behavior originating from Google’s side are possible.
  • Keyword level not available — the connector does not yet fetch keyword-level architecture, and keyword-level conversion reports are skipped to limit data volume.
  • One breakdown per query — reports do not support more than one breakdown at a time.
  • Floodlight metric and Floodlight breakdown cannot be combined — using a Floodlight custom-column metric together with a Floodlight breakdown in the same query is not supported and returns an error.
  • Performance Max resolution — data provided by the API for Performance Max campaigns has limited resolution, which may result in missing fields. At the ad-set and ad levels, Performance Max rows are synthesized from campaign-level data.
  • Data truncation — this connector limits the amount of data that can be fetched in a single query, so some data may be truncated. Report queries are capped at 10 pages, architecture at 20 pages, and account-hierarchy traversal at 50 pages. Narrow the date range or query at a higher level to resolve.

API references

See also