Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Google Ads does not provide a documented, one-click report that places search terms beside the responsive search-ad combinations that served. To build that view, export or query the search-term data and the responsive-search-ad combinations data, standardize their dimensions, and join them in a reporting layer. The result can show the demand that entered auctions alongside the headline and description assets that actually appeared.
What each Google Ads report tells you
Search-term and search-term insight data
Search-term reporting identifies the queries that triggered ads and their associated performance. The campaign_search_term_insight resource groups campaign search demand into categories rather than presenting every query as a single raw-text row. Google’s field reference says historical data for this resource is available from March 2023.
Responsive search-ad combinations
A responsive search ad (RSA) can contain up to 15 headlines and four descriptions. Google’s system assembles eligible assets into different combinations, adapts them to customer searches, and learns which combinations are most relevant over time. The combinations report lists combinations that were served and the impressions they received.
For API-based reporting, ad_group_ad_asset_combination_view exposes the served assets and impression metrics for an ad-level combination. The interface also supports CSV and PDF downloads, so an external spreadsheet, database, or dashboard can consolidate both report types.
#1 Best Overall
Why the reports cannot be merged directly in Google Ads
The two views have different grains. A search-term row describes demand, while a combination row describes creative assets served by an RSA. Google documents them as separate reporting surfaces. A combined report is therefore an analyst-built join, not a native Google Ads report. The exact metrics available depend on the selected API resources and the account’s configuration.
Recommended combined-report schema
Use one row per observed search-term or search-term category, ad combination, and date at the most detailed grain that both sources support. Keep a source marker so users can distinguish a demand record from a creative-combination record.
| Column | Purpose |
|---|---|
source_view or source_resource |
Identifies search-term data versus combination data. |
| Campaign ID and campaign name | Provides the campaign-level join key and readable label. |
| Ad-group ID | Connects demand and creative records within the campaign. |
| Ad ID and responsive-ad resource | Identifies the RSA when ad-level data is available. |
| Date | Sets the reporting period and prevents mixing unlike time ranges. |
| Search term or search-term category | Describes the query demand represented by the row. |
| Served headline assets | Stores the headline text or asset identifiers in the observed combination. |
| Served description assets | Stores the description text or asset identifiers in the observed combination. |
| Impressions, clicks and cost | Shows delivery and traffic performance where the source supplies each metric. |
| Conversions and conversion value | Preserves outcome metrics when configured and returned by the source. |
| Efficiency metrics | Calculates measures such as cost per conversion only when the underlying values are comparable. |
Step-by-step: build the unified report
- Set a common date range. Record the account, campaign scope, time zone and date range used for both extracts. Do not combine a search-term export from one period with a combinations export from another.
- Export or query search demand. Download the relevant search-term report from Google Ads, or query the campaign search-term insight resource through the Google Ads API. If you use category data, label it as a category rather than implying it is an exact query.
- Export or query RSA combinations. Download the responsive-search-ad combinations report, or query
ad_group_ad_asset_combination_view. Preserve the served headline and description assets, impression counts, and any other metrics returned for the selected dates. - Normalize names and types. Convert campaign and ad-group identifiers to the same data type, standardize date formatting, trim text fields, and use consistent names for impressions, clicks, cost, conversions and conversion value. Keep IDs as the primary keys; names can change.
- Define the join keys. Join on the dimensions genuinely shared by both datasets, normally campaign ID, ad-group ID, ad ID or responsive-ad resource, and date. Add other shared dimensions only when they are present and defined identically in both sources.
- Retain unmatched records. Use a full or explicitly documented outer-join strategy. Put search-term rows without a matching combination and combination rows without a matching search-term record into an exceptions view instead of silently discarding them.
- Present demand and creative together. Show the search term or category, served headline and description assets, delivery metrics, and outcome metrics in the same analytical view. Keep the original source marker and resource identifiers for auditability.
- Add a data note. Record the API version, report names, extraction timestamp, date range, account time zone and any fields unavailable in the account. Google’s interface and API field availability can change.
How to read the combined output
Compare intent with the assets that served
Useful comparison axes include search intent or category, the served headline/description combination, impressions, clicks, cost, conversions, conversion value and cost per conversion. This lets a marketer inspect whether particular creative assets appeared alongside different types of demand.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep aggregation boundaries clear
Do not add combination impressions to search-term impressions unless the dimensions and definitions make the totals additive. A dashboard can show both aggregates and a detailed joined view, but it should identify which figures come from which source and avoid presenting duplicated metrics as a single account total.
Important interpretation limits
A high-impression combination is evidence that the combination was served often, not proof that it caused conversions. Conversion conclusions depend on the account’s conversion setup, attribution model, selected dates and other campaign conditions.
Google warns that the combinations report should not be used to create static versions of responsive search ads because those fixed ads are not guaranteed to perform the same way. The report describes observed delivery; it does not establish a causal test of one immutable ad against another.
Rank #4
Availability and date considerations
Google’s documentation states that historical campaign_search_term_insight data is available from March 2023. Google Ads Help also states that full performance statistics for the ad-level asset report are available for dates on or after June 5, 2025. Older periods may therefore have different fields or less complete performance data. Check the returned schema and document gaps rather than filling unavailable cells with estimates.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Best Value
Common failure points
- No matching rows: Verify that campaign, ad-group, ad and date values use identical IDs and time zones. A name-only join is unreliable.
- Duplicate totals: Check whether one search-term row maps to multiple combinations or whether a combination row is repeated for several dates before summing metrics.
- Missing conversions: Confirm that the chosen resource exposes conversion fields for the account and that conversion tracking was active during the period.
- Category mistaken for query text: Label
campaign_search_term_insightoutput as grouped search demand; do not present categories as exact user searches. - Asset text changes: Retain asset IDs or the responsive-ad resource in addition to text so later edits do not make historical rows ambiguous.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
