How to Use Product Feeds in Demand Gen Campaigns

Begin with the Merchant Center account, product data source, linked Google Ads account, and the marketing methods enabled for the products. Google lists those items as prerequisites for Demand Gen product feeds. Review item IDs, titles, descriptions, availability, price, images, landing pages, and country coverage. Resolve disapprovals and stale inventory before the campaign can spend. A campaign filter cannot repair a product record that is ineligible or sends a shopper to a contradictory destination.

Choose products that answer one audience and merchandising question. Record the business objective, eligible countries, catalog owner, margin guardrail, inventory owner, creative owner, landing-page owner, and measurement period. Google supports a campaign with one product, but its guidance recommends at least four eligible products to maximize placement eligibility and generally recommends a broader relevant set. Treat those numbers as platform guidance, not a promise of performance. Keep a smaller canary only when its limited reach is an accepted test constraint.

When creating a Demand Gen campaign, select the product-feed option and the intended Merchant Center account. Google allows a feed label or all available feeds, followed by selection of specific products or the full catalog. Record the chosen account, feed label, campaign objective, conversion goals, locations, languages, bid strategy, dates, budget, and product filter. Verify the account identity rather than relying on a familiar account name in a manager view.

Google says construction-time product filtering supports one filter method and OR logic, while later subdivisions and exclusions can create narrower combinations. Design the grouping on paper before clicking. Use stable product IDs, product types, brands, conditions, or custom labels that the feed owner understands. Avoid overlapping groups that place the same item into multiple tests without a reason. Save an export or screenshot of the included and excluded products so later catalog edits do not silently change the experiment population.

Demand Gen can use product imagery and details from the Merchant Center feed alongside the campaign's image, video, text, logo, and call-to-action assets. Assign one owner to each layer. The catalog owner protects product truth; the creative owner protects the campaign story; the landing-page owner protects destination accuracy. Review how the product set appears across the eligible visual surfaces without assuming one preview represents every placement or device.

Check image crop, legibility, product identity, price and availability consistency, final URL, and mobile landing behavior for representative items. Do not add promotional claims to an image or headline unless the landing page and product data support them. If regional availability differs, follow Google's documented limitations and workarounds rather than showing a product nationally and hoping the destination corrects the mismatch. Pause affected items when inventory, policy, or destination evidence is not ready.

Inspect the Products tab in Google Ads and the item diagnostics in Merchant Center after setup. Google documents common Demand Gen feed issues including too few eligible products, product disapprovals, account suspension, and unsupported regional availability and pricing feeds. Classify each issue by item, reason, source system, owner, and next review time. Fix the catalog or policy evidence at its source, then request the supported review or wait for processing instead of duplicating the product into a new ID.

Confirm that at least one representative product from every intended group is approved, included, and able to serve. Verify that excluded or out-of-stock items are not in the active group. Record the time of the check because feed and campaign changes can take time to appear. A green campaign status is not enough: compare the active product population with the approved ledger, and treat products with zero delivery as an investigation rather than automatically increasing bids or broadening the audience.

Google's product reporting provides a centralized view of Merchant Center products across supported campaign types and channels. Use it to compare item, brand, category, eligibility, cost, clicks, conversions, and conversion value only at a documented grain. Product imagery from dynamic ads can receive attribution differently from ordinary ad assets, so do not add asset rows to product rows and call the total reconciled. Preserve the report columns, attribution setting, date range, currency, filters, and download time.

Join the report to product margin, inventory, returns, and landing-page evidence only through stable keys and completed periods. Classify each product as supported for continued testing, inconclusive, constrained by eligibility or inventory, or ready to stop. Do not claim that the feed caused incremental sales from a before-and-after chart. Expand only when the product set is still eligible, destinations are accurate, inventory can support the exposure, measurement is trustworthy, and the result clears the business guardrail under the documented reporting method.

Add a weekly product-feed change log that names new items, removed items, filter changes, disapprovals, landing-page changes, and inventory constraints. Compare the active campaign population with that log before explaining performance movement. If a catalog release changes many products at once, preserve the prior grouping and wait for a complete reporting period before making a second structural change. This keeps product availability, creative changes, audience changes, and bidding changes from becoming one untraceable intervention.