Google Ads

PMax Can Exclude an Income Range. That Does Not Make the Audience Strategy Fair or Accurate.

Neutral audience layers are reviewed against a fairness checklist before one translucent segment is excluded

Updated: October 31, 2026

Use household-income exclusions only when they are relevant, permitted and supported by business evidence. Measure what the excluded range contributes, preserve visibility into undetermined users, review geographic and product effects, and require a documented reason before a negative criterion reaches Performance Max.

What v26.1 made available

Google Ads API v26.1 added support for household-income exclusions in Performance Max through a negative campaign criterion. The capability provides implementation control, but it does not confirm that household income is an accurate or appropriate explanation for customer value.

Income data can be modeled, unavailable or uneven across markets. An exclusion may therefore remove people whose status is undetermined, suppress useful demand or act as a proxy for a business problem that should be solved in the offer, geography or qualification flow.

Test the exclusion hypothesis

Question Evidence Stop condition
Is income relevant? Price, financing and customer research No plausible purchase connection
Is the range measurable? Segment coverage and undetermined share Coverage is too sparse
Is performance different? Qualified value and margin Only click metrics differ
Is the use permitted? Policy and legal review Restricted or sensitive use
Can the offer improve? Landing and sales data Exclusion hides fixable friction

Run a demographic exclusion audit

  1. Export current demographic performance and coverage.
  2. Quantify the undetermined share by market.
  3. Compare qualified revenue, margin and sales acceptance.
  4. Check policy, legal and category restrictions.
  5. Test offer, price and qualification explanations.
  6. Use a limited experiment before a broad exclusion.
  7. Review impact across geography and customer type.

Avoid false precision

A demographic segment can look decisive in a report because it groups many people, not because it explains why they convert. Compare outcomes after controlling for geography, device, product, promotion and lead source. If the effect disappears, the exclusion is treating a correlated label as a cause.

Include undetermined users in the plan. Do not interpret missing classification as low value, and do not use aggressive exclusions where modeled coverage is too thin to support the decision.

Controls for responsible targeting

  • Confirm policy and legal eligibility.
  • Avoid sensitive-category use without specialist review.
  • Document business relevance.
  • Measure qualified outcomes, not CTR.
  • Protect undetermined users from accidental exclusion.
  • Set a review date and rollback threshold.

Run a pre-launch decision review

Build one realistic test case from the first row of the framework above, then follow it from the initial marketing signal through the customer action and the reporting record. Ask the channel owner, creative lead, analyst and conversion owner to review the same case independently. Each reviewer should be able to identify what was promised, what evidence supports it, what the customer can control and what event proves the outcome.

Record disagreements before launch. A difference in naming may look minor in a meeting, but it can split reporting, obscure a product limitation or produce a landing experience that answers a different question. Resolve the definitions in the campaign brief and measurement plan, then repeat the test on mobile, where context and controls are easier to lose.

Use a release gate instead of a vague best practice

Approve the work only when the offer facts, interaction state, conversion rule and downstream record reconcile. If any reviewer needs an unstated assumption to explain the result, the system is not ready. Assign an owner and a repair date for every exception, and preserve a small control group or annotated baseline where possible. That turns the launch into a measurable operating decision rather than a one-time interpretation of platform guidance.

Connect the decision to the rest of the system

Pair the audit with MTC’s audience-definition bias review. The purpose of the link is operational: the upstream promise, measurement rule and downstream experience must describe the same outcome.

Document the learning, not just the result

Record the hypothesis, segment settings, coverage, undetermined share, policy review, test dates, qualified results and approver. A demographic exclusion should never survive only because nobody remembers why it was added.

Revisit the criterion after changes in pricing, financing, geography or product mix. A once-useful exclusion can become a silent growth constraint.

Frequently asked questions

Does PMax now support household-income exclusions?

Google Ads API v26.1 added support through negative campaign criteria.

Should undetermined income be excluded?

Not by default. Measure its size and value because missing classification is not proof of poor fit.

What outcome should justify an exclusion?

A persistent difference in qualified economic value, supported by adequate coverage and policy review, is stronger than click behavior.

Sources

Published by Marketing That Clicks
Last reviewed October 31, 2026.