A Merchant Center supplemental data source lets you add or override attributes on top of your existing product feed, without changing the primary file your systems already rely on. The two highest-value uses are patching missing attributes that cause disapprovals and keeping price and availability current through the Take latest rule. Done well, this means fewer rejected products, richer assets for Performance Max, and faster fixes than waiting on an engineering ticket.
TL;DR:
- Supplemental data sources are ideal for fixing missing attributes, updating prices and availability more frequently, and tagging products for campaign segmentation.
- Set up requires choosing the appropriate input method, matching rule, and aligning metadata, with a practical custom match limit of 30,000 rows.
- Attribute rules, especially “Take latest” and “Set to,” help maintain current and normalized product data without editing primary feeds.
- Testing rules on a small subset before full implementation minimizes risks of unintended widespread changes.
- Enriching the Merchant Center data source directly influences Performance Max campaign assets and performance, making feed quality management essential.
Table of Contents
- When should you use a supplemental feed?
- How to create and upload a supplemental data source
- Attribute rules and rule recipes that fix common feed gaps
- How supplemental feeds work with Performance Max and page feeds
- Testing and governance: how to roll out changes safely
- Why a feed-first approach beats chasing campaign settings
- How we can help you put this into practice
- FAQ
- Sources
When should you use a supplemental feed?
Not every feed problem needs a supplemental source, so it helps to check your situation against a short list before you build one. Supplemental feeds earn their place when you have missing required attributes (size, colour, GTIN), price or availability that changes more often than your primary feed updates, a short-term promotion you want to label without a code release, or products you need to tag for campaign segmentation.
Before committing time to this, run through the checklist below:
- Product count affected: a handful of SKUs might be faster to fix by hand; thousands justify a rule-based fix.
- Update frequency: daily or hourly changes (stock, price) are exactly what Take latest is built for.
- Engineering constraints: if your primary feed is locked behind a release cycle, a supplemental source is your fastest lever.
- Risk appetite: test on a narrow subset first, since a badly built rule can touch far more SKUs than intended.
One constraint to flag early: a supplemental source can only enrich or override attributes on products that already exist in your primary feed, making professional moving and relocation services in Melbourne like Onyx Removals’ retail delivery solutions a key operational complement for regional inventory logistics. It cannot add or remove products, and custom matching carries a 30,000-row limit along with an allowlisting requirement, which shapes how you plan the build.
How to create and upload a supplemental data source
Setting one up takes a few steps inside Merchant Centre, and the choices you make about input method and matching determine how smoothly it runs once it is live.
- Go to Settings → Data sources → Supplemental sources, then select “Add supplemental product data” to start a new source.
- Choose your input method. A flat file suits infrequent, manual updates; a Google Sheets template works well for a marketing team updating promotions directly; an API feed suits high-frequency, automated updates such as live stock levels.
- Set your matching rule. The safest option is matching on the product ID field exactly, since it avoids ambiguity. Custom data source matching on attributes like brand or product_type is useful for category-wide labelling, but it requires enabling a limited feature (often via a support request) and is capped at 30,000 joinable rows.
- Align naming and metadata. Match the feed label, language, and country of sale between your primary and supplemental sources, since a mismatch here is one of the most common causes of a failed join.
30,000 rows is the practical ceiling for a custom-matched supplemental source. If your catalogue is larger, partition the data by brand or region and run several supplemental sources in parallel rather than trying to force one oversized file through a single custom join.
A supplemental data source can be built from a file, a Sheet, or an API, but whichever method you pick, it only ever overrides attributes on products already present in your primary feed.
Attribute rules and rule recipes that fix common feed gaps
Attribute rules sit between your data sources and the attributes Google actually uses, letting you transform, standardise, or combine values without editing the underlying file. By default, Google applies a basic precedence between sources, but for most feed problems you will want to write explicit rules rather than rely on the default behaviour.
A few recipes cover most of the gaps PPC managers run into:
- Prepend brand to title: use Set to with a template combining the brand attribute and the existing title, which improves matching for generic product names.
- Keep price and availability current: use Take latest so the most recently updated source (often your fast-moving supplemental feed) wins over a slower primary feed.
- Normalise variant naming: use Find & Replace to standardise colour or size labels that arrive inconsistently from different systems.
- Populate multi-value attributes: use Set to with multiple values where an attribute like product_type needs more than one entry.
Rule conditions can be combined with AND/OR logic, so you can target a rule narrowly (for example, only products where availability equals “out of stock”) rather than applying it catalogue-wide. After building a rule, reprocess the affected data source and check the preview before publishing.
One caveat worth repeating: depending on configuration, attribute rules can affect both supplemental and primary values, so a rule built carelessly can propagate across far more SKUs than you intended.
Pro Tip: Build and test every new rule on a narrow subset of SKUs first, then widen it once the preview and diagnostics confirm it behaves as expected.
How supplemental feeds work with Performance Max and page feeds
Performance Max builds its Shopping assets directly from your Merchant Centre data source, so enriching that data through a supplemental feed has a direct effect on what the campaign can show.
- Attach the right data source at setup. Performance Max pulls from whichever Merchant Centre source you select when the campaign is created, so confirm this before launch rather than changing it later.
- Use page feeds for landing-page control. Page feeds and custom labels let you steer traffic to specific product or category pages during final-URL expansion, which complements the attribute work in your supplemental feed.
- Richer data means broader asset coverage. Better descriptions, higher-resolution images, and accurate custom labels give Performance Max more raw material to build Shopping assets and improve how often your products serve.
- Lock objectives and data sources at setup. Treat the data source selection as a setup-stage decision, not something to revisit casually mid-campaign, since changes here can disrupt asset generation.
Testing and governance: how to roll out changes safely
A rule that looks correct in isolation can still cause a regression once it touches live campaigns, so a short governance routine protects you from that risk.
- Check Diagnostics and Product issues immediately after any rule change to confirm attributes processed as expected and to catch new disapprovals early.
- Sandbox aggressive changes by duplicating the primary feed for organic-only testing, or by trialling a rule on a narrow subset before a full rollout.
- Monitor a short set of KPIs after each change: product disapprovals, impression share, clicks, conversions, and ROAS, checked daily for the first week.
- Keep a change log recording what rule was applied, when, and to which subset, so a regression can be traced back to its cause quickly.
- Have a rollback ready: disable the specific rule or data source rather than unpicking the whole feed when something goes wrong.
Why a feed-first approach beats chasing campaign settings
Most PPC managers spend their time adjusting bids, budgets, and audience signals, while the feed sits untouched in the background. That is backwards. Performance Max and Shopping campaigns are built entirely from product data, so a feed with missing attributes or stale prices puts a ceiling on performance that no amount of bid tweaking will lift.
The practical order of operations is audit first, fix the quick wins (missing attributes, stale availability), then automate the fixes through attribute rules, and only then shift attention to monitoring and scaling. Skipping straight to campaign optimisation without this groundwork tends to waste spend on products that were never eligible to serve properly in the first place.
Whether this is worth doing in-house depends on volume and change velocity. A catalogue of a few hundred SKUs with occasional updates is manageable manually. A catalogue in the thousands, with daily price or stock churn, usually justifies either dedicated engineering time or a managed service built around feed work.
For deeper reading on the primary-feed side of this work, our Google Shopping feed setup guide and feed optimisation tips cover the checks worth running before you ever touch a supplemental source.
— Biplab
How we can help you put this into practice
We run eCommerce PPC as our entire focus rather than one service among many, which is why feed work sits at the centre of how we manage Google Shopping and Performance Max accounts. If your feed is holding back performance, a managed audit finds the gaps faster than trial and error.
Our feed and campaign work covers:
- Feed audits that produce a prioritised list of attribute gaps, ranked by the effort to fix and the opportunity each one represents.
- Attribute-rule implementation, building and testing the rule recipes covered above against your actual catalogue.
- Performance Max campaign management, aligning data source selection, page feeds, and asset groups once the feed itself is in good shape.
- One-off implementation projects for teams that want the fix done once rather than managed ongoing.
A free Google/Facebook Ads audit is the fastest way to see where your feed stands today, and our PPC management service picks up from there with no long-term contract required.
FAQ
What is a Merchant Center supplemental data source?
It is an additional data source you upload to enrich or override attributes on products that already exist in your primary feed. It cannot add new products or remove existing ones, and it supports file, Google Sheets, or API uploads.
Can a supplemental feed add new products to my catalogue?
No. A supplemental source only provides or overrides attributes for products already present in your primary feed; new products still need to go through the primary data source.
What is the row limit for custom matching in a supplemental feed?
Custom data source matching on attributes like brand or product_type is capped at 30,000 joinable rows, and enabling the feature itself is limited and may require a support request. Matching on product ID avoids this limit entirely.
How does Take latest differ from other attribute rule operations?
Take latest automatically uses whichever data source was updated most recently for a given attribute, which suits fast-changing values like price and availability. Other attribute rule operations such as Set to, Append/Prepend, and Find & Replace apply fixed transformations regardless of update timing.
Does Performance Max require a specific Merchant Center data source?
Performance Max builds its Shopping assets from whichever Merchant Centre data source you select at campaign setup, so the source needs to be chosen correctly before launch. Enriching that source, including through a supplemental feed, directly affects how many assets the campaign can generate.
Sources
- Set up custom data source matching – Google Merchant Center Help
- Optimization tips for Performance Max campaigns with a Google Merchant Center feed – Google Ads Help