Google's current Demand Gen pre-fill guidance states that Performance Max negative keywords and brand exclusions are not eligible for Demand Gen. Demand Gen creates demand across visual and discovery surfaces rather than operating like a Search keyword campaign. The practical task is to stop looking for an unsupported keyword list and choose controls that match the actual delivery risk.

VISUAL LESSON

What you will learn

  1. 01Explain why Search-style negative keywords do not map to Demand Gen.
  2. 02Choose an eligible control for each risk.
  3. 03Document residual uncertainty and reporting evidence.
Irrelevant signals are stopped by an exclusion gate while useful discovery paths continue toward message panels
The correct control depends on whether the concern is a channel, audience, placement, content type, location, product, or brand—not a Search query list.

ILLUSTRATIVE WORKED EXAMPLE

Route an illustrative Demand Gen control backlog

Concerns reviewedIllustrative backlog
24
Audience or customer exclusionFirst-party eligibility
7
Channel or placement decisionInventory concern
9
Creative, product, or page fixNot a targeting problem
8
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Replace the missing keyword box with a control decision

Symptom01Name the unwanted outcome

Capture channel, placement, audience, location, product, creative, destination, and business-quality evidence.

Control02Choose an eligible lever

Review channel controls, audiences and exclusions, content suitability, placements, locations, devices, feeds, creative, and bids.

Proof03Verify scope and result

Save the before state, changed setting, affected campaigns, reporting window, qualified outcomes, and remaining limitations.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Observed problem → correct control layer → scoped change → verified outcome

DiagnoseWhat was actually unwanted
ControlEligible narrow lever
VerifyScope and quality

THE LEAD ATLAS METHOD

Lead Atlas Data can research business contacts specific to the campaign's market, locations, and categories, giving the team a clearly bounded prospect cohort instead of treating a discovery-ad audience as a keyword list.See how custom list research works ↗
01

Confirm the limitation

Record that Demand Gen is not a Search keyword campaign and that Google's current pre-fill guidance says negative keywords and brand exclusions from Performance Max are not eligible to carry into Demand Gen. Capture the live account controls and review date.

Avoid instructions copied from Search, Display & Video 360, or Performance Max. Similar labels across products can have different scope, and a community workaround is not proof that Google Ads supports the control for this campaign.

02

Describe the unwanted outcome

Classify the concern as wrong audience, existing customer, unsupported location, weak Gmail or channel performance, unsuitable publisher context, irrelevant product, misleading creative, broken destination, low-quality conversion, or brand query concern. Preserve dates and examples.

Use campaign and channel reports, placement evidence where available, analytics, product data, and CRM outcomes. A disappointing lead does not prove a negative keyword would have prevented it, and a total Demand Gen result does not isolate Gmail.

03

Map the concern to eligible controls

Review audience exclusions, first-party customer exclusions, demographics, location and language, device controls, channel controls where available, placement and content-suitability settings, product filters, creative eligibility, landing pages, conversion goals, and bid strategy. Choose the smallest change that addresses the evidence.

Document exact scope. Account-level controls can affect unrelated campaigns, audience signals may expand, and content or placement controls may not create an absolute guarantee. Preserve the prior state and rollback owner.

04

Repair the underlying campaign when needed

If the problem is message-to-market fit, rebuild the offer, creative, product set, page, form, qualification, or follow-up instead of searching for an exclusion. If the conversion is too shallow, correct the goal and downstream quality feedback before automated bidding learns from it.

Test one material change at a time where practical. Keep location, dates, conversion action, attribution, and maturation window stable enough to compare, and label any simultaneous product or sales change.

05

Report what the control did

Compare channel delivery, spend, reach, clicks, conversions, qualified outcomes, value, complaints, and rejected demand before and after the scoped change. Explain conversion delay and residual uncertainty instead of claiming that unwanted intent was eliminated.

Deliverable: limitation reference, issue examples, control-layer matrix, current-settings capture, approved change, scope and rollback record, tracking test, channel report, qualified-outcome reconciliation, known limitations, and next-review owner.

THE TAKEAWAY

Do not promise negative-keyword control in Demand Gen; identify the concern, apply the narrowest eligible control, and verify actual channel and customer outcomes.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.