Why is keyword-level data not showing for my Google Search Ads 360 source?
Keyword-level reporting is not currently available for this connector. The SA360 data source imports ad account, campaign, ad set (ad group), and ad architecture, but it does not yet fetch keyword rows, and keyword-level conversion reports are skipped to keep data volume manageable. Keyword text still appears as a field on Search campaigns for reference, but a widget cannot break down or report performance at the individual keyword level. To analyze performance, report at the ad, ad set, or campaign level instead.Why do some Performance Max rows have missing fields?
Performance Max campaigns are campaign-level only in SA360. At the ad set and ad levels, Adriel creates synthetic rows by copying the campaign-level Performance Max data down, so these campaigns appear consistently alongside standard ad-set and ad rows. Because Performance Max data provided by the API has limited resolution, some fields can be empty on those rows. This is expected. For the most complete Performance Max figures, report at the campaign level rather than the ad set or ad level.Why do I get an error when combining a Floodlight metric with a Floodlight breakdown?
SA360 Floodlight custom columns can be used either as a metric or as a breakdown, but not both together in the same query. Requesting a Floodlight custom-column metric alongside a Floodlight breakdown returns an error and no data. To resolve it, keep the two apart: use a Floodlight custom column as the metric with a standard breakdown (for example, campaign or ad set), or use a Floodlight breakdown together with standard metrics such as conversions or spend. Splitting the request across two widgets is the usual workaround when both views are needed.Why can I only apply one breakdown at a time on Google Search Ads 360?
SA360 report queries support a single breakdown per query. Applying more than one breakdown to the same widget is not supported and returns an error. To see two perspectives at once, use separate widgets — one per breakdown — rather than stacking breakdowns in a single widget.Why does my Google Search Ads 360 data occasionally look unstable or incomplete?
Google currently flags the SA360 Reporting API as v0 (Beta). As a result, occasional instability or unexpected behavior originating from Google’s side is expected, and values may shift between refreshes as the source settles. Separately, this connector caps how much data a single query can return, so very large requests can be truncated. Narrowing the date range or reporting at a higher level (for example, campaign instead of ad) keeps each query within those limits and returns complete results. Each time breakdown also has a maximum look-back window, listed in the data reference. If a genuine error persists after narrowing the query, emailsupport@adriel.com with the affected dashboard URL and the SA360 ad account ID.
Related
Google Search Ads 360 data reference
Metrics, breakdowns, refresh cadence, and limits for the connector.
How to connect Google Search Ads 360
Steps to authorize and connect the data source to Adriel.
Google Ads FAQs
Common questions and expected behaviors for the Google Ads data source.
Data history and retention
How Adriel imports and caches historical data over time.