How to Set Up Google Ads Search Terms Report Correctly

To set up the Google Ads Search Terms Report correctly, validate the question and scope before changing the view, choose a date range that includes conversion lag, keep the matching Keyword and Match type visible, test the conversion and quality fields, and confirm the privacy and action limitations. A report is not correct merely because it contains rows; it must represent the intended campaign and support a decision the account can safely apply.

The regular Search Terms Report shows searches that triggered ads and met Google’s reporting thresholds. Search Terms Insights groups additional demand into themes and subthemes. They serve different purposes and may not reconcile exactly. Use Google’s official Search Terms Report guidance when the interface changes. For the broader operating framework, read Google Ads Search Terms Report best practices.

Validate the question and reporting boundary

Write the decision the report should support: exclude irrelevant traffic, find new demand, compare match behavior, improve ad or page language, investigate a device or network, or review qualified outcomes. Choose the smallest scope that can answer it. Account scope is useful for universal themes; campaign scope protects budget and objective boundaries; ad-group scope tests keyword, ad, page, and intent alignment.

Check that the campaign, ad group, account, network, location, language, and date range in the interface match the question. A report can look plausible while combining brand and non-brand campaigns, prospecting and remarketing, or different conversion goals.

Assign an owner who can apply or approve the possible outcome. A correct report may result in a keyword, negative keyword, ad, landing-page, tracking, budget, or no-change decision. Record the owner and next review before exporting data.

Verify the regular report versus insights

Use the regular Search Terms Report for individual exposed searches, the matching keyword, match type, campaign, ad group, and row-level outcomes. Use Search Terms Insights for grouped categories and subthemes that help explain broader demand, including some low-volume activity not shown individually.

Do not use Search Terms Insights as if it were a row-by-row replacement for the report. Privacy aggregation, conversion processing, and theme-label history can produce different totals. Name the primary surface in the review note.

Configure and test the date range

Choose a range with enough impressions, clicks, and conversions for the question and the campaign’s normal conversion lag. Do not use today or a partially processed day as the final evidence. For a low-volume campaign, extend the range or label the result directional rather than manufacturing certainty.

Record the time zone, start date, end date, and any excluded periods. Annotate promotions, budget changes, bid-strategy learning, tracking releases, landing-page outages, seasonal effects, and policy changes. If the report is being used to judge a setting change, save the before-state and effective date.

Check lag before calling a query waste

A search with no recorded conversion may be too new, have a long sales cycle, or be affected by consent or import delay. Compare raw conversions with qualified stages, revenue, or customer quality where reliable. A query that clearly violates the offer or policy can be excluded promptly, but ordinary performance decisions need enough evidence.

Configure columns and confirm their meaning

Add the fields that explain the search and the action:

Search term;
Keyword;
Match type;
Campaign and Ad group;
impressions, clicks, click-through rate, cost;
conversions, conversion rate, conversion value, and efficiency;
qualified outcomes, revenue, margin, device, location, network, or landing page when relevant.

The Keyword column identifies the account keyword that matched the search and may not be visible by default. The Match type column describes how closely the query relates to the account keyword; it is not necessarily identical to the keyword’s configured type. Check the current Google Ads help if the label or placement differs.

Test the columns against a known row

Find a row whose matching campaign, ad group, keyword, and outcome you understand. Confirm that the Search term is the user’s query, Keyword is the account term, Match type reflects the relationship, and cost and conversion fields belong to the same scope and date range. If the row cannot be explained, pause the export and verify the view rather than assuming the table is correct.

Apply segments and filters without hiding evidence

Use one segment at a time to answer a specific question:

time for trends or a post-change pattern;
conversions for outcome-producing versus traffic-only searches;
device for mobile and desktop journey differences;
network for partner or other inventory quality differences.

Keep an unsegmented baseline and remove filters before closing the review. A filter that finds costly rows is useful; a filter that hides all low-volume or no-conversion rows before classification is not. If a pattern appears only on a device, location, network, or schedule, test the page, form, call, eligibility, and tracking path before changing the keyword.

Save the verified view

After the table and fields are correct, save a named column set or report view where the current Google Ads workflow supports it. Add the intended question, scope, owner, date-range convention, conversion-lag rule, and refresh cadence to the handoff. A saved view is a starting point; confirm the live account and scope every time.

Validate privacy and Search Terms Insights expectations

Google omits some search terms that do not meet activity thresholds for privacy. No column or filter setting can expose every hidden query. Treat the absence of a row as a reporting limitation, not proof that the query did not occur or that a keyword never matched.

Search Terms Insights groups additional demand into themes and subthemes. Use it to understand category patterns, emerging customer language, and coverage gaps. Do not expect its totals to reconcile row for row with the regular report because hidden queries, aggregation, conversion processing, and theme history can differ.

Keep query exports limited to the people and period that need them. Search terms can reveal sensitive interests. Follow the account’s access, retention, and privacy rules and remove copies when the review is complete.

Validate the action path before exporting

For each important row or theme, add a short classification and decision:

valuable and relevant;
relevant but unproven;
irrelevant or unserviceable;
ambiguous and needing more context.

Then choose retain, add coverage, add a negative, revise an ad, improve the landing page, repair tracking, restructure, or wait. Record the matching keyword, ad group, scope, spend, outcomes, reason, owner, date, threshold, and next review.

If the action is a keyword or negative keyword, use the campaign workflow that supports it and verify its scope after saving. Google notes that a Report Editor view may not offer direct keyword or negative-keyword actions. Do not apply a broad negative because a single row looks irrelevant; test it against the valuable variants you intend to keep.

Check the full customer path

Compare the query with the ad, landing page, device, location, language, form, call, checkout, consent, and business outcome. A high-click query can reveal a page mismatch or accidental-click pattern. A no-conversion query may still be valuable when the sales cycle is long. A tracking repair can be more correct than a targeting change.

Common “set up correctly” failures

Watch for these validation errors:

using a broad account report for a campaign-specific decision;
combining campaign jobs with different conversions or budgets;
treating today’s rows as final before conversion processing completes;
hiding Keyword or Match type and then guessing why a query matched;
assuming Match type is the same as the keyword’s configured match type;
using Search Terms Insights as an exposed-query list;
treating privacy-omitted queries as zero demand;
filtering before classifying and never reviewing the unfiltered baseline;
applying a negative from an analysis surface without checking scope;
exporting query data with no owner, privacy boundary, or action handoff.

Correctness checklist

Before considering the report ready, confirm:

[ ] The question, account/campaign/ad-group scope, network, owner, and action path are clear.
[ ] Date range, time zone, conversion lag, promotions, releases, and other caveats are recorded.
[ ] Search term, Keyword, Match type, Campaign, Ad group, cost, conversions, value, and quality fields are visible.
[ ] A known row was used to verify field meaning and scope.
[ ] Segments and filters answer a question and an unfiltered baseline is available.
[ ] Privacy omissions and the difference between Search Terms Report and Insights are understood.
[ ] Query classification, negative or keyword scope, landing-page review, and tracking checks are included.
[ ] The saved view has an owner, cadence, retention rule, next review, and decision record.

For the standard setup sequence, see how to set up Google Ads Search Terms Report. For ongoing governance, read the Search Terms Report best practices guide. The adz.so product overview describes the current audit entry point and does not imply that adz.so manages or edits the report automatically.