Inside this resource.
12 sectionsA map of the published document. Choose a section to start reading.
- 01Put this guide to work
- 02What You'll Learn
- 03Section 1: Review the Product-Grouping Problem
- 04Section 2: The 4-Layer Feed Architecture
- 05Section 3: Layer 1 - Setting Up Feed Labels
View 7 more sections
| id | custom_label_0 |
|---|---|
| SKU001 | WINNER |
| SKU002 | RISER |
| SKU003 | LAGGARD |
| SKU004 | SLEEPER |
Source: View the complete rubric · Source-defined bands. Your account has not been scored.
Separate the product boundary from the review label.
Feed labels and custom labels do different jobs. Segment sizes in this method are workload heuristics, not platform learning limits.
- Set the boundary
Define the intended product and market universe.
- Map labels
Distinguish structural feed labels from changeable custom labels.
- Review products
Use item evidence, stock and margin to assess the grouping.
- Check routing
Verify which products enter each campaign before judging results.
Read the full source: Section 1: Review the Product-Grouping Problem · Section 2: The 4-Layer Feed Architecture · Summary: The 4-Layer Feed Architecture
Jump to a section
Put this guide to work
Use labels, variant grouping, performance buckets and budget ownership to create a maintainable Shopping structure.
Your task: Map feed-to-campaign roles. Record the source, date range and reviewer beside the result. Leave anything you have not checked marked Not checked.
Related work: Plan a PMax asset group before building it. · Multi-Campaign Budget Planner
What You'll Learn
- How to review product-group complexity without inferring self-competition
- The 4-Layer Feed Architecture (our proprietary framework for multi-feed segmentation)
- How to set up feed labels for structural campaign control
- The 40-Variant Rule: why segment size matters more than you think
- Performance bucketing with custom labels (dynamic product routing)
- Budget orchestration: same ROAS target, different budgets
- A 4-week implementation checklist
This guide is for: E-commerce advertisers running Shopping or Performance Max with 100+ SKUs who want more control over product-level performance.
Planning estimate:2–4 weeks for the example architecture; assess actual dependencies and measure results. No immediate improvement is promised.
Section 1: Review the Product-Grouping Problem
Review Product Grouping
Large groups can make product-level review harder, but product count does not establish an internal auction between your products, a Shopping Quality Score drop or higher CPC. Inspect actual item performance, margin, stock and campaign controls before splitting.
The 40-variant/25–35 targets in this method are operator workload heuristics, not Google limits or optimal learning sizes. Smaller or larger groups can be appropriate.
The Confusion That Costs You
Most advertisers treat "feed labels" and "custom labels" as interchangeable terms. They're not.
Feed labels:
- Structural segmentation at the data source level
- Set when you create a feed in Merchant Center
- Immutable after creation
- One feed label per campaign
Custom labels:
- Dynamic segmentation within campaigns
- Can be updated via supplemental feeds
- Five available (custom_label_0 through custom_label_4)
- Changeable at any time
When you understand this distinction, you can build a two-layer system:
- Feed labels create hard campaign boundaries
- Custom labels create flexible product routing within those boundaries
Most advertisers use one or the other. The best results come from using both.
Section 2: The 4-Layer Feed Architecture
We call our framework "The 4-Layer Feed Architecture." It's how we structure multi-feed Shopping accounts that need maximum control without maximum complexity.
Think of it like building a skyscraper. Each layer supports the next.
Layer 1: Feed Label Foundation
What it is: Structural segmentation at the data source level in Google Merchant Center.
Why it matters: Feed labels determine which products can enter which campaigns. This is your immutable framework. Once set, you can't change a feed's label without creating a new feed.
Typical use cases:
- Separating products by country/language
- Selecting product sets for campaigns; brand-query control requires supported query controls, not feed labels alone
- Segmenting by product category at the highest level
- Maintaining separate feeds for different marketplaces
Impact: Creates clean campaign boundaries. Prevents cross-contamination between product universes.
Layer 2: The 40-Variant Rule
What it is: An optional 40-variant review target (often 25–35 in this method), to adapt to product diversity, volume and budget; not a hard platform cap.
Why it matters: Manageable groups can simplify review; the count alone establishes neither algorithmic confusion nor a Quality Score/CPC effect.
The numbers:
- Review target: 40 variants per segment, with actual controls and evidence taking priority
- Working workload preference: 25–35 variants, not a measured platform optimum
- Review preference: 20 is not a minimum; smaller coherent groups can be appropriate
Layer 3: Performance Bucketing
What it is: Dynamic custom labels that sort products by real-time performance.
The 4-tier system (our naming):
- Winners: Products with sufficient observed evidence above the chosen business target. Review capacity and marginal economics before increasing exposure.
- Risers: High potential, near-target performance. Increase exposure to find new Winners.
- Laggards: Below target, still converting. Reduce spend, don't eliminate.
- Sleepers: Low impressions, unknown potential. Test with limited budget.
Why it matters: Products should flow between tiers based on actual results. A Sleeper can become a Winner. A Winner can become a Laggard. Static segmentation misses this.
Layer 4: Budget Orchestration
What it is: Campaign-level budget allocation with targets chosen for actual goals and margins; one shared target is an optional example.
Planning choice: A common target can simplify comparisons when economics are comparable. Different campaign targets can be appropriate for different margins or goals; they do not inherently confuse bidding.
One illustrative approach:
- Same target ROAS for all campaigns in your architecture
- Different budgets for each tier
- Risers get 15-20%
- Laggards get 15-20%
- Sleepers get 10-15%
Scope: Campaign budgets and targets affect delivery. Asset groups do not have independent budgets/targets; separate campaigns are needed for separate budget control.
How the Layers Work Together
┌─────────────────────────────────────────────────────────────┐
│ LAYER 1: Feed Labels (GMC) │
│ ├── FEED-US-SET1 → Product Set 1 Campaign │
│ ├── FEED-US-CATEGORY1 → Category 1 Campaign │
│ └── FEED-US-CATEGORY2 → Category 2 Campaign │
│ │
│ LAYER 2: 40-Variant Rule (within each campaign) │
│ └── Each segment reviewed; 25-35 is a workload target │
│ │
│ LAYER 3: Performance Buckets (custom labels) │
│ ├── Winners → Campaign 1 (own-budget example) │
│ ├── Risers → Campaign 2 (own-budget example) │
│ ├── Laggards → Campaign 3 (own-budget example) │
│ └── Sleepers → Campaign 4 (own-budget example) │
│ │
│ LAYER 4: Budget Orchestration (Google Ads) │
│ └── Same ROAS target, different budgets per tier │
└─────────────────────────────────────────────────────────────┘
Section 3: Layer 1 - Setting Up Feed Labels
When to Use Multiple Feeds
Use separate feeds when:
- You sell in multiple countries/languages
- You have distinct product lines with different margin structures
- You need distinct product sets; feed labels alone do not separate branded from non-brand queries
- You need different pricing/availability by marketplace
Use a single feed when:
- You're US-only, single language
- All products have similar margin structures
- You don't need campaign-level product isolation
Feed Label Naming Conventions
Feed labels must follow Google's rules:
- Maximum 20 characters
- A-Z uppercase only
- Numbers 0-9
- Hyphens and underscores
- No spaces
Recommended format: [COUNTRY]-[CATEGORY]-[TYPE]
Examples:
US-OUTDOOR-BRANDUS-INDOOR-GENERALUK-OUTDOOR-SALEDE-ALL-PRODUCTS
Keep labels descriptive but short. You'll reference these in Google Ads.
Step-by-Step: Creating a Feed Label in GMC
Prerequisites: Enable "Advanced data source management" in Merchant Center Add-ons
- Go to Settings → Data Sources in Merchant Center
- Click "Add product source"
- Configure your data source (file upload, Google Sheets, or API)
- Scroll to bottom - find "Feed label" setting
- Click the pencil icon next to feed label
- Enter your label name (following naming conventions)
- Click Save
Common Mistakes
Mistake 1: Creating too many feeds
- Symptom: 10+ feeds for a single country
- Fix: Use custom labels for dynamic segmentation, not feed labels
Mistake 2: Inconsistent naming
- Symptom:
US_Products,usa-brand,US-OUTDOOR - Fix: Establish convention BEFORE creating feeds
Mistake 3: Forgetting to enable Advanced data source management
- Symptom: Can't see feed label option
- Fix: Settings → Add-ons → Enable "Advanced data source management"
Section 4: Layer 2 - Applying the 40-Variant Rule
How to Audit Current Segment Sizes
In Google Ads:
- Go to your Shopping or PMax campaign
- Navigate to Product Groups (Shopping) or Listing Groups (PMax)
- Look at the "Products" column for each group
- Flag any group with 40+ products
What you're looking for:
- Groups with 100+ products (review complexity and actual performance; count alone is not a critical fault)
- Groups with 40–100 products (review whether distinct controls or themes justify a split)
- Groups with 40 or fewer (still review suitability; the count does not certify quality)
How to Split Oversized Segments
Option 1: Use existing attributes
- Split by brand
- Split by product type
- Split by price range
- Split by category
Option 2: Create custom labels for segmentation
- Add a custom label via supplemental feed
- Label by margin tier
- Label by performance tier
- Label by seasonality
Example: Hammock brand with 200 SKUs
Before:
- Campaign 1: Hammocks (100 products)
- Campaign 2: Accessories (100 products)
After:
- Campaign 1: Hammocks - Portable (25 products)
- Campaign 2: Hammocks - With Stand (30 products)
- Campaign 3: Hammocks - Indoor (20 products)
- Campaign 4: Hammocks - Premium (25 products)
- Campaign 5: Accessories - Hardware (35 products)
- Campaign 6: Accessories - Fabrics (30 products)
- Campaign 7: Accessories - Care (25 products)
- Campaign 8: Bundles (10 products)
Same 200 SKUs across 8 example campaigns, with 10–35 products each. This is an organizational example, not proof that 8 campaigns outperform 2.
Review Segment Size From Evidence
The 25–35 target is a working preference. Product count is not conversion volume; do not split or merge solely to hit it. Assess theme clarity, budget, signal quality, conversion lag and maintenance cost.
When NOT to Segment
Review the risks of segmentation when:
- You have fewer than 50 conversions per month total
- A product line has fewer than 20 products
- You're launching new products (let Google gather data first)
- You don't have 90+ days of performance data
These counts and time windows are planning prompts, not universal prohibitions. Separate campaigns only for justified control needs; keep asset-group themes coherent without assuming separate budgets.
Section 5: Layer 3 - Performance Bucketing with Custom Labels
The 4-Tier System
We use four performance tiers. Our naming differs from other systems, but the logic is consistent:
Winners (custom_label: WINNER)
- Definition: Top-performing products exceeding ROAS target
- Action: Maximize exposure. These pay the bills.
Risers (custom_label: RISER)
- Definition: Products near ROAS target with high click volume
- Typical %: 15-20% of catalog
- Action: Increase budget to test if they become Winners
Laggards (custom_label: LAGGARD)
- Definition: Products below ROAS target but still converting
- Typical %: 20-30% of catalog
- Action: Reduce budget, don't eliminate. Monitor for trend changes.
Sleepers (custom_label: SLEEPER)
- Definition: Products with low impressions (unknown potential)
- Typical %: 40-50% of catalog
- Action: Test with limited budget to wake them up
Setting Up Supplemental Feeds for Custom Labels
Step 1: Create your supplemental data source
- In Merchant Center, go to Settings → Data Sources
- Click "Add supplemental source"
- Choose format (Google Sheets recommended for easy updates)
- Connect your source
Step 2: Structure your supplemental feed
Required columns:
id(must match primary feed product IDs)custom_label_X(where X is 0-4)
Example Google Sheet:
| id | custom_label_0 |
|---|---|
| SKU001 | WINNER |
| SKU002 | RISER |
| SKU003 | LAGGARD |
| SKU004 | SLEEPER |
Step 3: Map the supplemental feed
- Go to the supplemental source settings
- Connect it to your primary feed
- Map the
custom_label_Xcolumn
Step 4: Schedule updates
- Manual: Update weekly based on performance reports
- Automated: Use scripts or third-party tools to update daily
Performance Tier Criteria
How to assign products to tiers (based on last 30 days):
| Tier | ROAS vs Target | Clicks | Conversions |
|---|---|---|---|
| Winner | 125%+ of target | 50+ | 5+ |
| Riser | 75-124% of target | 25+ | 2+ |
| Laggard | Below 75% | 25+ | 1+ |
| Sleeper | Any | Under 25 | Any |
Adjust thresholds based on your volume. High-volume accounts can use stricter criteria.
Automation Options
Manual approach:
- Export product performance weekly
- Calculate tier assignments in a spreadsheet
- Update supplemental feed
- Time: 2-3 hours per week
Semi-automated approach:
- Use Google Ads scripts to export data
- Process in Google Sheets with formulas
- Upload supplemental feed via scheduled fetch
- Time: 30 minutes per week
Fully automated approach:
- Third-party tools (Producthero Labelizer, Channable, DataFeedWatch)
- Daily updates based on real-time performance
- Products flow between tiers automatically
- Time: Initial setup, then minimal maintenance
When to Manually Override
Automation is useful, but sometimes you know better than the algorithm:
Override to Winner:
- New product launch with strategic importance
- Seasonal items before peak season
- High-margin products you want to push
Override to Laggard:
- Stock running low - reduce exposure
- Margin compressed due to competitor pricing
- Known quality issues
Override to Sleeper:
- Testing new creative before broader rollout
- Gathering data on repositioned products
Section 6: Layer 4 - Budget Orchestration
Same ROAS Target, Different Budgets
Use campaign-level budgets and ROAS targets suited to actual goals and margins. A shared target is one optional scenario, not a requirement for products to move between tiers. Google recommends separating PMax campaigns where different goals, budgets or targets justify it.
Example:
- Total daily budget: $1,000
- Target ROAS: 400% (for ALL campaigns)
| Campaign | Tier | Daily Budget | % of Total |
|---|---|---|---|
| PMax-Winners | Winner | $500 | 50% |
| PMax-Risers | Riser | $200 | 20% |
| PMax-Laggards | Laggard | $150 | 15% |
| PMax-Sleepers | Sleeper | $150 | 15% |
Winners get the most budget. But the target is the same. Smart bidding optimizes toward 400% ROAS in all campaigns, with budget constraints determining which products get priority.
Budget Allocation Guidelines
Conservative approach (prioritize profitability):
- Winners: 55-60%
- Risers: 20%
- Laggards: 10-15%
- Sleepers: 10%
Growth approach (prioritize volume):
- Winners: 40-45%
- Risers: 25%
- Laggards: 15%
- Sleepers: 15-20%
Testing approach (finding new Winners):
- Winners: 40%
- Risers: 20%
- Laggards: 15%
- Sleepers: 25%
Adjust based on your goals. The percentages matter less than the principle: review actual economics, then choose targets and budgets.
Campaign Naming Conventions
Consistent naming makes reporting and management easier.
Format: [COUNTRY]_[TYPE]_[FEEDLABEL]_[TIER]
Examples:
US_PMAX_OUTDOOR_WINNERSUS_PMAX_OUTDOOR_RISERSUS_PMAX_OUTDOOR_LAGGARDSUS_PMAX_OUTDOOR_SLEEPERS
Or if you don't use feed labels for structural separation:
US_PMAX_ALL_WINNERSUS_PMAX_ALL_RISERS
Monitoring and Adjustments
Weekly check:
- Are products flowing between tiers appropriately?
- Is each tier's performance in line with expectations?
- Are budget constraints causing limited-by-budget status?
Monthly review:
- Recalculate tier assignments if using manual approach
- Adjust budget percentages based on performance trends
- Consider campaign-level target adjustments based on actual goals/margins
Quarterly audit:
- Review overall architecture
- Check for segment bloat (40-variant rule compliance)
- Consider adding/removing feed labels based on catalog changes
Section 7: Implementation Checklist
Week 1: Audit and Planning
Day 1-2: Current State Audit
- Export all product performance data (90 days)
- Count products per segment in all Shopping/PMax campaigns
- Identify segments with 40+ products
- Calculate current tier distribution (Winners/Risers/Laggards/Sleepers)
Day 3-4: Architecture Design
- Decide on feed label structure (or confirm single feed)
- Map out campaign/asset group structure
- Define tier criteria (ROAS thresholds, click thresholds)
- Calculate target budget allocations
Day 5: Supplemental Feed Setup
- Create Google Sheet for supplemental feed
- Build tier assignment formulas
- Populate initial tier assignments
- Test supplemental feed connection in GMC
Week 2: Feed Label Setup (If Using Multiple Feeds)
Day 1-2: Create New Feeds
- Enable "Advanced data source management" in GMC
- Create feed labels following naming convention
- Upload product data to new feeds
- Verify all products are approved
Day 3-4: Validate Structure
- Confirm feed labels visible in Google Ads
- Check product counts per feed
- Verify no duplicate products across feeds
Day 5: Documentation
- Document feed label architecture
- Create reference guide for team
- Save naming conventions for future feeds
Week 3: Custom Label Implementation
Day 1-2: Supplemental Feed Go-Live
- Connect supplemental feed to primary feed(s)
- Verify custom labels appearing on products
- Spot-check tier assignments
Day 3-4: Campaign Restructure
- Create new campaigns for each tier (or asset groups)
- Select campaign-level targets from actual comparable goals/margins; a shared target is optional
- Configure independent tier budgets only at campaign level; asset groups share the campaign budget
- Apply listing group filters for custom labels
Day 5: Variant Rule Compliance
- Review 40+ segments and split only where theme, business controls and evidence justify it
- Document actual segment suitability; 25–40 products is a workload preference, not a pass gate
- Document segment structure
Week 4: Campaign Launch and Monitoring
Day 1-2: Soft Launch
- Enable new campaign structure at 50% of normal budget
- Monitor for errors or disapprovals
- Verify products showing in correct campaigns
Day 3-4: Full Launch
- Increase to full budget allocation
- Set up automated reporting
- Create performance dashboards
Day 5: First Week Review
- Document initial performance baseline
- Identify any products in wrong tiers
- Adjust tier criteria if needed
Ongoing Maintenance
Weekly (30-60 minutes):
- Update tier assignments (or verify automation)
- Check for budget pacing issues
- Review segment sizes for new products
Monthly (2-3 hours):
- Full performance review by tier
- Adjust budget allocations
- Review and update tier criteria
Quarterly (half day):
- Architecture audit
- Feed label review
- 40-variant rule compliance check
- Consider structural changes
Quick Reference: Decision Trees
Do I Need Multiple Feed Labels?
START: Do you sell in multiple countries?
├── YES → Consider eligible country/language source settings; separate labels are optional
└── NO → Continue
│
├── Do you have distinct product lines with different margins?
│ ├── YES → Consider feed labels per product line
│ └── NO → Continue
│ │
│ └── Do you need hard campaign boundaries?
│ ├── YES → Use feed labels
│ └── NO → Single feed is fine (use custom labels)
How Should I Split This Segment?
START: Review business control/theme needs; 40+ products alone does not require a split
│
├── Can I split by brand?
│ └── YES → Consider a brand split only with a control/theme reason and usable evidence
│
├── Can I split by product type?
│ └── YES → Split by product type
│
├── Can I split by price range?
│ └── YES → Split by price range ($0-50, $50-100, etc.)
│
└── No justified control/theme split? → Retain the group; use labels only where useful
What Tier Should This Product Be?
START: Product performance (last30 days); missing/insufficient evidence → UNCLASSIFIED
│
├── 50+ clicks AND5+ conversions AND ROAS >125% target
│ └── → WINNER
│
├── 25+ clicks AND 2+ conversions AND ROAS 75-124% target
│ └── → RISER
│
├── 25+ clicks AND 1+ conversions AND ROAS < 75% target
│ └── → LAGGARD
│
└── <25 clicks
└── → SLEEPER
Summary: The 4-Layer Feed Architecture
Layer 1: Feed Label Foundation
- Creates structural campaign boundaries
- Set in Merchant Center, immutable after creation
- Use for country, language, or major product line separation
Layer 2: The 40-Variant Rule
- Optional 40-variant review target, often 25–35 in this workload method
- Supports product-level review; does not prove or prevent cannibalization
- Split oversized segments by brand, type, price, or custom label
Layer 3: Performance Bucketing
- Winners, Risers, Laggards, Sleepers
- Applied via custom labels in supplemental feeds
- Products flow between tiers based on observed evidence, with unclassified handling when thresholds do not cover a case
Layer 4: Budget Orchestration
- Shared or different campaign-level targets chosen for actual economics
- Different budgets control priority
- Budget allocation follows actual marginal contribution and test risk; tier names do not mandate percentages
Expected results:
- Products flow to their natural performance tier
- You get surgical control without managing thousands of individual products
What to Do Next
- Audit your current setup: How many products are in your largest segment?
- Review complexity: Inspect large groups for justified theme or control changes; do not split from product count alone.
- Decide on architecture: Single feed with custom labels, or multiple feeds?
- Build your supplemental feed: Start with manual tier assignments.
- Implement gradually: Don't restructure everything at once.
The 4-Layer Feed Architecture isn't about complexity. It's about giving Google's algorithm the constraints it needs to make smart decisions on your behalf.
Measure contribution margin and actual outcomes after any architecture change; labeling and automated budget routing do not guarantee ROAS or profitable scale.
Stop funding both sides of the war. Build the architecture. Let your products win.
For questions or implementation support, reach out on X/Twitter.
Choose who handles the next step.
Use the reference yourself, book a focused paid working session, or have Tegra handle the ongoing channel work.
Search, Shopping, Performance Max and Demand Gen campaigns, plus the research, product feeds, static and video creative, and landing, offer and pre-sale pages behind them.
Explore managed Google Ads → · See paid working sessions →