MAHMOUD ABDELNABY

PRACTICAL GUIDE · Paid media

How to Diagnose Branded Search Overlap in Performance Max

Check whether branded queries are appearing in Performance Max, separate overlap from proven cannibalization, and test exclusions without assuming they will improve results.

Seeing your brand name in Performance Max search terms does not, by itself, prove that the campaign took a conversion away from your Search campaign. It shows that an ad appeared for a branded query in the reporting view. To decide whether to add an exclusion, first establish what is overlapping, what the brand campaign is meant to do, and what evidence would show that the change helped or hurt.

Google Ads currently provides a Performance Max search terms report with search terms, associated metrics, landing pages, and ad formats. Google also documents brand exclusions for Performance Max and Search, while cautioning that controls can limit conversion opportunities. Use the current account view and documentation to confirm which controls are available in your account before changing settings. Performance Max search terms report · Brand settings for Search and Performance Max

Separate overlap, attribution, and incrementality

  • Observed overlap: Performance Max served for a branded query during a defined period, according to the report.
  • Attribution: A conversion was credited to a campaign under the account’s conversion and attribution settings.
  • Incrementality: The conversion would not have happened, or would have happened differently, without the campaign. This is a causal question; a query row or attribution label alone does not answer it.

These can coexist, but they are not synonyms. A brand campaign may protect coverage, support a specific landing page, or capture demand from people who already know the business. A PMax campaign may also reach branded searches. Whether that is wasteful depends on the goal, economics, query, and observed user path—not on the mere presence of the brand name.

Build a baseline from comparable views

Before changing an exclusion, document:

  1. The date range, account timezone, currency, and conversion actions included in the report.
  2. Branded query groups, including spelling and language variants where the reporting view exposes them.
  3. PMax search term, landing page, ad format, cost, and conversion details that are actually available.
  4. The corresponding brand Search campaign’s targeting, budget limits, impression coverage, landing page, and conversion definitions.
  5. Other demand sources active in the same period: organic brand searches, direct traffic, promotions, partner referrals, and offline sales where known.

Avoid combining different attribution settings or conversion windows as though they were a single comparable series. Note reporting limits and privacy aggregation. If a query or metric is not exposed, mark it unavailable rather than reconstructing it from a category label.

Diagnose the job of the brand campaign

Ask what the separate brand campaign is supposed to accomplish. Is it meant to preserve a message, route to a location-specific page, provide a controlled offer, protect coverage during a promotion, or simply capture existing demand? Define that job and its guardrails before deciding to block PMax.

Review whether the branded queries in PMax lead to a useful landing page and whether the business could serve those visitors at acceptable economics. Check if the brand Search campaign is limited by budget or eligibility. If there is a genuine reason to control brand traffic, compare campaign-level brand exclusions with negative keywords using Google’s current documentation. These controls may operate differently, and the account-level negative keyword option can affect other campaigns beyond PMax; do not apply a broad exclusion without tracing its scope.

Test an exclusion with an explicit risk check

If the baseline shows a specific issue and the business wants to separate branded traffic, choose the narrowest applicable control. Save the original settings, identify which inventory and campaigns the change affects, and define what would count as a problem: loss of valuable shopping coverage, fewer qualified conversions, a higher cost per completed action, or reduced reach in an important market.

Where the account supports a valid experiment or a defensible comparison, use it. Otherwise, make a controlled change with a comparison period and record other changes that could affect demand. Avoid changing budget, creative, landing page, bidding, and exclusions all at once if you need to interpret the result.

Review observed query and campaign measures after enough data has accumulated for the account’s volume and conversion delay. Compare costs and qualified outcomes, not only attributed conversion counts. A lower PMax conversion count after an exclusion does not automatically mean the account lost value; those conversions may have moved to another campaign. Likewise, a stronger brand Search report does not prove the change created incremental business.

Example: an overlap report is a starting point, not a verdict

Suppose a PMax search terms view shows branded queries and the brand Search campaign also records conversions. The marketer first checks whether the PMax rows are Search or Shopping format, what landing pages were shown, how many conversions were attributed under each campaign’s settings, and whether the brand campaign was budget-limited. They then define a narrow test and monitor total qualified outcomes across both campaigns plus any business-side reconciliation available.

This example illustrates a diagnosis process. It does not describe a real account or imply that an exclusion will improve results.

Short-video script: brand-query overlap is not proof of cannibalization

Length: 45 seconds. Visual: two campaign cards and an evidence checklist.

0–5 sec — Hook: “Your brand appeared in Performance Max. Did it steal a sale? The report alone cannot tell you.”

6–17 sec — Explain: “Overlap is what served. Attribution is what the model credited. Incrementality asks what would have happened without the campaign.”

18–30 sec — Diagnose: Show query, format, landing page, conversion settings, and whether the separate brand campaign was constrained.

31–39 sec — Test: “If you exclude a brand, save the baseline and watch total qualified outcomes across campaigns.”

40–45 sec — Close: “Control only after you know what the control can change.”

Use a redacted demo account or synthetic data. Do not show client names, budgets, or conversion records.

  1. Cover: Performance Max shows your brand. What now?
  2. Do not jump to cannibalization: A search-term row proves appearance, not the counterfactual.
  3. Inspect the row: Query group, date, format, landing page, and available metrics.
  4. Compare the brand campaign: Goal, budget constraint, landing page, and conversion setup.
  5. Map the control: Identify the precise campaigns and inventory an exclusion affects.
  6. Set guardrails: Qualified outcomes, costs, useful coverage, and market reach.
  7. Change carefully: Save settings and avoid simultaneous unrelated changes.
  8. Report honestly: Show both campaign-level attribution and total account/business evidence, with limitations.

Field experiment thread: evaluate a brand exclusion without assuming a win

This is a proposed evaluation, not a performance case study.

1/ Capture the current PMax search term view and brand Search settings for a completed period. Record timezone, currency, conversion actions, and visible reporting limitations.

2/ Define the specific query group and business reason for considering an exclusion. If the only reason is “the brand appears,” collect more evidence before changing anything.

3/ Write the hypothesis and guardrails: what outcome should improve, what valuable coverage must not be lost, and which total qualified measure will be reviewed.

4/ Apply the narrowest documented control only after identifying its scope. Save the prior state and the change date. Use an experiment or comparable period when available.

5/ Compare query visibility, campaign allocation, cost, and qualified outcomes across affected campaigns. Note promotions, seasonality, budget changes, and conversion delays; report the result as observed, not causal unless the design supports causality.

Tool-neutral prompt pack: audit PMax brand-query overlap

Prompt 1 — Separate evidence from inference

Review these redacted search term rows and campaign settings [paste data]. Separate observed branded-query overlap, attributed conversions, and claims about incrementality. List missing fields and reporting limitations. Do not infer a sale was stolen or added.

Prompt 2 — Map the exclusion scope

Using this current official platform documentation [paste URL or excerpt] and these campaign settings [paste redacted details], map which campaigns and inventory the proposed brand exclusion or negative keyword could affect. Flag anything that requires account-level confirmation. Do not recommend a change without stating its reach and risks.

Prompt 3 — Draft a review plan

Turn this baseline [paste sanitized summary] into a test plan with a hypothesis, comparison method, primary business measure, guardrails, reporting window, confounders, and stop conditions. Distinguish attribution from incrementality and avoid promising a performance improvement.

Stop-doing swipe file: stop calling overlap cannibalization without a test

Stop: “PMax took 40 conversions from Search because branded terms appeared in its report.” The query report does not show what would have happened without PMax.

Say instead: “PMax served for these branded query groups during [period]. The separate brand campaign recorded [observed data] under [conversion settings]. We have not established how many outcomes were incremental or displaced.”

Stop: applying an account-level exclusion because one campaign appears to use brand traffic. It may affect campaigns beyond the one you are diagnosing.

Do this instead: map control scope, preserve the baseline, set a total-outcome guardrail, and evaluate an appropriately narrow change only when the evidence supports it.

Hook–Value–Template: decide whether to exclude branded traffic

Hook: “A branded query in PMax is a clue to investigate—not proof of wasted spend.”

Value: Separate what served, what received attribution, and what was incremental. Map the control’s reach and judge the change by total qualified outcomes and business constraints.

Decision brief:

Question: [what concern are we investigating?]
Period and account settings: [dates, timezone, currency, conversions]
Observed PMax brand queries: [query group, format, landing page, metrics]
Brand campaign context: [goal, budget/eligibility, landing page]
Hypothesis: [what should change, and why?]
Proposed control and scope: [setting, affected campaigns/inventory]
Primary measure: [qualified outcome across relevant campaigns]
Guardrails: [valuable coverage, cost, market reach]
Confounders and limits: [other changes, attribution, data gaps]
Decision date and owner: [date / role]

Approve an exclusion only if the business goal and expected trade-off are clear. The brief is a decision aid, not a guarantee that the change will improve performance.