Demand Gen campaigns can serve across Google surfaces that include Gmail, but a low-traffic symptom may come from many layers. Google recommends examining account issues, campaign dates and status, budget, bidding, targeting, conversion tracking, and review status. The durable skill is a diagnostic order that preserves evidence.
VISUAL LESSON
What you will learn
- 01Run a layered low-traffic diagnosis.
- 02Distinguish hard blockers from constraints.
- 03Create a change log and recovery check.

ILLUSTRATIVE WORKED EXAMPLE
Prioritize an illustrative low-traffic investigation
PRACTICAL INTERFACE MAP
Move through Google Ads without losing the baseline
Record notifications, billing, policy, start and end dates, enabled state, learning, and review status.
Review budget, bid strategy, audience size, geography, exclusions, inventory, assets, and landing pages.
Confirm the intended conversion action records correctly, log one change, and schedule the next review.
STEP-BY-STEP LESSON
Eligibility → schedule → delivery → measurement
THE LEAD ATLAS METHOD
Lead Atlas Data can research current business contacts for the campaign's chosen categories, market, and locations, providing a separately measurable outreach path while Gmail delivery is diagnosed.See how custom list research works ↗Freeze the evidence
Record campaign ID, date range, spend, impressions, clicks, conversion actions, recent changes, and the exact surface or report that raised the concern. A total Demand Gen symptom does not prove Gmail alone is the cause.
Save the current settings and change history before editing. Compare like-for-like dates and account for launch timing, seasonality, conversion delay, review periods, and reporting freshness.
Clear account and policy blockers
Inspect account notifications, billing, advertiser verification where required, access, policy disapprovals, asset review, and destination availability. A single blocked component can prevent or restrict delivery.
Open each notice and record affected item, reason, owner, required action, evidence, and deadline. Fix the underlying issue; do not evade review with superficial variations.
Verify campaign state and timing
Confirm the campaign and ad groups are enabled, start and end dates are correct, the schedule covers the intended hours, locations and languages match the brief, and assets are eligible. Check whether a recent change restarted a learning or review period.
Use a launch checklist and compare the current state with the approved brief. Correct wrong dates or locations immediately, then record the exact time so recovery can be evaluated later.
Inspect delivery constraints
Review budget, bid strategy, bid or target settings, audience size, exclusions, device and geography controls, creative coverage, feed dependencies where used, and landing-page quality. Change only the diagnosed constraint.
Estimate what the budget and conversion history can reasonably support without inventing a benchmark. If widening audience or changing bids, state the tradeoff and preserve a before-and-after record.
Verify measurement and recovery
Test the intended conversion action and confirm it is the action the bid strategy is optimizing toward. Monitor eligibility, impressions, spend, click quality, conversions, and downstream lead handling after the recorded change.
Deliverable: baseline export, blocker checklist, dates-and-status audit, budget and bid review, audience and asset review, conversion test, one-change log, recovery window, and next decision.
THE TAKEAWAY
Start with hard blockers, capture evidence at each layer, and change one diagnosed constraint at a time rather than widening everything at once.OFFICIAL REFERENCES