The short version
- One campaign holds very different products, yet shares a single daily budget and Target ROAS.
- Every night, Karsa.ai predicts product performance across your catalog and groups similar SKUs into clusters.
- You run one campaign per cluster, giving each group a dedicated budget and matching Target ROAS.
One Target ROAS under-bids top items and over-bids weak ones.
Each cluster gets a Target ROAS that matches its products.
The problem: one campaign reports a single average
An online store often places thousands of SKUs into one Google Shopping or Performance Max campaign. Fixed brand and category setups behave the same way because Smart Bidding optimizes toward one campaign Target ROAS.
Reports display one blended average, which can meet your target while individual items perform very differently:
- Top products hit the shared budget cap. They compete for daily spend against every weaker item in the catalog.
- Loss-making products continue spending. Strong sellers lift the campaign average above target, hiding unprofitable clicks underneath.
One average for the whole campaign.
Top products reached 820% ROAS. Loss-making products reached 65%.
Why a fixed 30-day window does not fit every product
Static groups by category, brand, or margin stay frozen when demand shifts with prices, stock, promotions, and seasons.
Historical label scripts instead apply a fixed cutoff such as "ROAS above 400% over the last 30 days". That single lookback works for steady everyday sellers, yet fails whenever an item follows a different buying rhythm:
- Longer purchase cycles look inactive: An item bought every five to six weeks can show zero 30-day orders and get demoted.
- Ended seasons keep spending: Past peak orders remain inside the 30-day count for weeks after demand drops.
- Rising demand waits in a low cluster: Early orders take weeks to pass a 30-day cutoff, missing peak auctions.
Shortening the lookback adds daily noise for slower items, while lengthening it slows reaction to seasonal shifts. Splitting rules by fast, slow, and seasonal items creates dozens of manual cutoffs to maintain. Karsa.ai replaces fixed lookback rules with machine-learning models that predict product performance directly from your store data.
| Method | Products are grouped by | Limit |
|---|---|---|
| Single or category campaigns | Catalog taxonomy | One blended average across unequal SKUs |
| Margin buckets | Gross margin % | Identical margins still convert very differently |
| 30-day rule scripts | Fixed lookback window and static cutoffs | One time window misreads different buying cycles |
| Karsa.ai | Nightly predicted product performance | Requires roughly 100+ monthly Google Ads conversions |
What Karsa.ai does instead
Every night, Karsa.ai predicts future performance for each SKU in your feed, including items with sparse clicks. Items with similar predicted performance join the same cluster, keeping auction behavior consistent inside every campaign.
Cluster count adapts to your account volume so each active campaign retains at least 30 monthly conversions. Typical accounts run 3 to 8 active groups, and one workspace can maintain multiple independent clusterizations in parallel.
Product margin never decides cluster placement. Instead, it calculates net profit and sets the break-even Target ROAS per cluster.
Karsa.ai updates only custom_label values via a Google Merchant Center supplemental feed while your team controls bids and budgets.
The optional C0 cluster
C0 is an optional cluster for chronically loss-making products. You enable it per clusterization, because isolating unprofitable SKUs into a separate campaign does not pay off in every account. When C0 stays off, Karsa.ai assigns all items to active clusters based on predicted performance.
Three places where performance improves
1. Top products receive a dedicated budget
SKUs with the highest predicted performance enter the top cluster, where a separate daily budget protects Search Impression Share.
Top, mid, and loss-making items draw from one daily budget.
Top SKUs get an isolated growth budget and recover Lost IS.
2. Smart Bidding learns from uniform campaigns
For low-click SKUs, Google Smart Bidding relies on campaign-level conversion data. Grouping items with similar predicted performance gives every campaign a clean signal, so one Target ROAS fits all included SKUs.
3. Weak products stay behind strict guardrails
You keep your entire catalog active in Merchant Center without hard exclusions. Low-performing items move into C1 (or optional C0) under a break-even Target ROAS and a capped daily budget. Once predicted performance recovers, Karsa.ai promotes the SKU back into a higher cluster overnight.
Loss-making items keep spending under a healthy-looking average ROAS.
Break-even Target ROAS + capped test budget; recovering SKUs move up.
Discounts affect strong and weak clusters differently
A price cut affects strong and weak clusters in opposite ways, which static margin labels miss.
- Top clusters: Lower unit margin raises break-even ROAS, yet higher conversion rates can still grow total daily profit.
- Weak clusters: Lower margin rarely brings enough extra orders, so Karsa.ai raises the break-even floor overnight to guide a stricter target.
Where you see it in the Portal
The Portal displays achieved return, Target ROAS, cost, conversion value, and net profit per cluster before your feed goes live.
Frequently asked questions
Does Karsa.ai group products into clusters according to margin?
No. Karsa.ai groups SKUs by predicted product performance, so items inside one campaign behave similarly during auctions. Margin applies separately to set the conversion threshold, net profit, and the break-even Target ROAS of each cluster.
Why can a 30-day rule not do the same job?
A rule relies on one fixed lookback window, and no single period fits your entire catalog. Thirty days works for a steady seller, yet misreads longer buying cycles and seasonal shifts. Machine-learning prediction spots changing product performance early without manual threshold maintenance.
Is the C0 cluster required?
No. C0 is an optional group for loss-making products, enabled only where isolating unprofitable spend pays off. When C0 is disabled, Karsa.ai assigns every SKU to an active cluster by predicted performance.