Your Performance Max results have moved in the wrong direction, and the campaign offers enough levers to make almost any explanation sound plausible. You could replace assets, add negatives, split campaigns, exclude placements, or change the budget before lunch. If you do all of them, you may change performance, but you will lose the ability to explain why.
The better question is not “What can I optimize?” It is “Which layer failed?” Start with conversion data, establish a stable baseline, test one hypothesis, and only then intervene at the search, channel, placement, or device layer.
Verify the conversion signal before diagnosing the campaign
Performance Max depends on conversion data for both reporting and automated bidding. When a CRM import, offline conversion feed, or tag connection breaks, the campaign can appear to deteriorate even when the first failure occurred in the measurement pipeline. Optimizing against that false decline can waste budget and teach the bidding system from incomplete outcomes.
Google Ads’ Data Manager includes a central diagnostics view for data connections. It assigns statuses such as Excellent, Good, Needs Attention, and Urgent, and it can surface refused credentials, formatting problems, failed imports, and tagging mismatches. Its run history also shows recent synchronization attempts and error counts.
Use that information as an incident log, not as decoration. A Needs Attention or Urgent connection should stop a creative or targeting diagnosis until you understand whether conversions are missing. An Excellent or Good status is useful, but it is not proof that you selected the right conversion action or assigned the right business value. It tells you about connection health, not the quality of your measurement design.
- Record when the unexplained performance shift began. Do not rely on memory; you will need to compare that point with import and synchronization history.
- Check every data connection that supplies conversions used by the campaign, including CRM and offline conversion imports.
- Read the status and actionable alerts. Separate an authentication failure from a formatting error, a failed import, or a tag mismatch because each requires a different fix.
- Open the run history and identify the first unsuccessful or error-heavy synchronization. A failure that starts near the apparent campaign decline is a measurement lead worth resolving first.
- Compare completed outcomes in the originating business system with successfully imported outcomes for the same period. This helps distinguish a reporting gap from a real demand or traffic problem.
- After restoring the connection, mark the affected dates as an incident window. Do not use that contaminated period to declare a creative winner or justify a structural campaign change.
This order matters most when you optimize toward offline revenue, qualified leads, or later-stage CRM events. A small import failure can make high-quality traffic look unproductive, while a delayed correction can make the recovery look like sudden campaign growth. Neither interpretation describes the media accurately.
Build a baseline that separates the diagnostic layers
Once the conversion pipeline is credible, take a campaign snapshot before editing anything. Record the campaign and asset group, the conversion objective being evaluated, the date of the last material change, conversion volume or value, spend, and the efficiency metric tied to your business goal. Add notes for promotions, feed changes, landing-page changes, and other events that could alter demand or conversion rate.
The snapshot gives every later comparison an anchor. It also forces you to distinguish a campaign-wide decline from a concentrated problem. That distinction determines whether you need an experiment, an exclusion, or no change at all.
| Diagnostic question | Where to inspect it | What the view can establish | Important limitation |
|---|---|---|---|
| Did the conversion pipeline fail? | Data Manager diagnostics and run history | Connection status, synchronization failures, error types, and error counts | A healthy connection does not validate the business definition of a conversion |
| Did query intent change? | Campaign-level search term view | Search terms with campaign metrics that can support exclusions and intent analysis | The visibility applies to search-network traffic, not every Performance Max channel |
| Are search themes contributing? | Search theme reporting | Whether a theme is receiving traffic and producing conversions | Low use is different from poor performance |
| Did delivery move between networks? | Channel performance report | Performance across channels such as Search, Discover, and Display | A channel difference identifies where to investigate; it does not by itself prove the cause |
| Is inventory irrelevant or unsafe? | Placement data in the API or Report Editor | Specific placements that warrant relevance or brand-safety review | Placement analysis does not explain search-query performance |
| Is the issue concentrated by device? | Device reporting | Differences in product and campaign outcomes across devices | Splitting campaigns can fragment the data used by machine learning |
Do not confuse grouped search term insights with the campaign-level search term view. Grouped insights can help you recognize query categories, but they have lacked the cost depth needed for many optimization decisions. The campaign-level view exposes more detailed search metrics, although it still describes only the search-network portion of Performance Max.
That limitation changes how you interpret silence. If the search view does not explain the decline, you have not proved that search is healthy or that another channel is guilty. You have only eliminated the visible search terms as the complete explanation. Move to the channel report rather than stretching search-only data across the whole campaign.
Run a creative experiment only when creative is the question
A built-in Performance Max beta makes structured creative testing possible inside one campaign and asset group. You can define a control from existing assets, create a treatment with alternatives, retain shared assets across both variants, and assign a traffic split such as 50/50. This within-asset-group experiment reduces interference from separate campaign structures.
Use the beta when your hypothesis is genuinely about creative. It cannot cleanly answer whether a budget change, product feed edit, landing-page release, search-term exclusion, or conversion import repair caused the result. If those variables move during the experiment, the split may still produce numbers, but the business conclusion will be weak.
- Write one falsifiable hypothesis. Name the asset change, the business metric expected to improve, and the reason the audience should respond differently.
- Select one campaign and one asset group where the beta is available. Confirm that both variants will be evaluated against the same conversion setup.
- Use the current creative set as the control. Change only the intended creative variable in the treatment, and share assets that are not part of the hypothesis across both sides.
- Choose the traffic allocation deliberately. A 50/50 split gives the two variants equal traffic opportunity, but it also assigns half of experiment traffic to an unproven treatment.
- Define the decision rule before launch. Choose a primary business outcome and note any guardrails, such as conversion volume or spend, that would make an apparent efficiency gain commercially unacceptable.
- Freeze unrelated campaign changes. Keep a change log so that an emergency edit, promotion, feed update, or measurement incident is visible during interpretation.
- Give the experiment enough time. Early experience indicates that tests shorter than three weeks can be unstable, particularly in lower-volume accounts. Three weeks is a warning boundary, not a universal guarantee of certainty; low volume may require a longer run.
- Apply the treatment only when the result answers the original hypothesis. If the evidence is inconclusive, preserve that conclusion instead of promoting whichever side happens to be ahead at the stopping point.
The last step is easy to mishandle. A tie or inconclusive result is useful: it tells you that the proposed creative change has not demonstrated enough value to justify rollout under the observed conditions. It does not authorize a second round of post-hoc metric hunting until something looks favorable.
Randomized traffic improves causal confidence, but it cannot rescue a damaged conversion feed or a test that overlaps several campaign edits. Test quality still begins with signal quality and operational discipline.
Diagnose search, channel, placement, and device problems separately
If creative is not the only credible cause, work down through the remaining delivery layers. Make the smallest change supported by the evidence. A query problem calls for a query control; a risky placement calls for a placement review. Neither automatically justifies rebuilding the campaign.
Search terms, search themes, and brand traffic
Start with the campaign-level search term view and compare terms by both traffic and outcomes. Terms with higher-than-average click volume and zero conversions are sensible exclusion candidates. They are not automatic exclusions. Check whether tracking is complete, whether the term is relevant, and whether the evaluation period contains enough activity to support the decision.
Review brand traffic separately. Performance Max can lean toward high-intent branded searches, which may make aggregate efficiency look stronger without answering how much non-brand demand the campaign is creating. When preventing brand leakage is the actual requirement, explicit negative keywords provide more direct control than simply admiring the blended result. Brand exclusions also exist, but the key is to choose a control that matches the question you are trying to answer.
Treat search themes as positive targeting input, not as a substitute for term-level diagnosis. Use search theme reporting to see whether a theme receives traffic, where that traffic originates, and whether it converts. An underused theme has not necessarily failed; it may simply have received too little delivery to evaluate. A used theme with meaningful traffic and no business outcome presents a different problem.
Channels and placements
The channel performance report helps you locate delivery and performance across networks such as Discover and Display. Use it to identify where the deviation is concentrated. If total campaign efficiency falls while one channel’s delivery or outcomes change sharply, inspect that channel’s inventory and creative fit before changing every asset group.
For placement-level work, use the API or Report Editor data to identify inventory that is irrelevant or creates brand-safety concerns. Political content and children’s videos on YouTube are examples of placements that may require closer scrutiny for some advertisers. When placement names or video titles are in an unfamiliar language, Google Sheets’ translation function can speed up the relevance review.
Keep Search Partner Network limitations in view. Performance Max does not provide a simple opt-out for that network. Compare its performance with Google Search where the reporting permits, document the constraint, and focus on exclusions and controls that are actually available. Do not promise an optimization that the campaign settings cannot enforce.
Devices
Device reporting can reveal that certain products perform differently across phones, computers, or other devices. Treat that as a prompt to inspect the experience as well as the media. Product presentation, landing-page usability, checkout behavior, and competitive conditions may all sit between the click and the conversion.
Do not split campaigns by device merely because the report shows a difference. Campaign splits reduce the data available to each campaign and can weaken machine-learning inputs. Consider a split only when the difference is sustained and commercially material, both sides will retain enough volume to evaluate, and the new structure gives you a control you can use. If the split only produces cleaner-looking reports, the cost in fragmented learning may be higher than the benefit.
Key takeaways: use this Performance Max diagnostic order
- If a conversion connection needs attention, shows urgent errors, or has failed imports, repair measurement before judging campaign performance.
- If measurement is healthy, capture a stable baseline and identify whether the deviation belongs to search, a broader channel, placements, devices, or creative.
- If the question is specifically about creative and the beta is available, use the native asset experiment inside one campaign and asset group.
- If a creative test has run for less than three weeks, especially with low volume, treat an apparent lead as unstable rather than rushing to declare a winner.
- If a search term has unusually high click volume and no conversions, review it as an exclusion candidate instead of applying an arbitrary account-wide threshold.
- If a problem is confined to one delivery layer, change that layer. Avoid campaign-wide restructuring until the evidence shows that the structure itself is the constraint.
- If a device or campaign split would starve each side of useful data, keep the structure intact and use reporting for diagnosis rather than control for its own sake.
On your next review, begin with the data connection history and a dated baseline. Then write down one question that the available report or experiment can actually answer. One clean diagnosis gives you a reusable decision; five simultaneous optimizations give you a new mystery.
