Performance Max can scale results, but it can also drain your investment if not managed correctly. In this guide, you will discover how to regain control of your budget, optimize resource allocation, and make data-driven decisions to improve performance without wasting spend.
Google launched Performance Max in 2021, promising to simplify ecommerce advertising. One single campaign, all Google channels, and automation that optimizes in real-time. For many teams, it was a relief to stop managing Search, Display, and Shopping separately.
The problem appeared later. Performance Max makes budget distribution decisions that the team cannot fully see. The system doesn't exactly fail; it optimizes based on its own signals, and those signals tend to favor what has already worked before.
The most common result is this: products with the best sales history hoard most of the spend. New products don't generate data because they don't receive traffic.
And there is a third group: products with real potential that have gone months without significant exposure and remain that way because the algorithm has no reason to test them.
Why Categorical Organization Doesn't Solve the Performance Max Problem
The instinctive response for many teams is to organize campaigns by category. Shoes in one campaign, accessories in another. This makes sense from a catalog perspective, but not from a performance perspective.
The PMax algorithm does not distribute budget equitably within a campaign. Within "shoes," it will favor models with conversion history, regardless of the fact that you are paying for all shoes to compete. Those that were already selling well keep receiving the spend. The others wait.
The organization that actually works is by real performance. Grouping products according to how they behave, not what they are.
The Segmentation That Changes How PMax Works
The most direct framework divides the catalog into three groups.
The first are high-performing products (Stars)
High ROAS, consistent conversions, clicks that justify the spend. The goal with this group is to maintain profitability while maximizing volume. ROAS targets are higher, between 3x and 5x depending on the business margin.
The second group are the "zombie" products
They have been in the catalog for some time but with insufficient exposure to generate relevant data. They might be bad products, or they might be good products that the algorithm never tested because they lacked history.
For this group, the goal is visibility, not immediate profitability. ROAS targets are lower, between 0.5x and 2x, because the goal is to get data to make a real decision about each SKU.
The third group are new arrivals
Recently added products that cannot compete in the same campaign as star products because they have no history. They need a separate campaign with different evaluation criteria: the KPI isn't ROAS, it's visibility and initial behavior data.
Thresholds That Define Each PMax Segmentation
For segmentation to work in practice, the team needs to precisely define which metrics determine which group each product falls into. Some reference parameters include:
- Stars: ROAS above 3x to 5x, click volume sufficient for data to be statistically relevant, consistent conversions in the analysis period.
- Zombies: ROAS below 2x, or insufficient data to evaluate, or low clicks relative to the catalog average. The exact threshold depends on business margin and volume.
- New arrivals: Criteria based on the date added to the catalog—for example, products added in the last 30 days—with awareness and data accumulation goals before being evaluated against the other groups.
These thresholds are not universal. A business with high margins can tolerate a lower star ROAS than one with tight margins. The point is to define them clearly so that classification is consistent and doesn't depend on the personal judgment of the analyst on duty.
The Analysis Period Matters More Than It Seems
Many teams use 30-day windows to evaluate performance. For fast-changing catalogs, that is too slow.
With a 30-day window, a product that performed well three weeks ago and started to drop this week still looks profitable in the aggregate.
And a seasonal product that took off ten days ago doesn't yet show the potential it is already having in the last few days.
A 14-day window provides more up-to-date signals. It is especially relevant in fashion, home decor, and any category where demand changes with trends or seasonality.
The trade-off is that with less data comes more noise, so it makes sense to combine shorter windows with a minimum click volume before making reclassification decisions.
The Most Time-Saving Step: Automating Movement Between Groups
Segmentation works if products move between groups when their performance changes. If this is done manually by a person reviewing SKU by SKU, the system doesn't scale for large catalogs.
The way to make it sustainable is to define rules that move products automatically.
If a zombie product exceeds a 3x ROAS in 14 days, it moves to the star group. If a star product falls below 2x in the same period, it drops to the zombie group for review. New products always enter the new arrivals group and migrate to zombie or star after a defined data accumulation period.
Feed management tools allow you to automate this logic without the team having to review every individual product.
The case documented by Channable with La Maison Simons, a Canadian fashion retailer, illustrates the type of result this approach can produce: ROAS that nearly doubled in three years, reduction in cost per click, and a 14% increase in average order value.
Products that previously received no exposure ended up being some of the best performers once they had a campaign designed to give them visibility.
The Same Logic Applies to Other Channels
Once the star/zombie/new arrival segmentation exists for Google, it makes sense to replicate it on Meta, TikTok, Pinterest, and any other paid channel where the team is active.
A zombie product on Google might have traction on TikTok. The audience profile that converts on one channel doesn't necessarily convert on another.
Having the same classification across all channels allows you to see where each product actually works and distribute budget accordingly, instead of assuming that what didn't work on Google won't work anywhere.
Consistency across channels also simplifies reporting. Instead of analyzing each platform's performance separately, the team can evaluate how each product segment moves through all channels and detect patterns that wouldn't be visible looking at Google or Meta in isolation.
What the Paid Media Team Needs to Optimize Performance Max
Three concrete things.
- First, clarity on which metrics define each group for the specific business. ROAS thresholds vary by margin, category, and seasonal objectives. There is no universal number.
- Second, visibility of performance at the SKU level in a centralized way. PMax does not provide that granularity natively, so in most cases, a feed management tool or an integration that consolidates product data from all campaigns and channels is needed.
- Third, defined rules for automatic movement between groups. Without automation, segmentation becomes another manual process the team has to maintain week after week, which doesn't scale.
The starting point doesn't have to be perfect. Starting with three campaigns and simple thresholds is already better than a single campaign organized by category where the algorithm distributes budget based on its own history.
Performance-based segmentation doesn't eliminate PMax automation; it makes it work with better information about what deserves spend and what still has to prove it earns it.