Google Demand Gen audience reporting can show how campaign and ad-group results are associated with audience segments, demographics, and exclusions. The report is useful for diagnosing delivery and performance patterns. It does not, by itself, tell a team which segment caused additional revenue or which segment will produce the best customers next month.
A practical weekly review connects the platform’s audience and channel reports to the campaign objective and the outcomes sales cares about. The goal is a defensible next decision—not a ranking based on the lowest reported cost per conversion.
Start with the decision the review must support
Before opening a report, write down the question. Is the team checking whether the campaign is reaching the intended audience, whether a particular segment is consuming budget, whether leads meet qualification rules, or whether the current channel mix supports more investment? One report cannot answer all of these questions with the same metric.
Record the campaign goal, the conversion actions used for optimization, the date range, and any recent changes to audience segments, creative, budgets, or bidding. Keep the review period consistent from week to week, and leave enough time for the relevant conversion lag. Google notes that Demand Gen results can vary from day to day and that conversion data can arrive after the ad interaction; a single recent day may therefore be incomplete. See Google’s Demand Gen performance guidance.
Read the audience report as a diagnostic view
Google Ads’ audience report brings together performance by campaign, ad group, and account, including audience segments, demographic views, and exclusions. Depending on the report and available data, the table can include impressions, clicks, cost, conversions, and conversion value. Google’s current terminology uses “audience segments” and “your data” for groups and first-party data audiences. See About Audience reporting.
Use the report to ask diagnostic questions: Which segments are receiving delivery? Where is spend concentrated? Which groups are associated with the selected conversion action? Are exclusions or settings limiting reach? A reported result is evidence about the selected measurement view; it is not proof that everyone in a segment behaved alike or that the segment caused the conversion.
If a segment is missing or has little data, do not convert that absence into a zero-performance conclusion. Record what the account can show, what is unavailable, and whether the sample is large enough for the decision.
Separate audience performance from channel performance
Demand Gen can deliver across multiple Google surfaces. Google Ads reporting provides a network breakdown and additional segmentation for supported channels and formats. Current Google documentation lists surfaces such as YouTube, Discover, Gmail, Google Display Network, and Maps; the exact fields visible in an account depend on campaign setup and reporting availability. See Demand Gen campaign metrics and reporting.
Review network and format results alongside audience segments, but do not assume that a segment-level result and a network-level result can simply be added together. They are different cuts of campaign performance. Keep the report’s scope visible and avoid double-counting the same campaign spend or conversions when summarizing multiple views.
For a separate discussion of the difference between Search and Demand Gen campaign roles, see Google Ads Search vs. Demand Gen campaigns. For video-specific creative preparation, see Demand Gen video asset formats.
Use a metric set that follows the business goal
Keep four kinds of measures distinct:
- Delivery: spend, impressions, reach where available, clicks, and channel or format distribution.
- Platform conversion: the action optimized by the campaign, its value, and the reporting/attribution view being used.
- Qualified outcome: CRM-confirmed inquiries, sales-accepted leads, held meetings, opportunities, or sales—whichever outcome the team has defined and can match reliably.
- Economics: cost per qualified outcome and contribution, calculated using a consistent spend and cost boundary.
Do not let click volume or a low platform CPA stand in for lead quality. If CRM matching is incomplete, show the match rate and label the result as directional. Where the business goal is reach or brand lift, use the measures selected for that goal; do not force every campaign into a lead-volume scorecard.
Keep attribution views separate in the weekly report
Google Ads’ data-driven attribution distributes conversion credit across eligible ad interactions, including clicks and video engagements in Demand Gen. It is still a platform attribution model, not a controlled test of incremental impact. See Google’s explanation of data-driven attribution.
Google also documents separate “Conversions (Platform Comparable)” columns for Demand Gen. These offer an alternative reporting view that can account for view-through conversions and isolate Demand Gen from other Google campaigns under the documented methodology. They do not change bidding or optimization. If the team uses these columns, label them clearly and do not compare their values with the standard “Conversions” column as though the definitions were identical. See Google’s documentation on Platform Comparable columns.
When a budget decision depends on whether advertising created additional demand, use an appropriate incrementality design where feasible. A difference in reported audience CPA is not an incrementality result. Our guide to holdout tests when platform attribution is not enough explains the purpose and limits of that approach.
Example: a lower platform CPA may not mean a stronger sales outcome
The numbers below are illustrative, not a benchmark. Assume two audience segments are reported over the same sufficiently mature period. Segment A has $2,400 in spend and 32 platform-reported conversions, or $75 per reported conversion. Segment B has $1,800 in spend and 18 platform-reported conversions, or $100 per reported conversion.
Suppose the CRM match shows 8 qualified outcomes from A and 9 from B. Under the same spend definition, cost per qualified outcome is $300 for A and $200 for B. The platform column favors A; the qualified-outcome view favors B. That difference is a reason to inspect the offer, audience setup, creative, and follow-up—not proof that B caused more incremental demand.
The comparison is only useful if the CRM outcome has a stable definition, records are matched consistently, and the data windows account for conversion delay. If those conditions are not met, show the limitation instead of presenting the ratio as final.
End the review with one bounded next step
A useful weekly report ends with a decision and a reason. For each proposed change, record:
- the campaign and audience or channel slice being reviewed;
- the objective and conversion definition;
- the report date range and whether it is mature;
- spend, platform results, qualified CRM outcomes, and match coverage;
- the suspected constraint and supporting evidence;
- the one change to make or the reason to hold; and
- the guardrail and date for the next review.
Change one major element at a time where possible. If audience, channel, creative, and bidding all change together, the next review cannot reliably explain what drove the result. Scale only when the platform trend, qualified outcomes, and economics support the same decision; otherwise, keep the next step small and measurable.
How did this article land?
Choose one reaction. You can change it anytime.