Demand Gen Data Feeds: Dynamic Ads Without Merchant Center

Demand Gen business data feeds are Google’s newest answer to a long-standing gap in feed-based advertising: dynamic ads for businesses that don’t sell retail products. As Search Engine Land reported on July 17, 2026, advertisers can now attach a structured data file to a Demand Gen campaign and let Google assemble the ads — with no Google Merchant Center account anywhere in the flow.

That single omission is the story. For years, dynamic ad formats in Google’s ecosystem have been gated behind Merchant Center — a product built for ecommerce catalogs, not hotel rooms, property listings, or dealership inventory. Travel, real estate, and automotive advertisers either forced their inventory into a retail schema or gave up on dynamic formats entirely. Business data feeds remove that gate for exactly those verticals.

This guide covers what launched and what it deliberately excludes, the setup path through the Ads Business data tool, the Google Display Network-only limitation nobody should gloss over, a genuine contradiction inside Google’s own help documentation, and a decision matrix for choosing between Google’s now-parallel Demand Gen feed mechanisms. Everything below is sourced to Google’s Help documentation and the trade press coverage from July 17–19, 2026.

The announcement surfaced through Search Engine Land’s July 17 report, with same-day independent coverage from PPC News Feed — which credits the spot to PPC commentator Hana Kobzová — and a mention in Search Engine Roundtable’s daily recap. Google’s own documentation for the feature lives in the “Use business data feeds in Demand Gen campaigns” Help article. No Google spokesperson has commented publicly — every Google-attributed statement in this post comes from that Help-documentation text.

The mechanics: a business data feed is a structured file listing the items, services, or inventory an advertiser wants to promote — item IDs, image URLs, landing-page URLs. Google matches those rows to audience interest signals and assembles the ad dynamically, replacing the manually built creative Demand Gen otherwise requires. Google’s Help documentation frames the intended audience directly: “This option is helpful for businesses in travel, flights, real estate, and automotive industries that do not use Google Merchant Center.”

Why does that sentence matter so much? Because it marks the first time Demand Gen’s dynamic machinery has been decoupled from the retail stack. Adegbola’s broader framing in the same piece: “While Demand Gen has steadily gained new automation features, much of its dynamic functionality has been geared toward ecommerce. Business data feeds broaden that capability to service-based and inventory-driven businesses, signalling Google’s push to make Demand Gen more versatile beyond retail.” For a hotel group with rotating seasonal availability or a dealership with a lot that turns over weekly, the pitch is that the feed — not a designer — keeps the creative current.

Per Google’s Instructions section, the setup path never touches Merchant Center. The sequence:

1. Open the Tools menu → Business data in Google Ads.
2. Click the plus button and choose “Dynamic ad feed.”
3. Pick the industry template that matches your inventory — travel, flights, real estate, automotive, or local services.
4. Upload the completed feed via CSV or secure SFTP.
5. Wait out Google’s policy review of the feed contents.
6. Attach the approved feed to a Demand Gen campaign at campaign creation.

Two settings determine whether anything actually serves. First, the campaign must have the Google Display Network enabled in its settings — a structural requirement, since GDN is currently the only surface these assets can appear on. Second, standard Smart Bidding strategies remain available on business-data-fed campaigns, including Target CPA and Maximize Conversions — Google frames the continuity as a benefit, and it means feed adoption doesn’t force a bidding migration.

The pause behavior deserves a closer read. Google does let you pause a business data feed after launch, via the campaign’s “Product feeds” toggle under campaign settings — but the same doc warns that pausing “may negatively impact performance.” Combined with the permanent feed-type selection, the design pushes advertisers toward committing to a feed structure up front rather than iterating on it mid-flight. Treat the feed schema decision with the same care you’d give a campaign-structure decision, because functionally that’s what it is.

Demand Gen’s sales pitch has always been its footprint. Google’s own Demand Gen overview documentation claims reach of up to 3 billion monthly active users across YouTube (including Shorts), Discover, Gmail, Maps, and the Google Display Network — with over 50 billion global daily views on Shorts alone. Business data feeds, during this phase, touch exactly one of those five surfaces.

The budgeting implication is direct: a business-data-fed Demand Gen campaign is, today, functionally a GDN dynamic campaign wearing Demand Gen’s bidding and audience machinery. That is not worthless — but it is not the 3-billion-user, five-surface footprint the Demand Gen brochure describes, and none of the launch coverage spells that distinction out. Forecast reach and CPMs against display expectations, not against your existing Demand Gen video-plus-Discover benchmarks. And since Demand Gen billing has its own recent quirks, revisit Demand Gen’s CPM billing shift before you set budgets — impression-based billing changes what a display-only footprint costs you.

No pricing, budget minimums, or CPC/CPM figures specific to business data feeds have been published anywhere in the sourced coverage. Treat any confident cost forecast for this feature as invented — including your own. The honest position is qualitative: GDN inventory generally clears cheaper than YouTube and Discover placements, so early feed campaigns will likely skew toward lower-cost, lower-intent impressions until the surface list grows.

Here is the part every other write-up skipped. The same Google Help article that documents this feature contains two sections that flatly disagree with each other — and if you build a feed off the headline alone, the Prerequisites section will send you on a detour the Instructions section never asks for.

The Prerequisites section lists steps to set up your account for Google Merchant Center, create a feed for your Merchant Center account — with an approval window of up to 3 days — and link Merchant Center to Google Ads. The Instructions section of the very same page then describes creating the feed natively in the Ads Business data tool, with no Merchant Center step anywhere in the flow. Search Engine Land’s reporting sides with the Instructions: the update does not require a Merchant Center feed.

Our read — and it is a read, not a Google statement: the Prerequisites block looks like carry-over boilerplate from Demand Gen’s older, Merchant-Center-based product feed, a separate and longstanding feature that has its own Help article. The Instructions section is the one that matches the feature’s entire stated purpose — serving businesses that, in Google’s own words, “do not use Google Merchant Center.” But we’d rather show you the contradiction than silently resolve it.

The July 17 launch did not replace anything. Demand Gen’s Merchant-Center-based product feed for ecommerce sellers still exists as its own feature, and automotive advertisers got a separate Merchant-Center-based feed capability back in May 2026. That means the real question for an advertiser is no longer “should I use a feed” but “which of Google’s parallel feed mechanisms does my business actually belong in.” No source article lays this out side by side, so we did:

Two rows deserve annotation. The automotive row is the strange one: dealers now have two Google-sanctioned feed routes into Demand Gen, announced eight weeks apart, with different accounts, different schemas, and different surface behavior. And the ecommerce row is a reminder that this launch changes nothing for retail sellers — if you sell products, the Merchant-Center product feed remains your mechanism, and the fundamentals in our Shopping product feed strategy guide still apply. Feed quality disciplines — clean identifiers, sharp imagery, accurate landing pages — transfer directly from the Shopping world to business data feeds, even though the accounts involved do not.

Because this launch is GDN-only and each campaign is permanently locked to its feed-type choice, the advertiser question is not “should we use this” — it’s “is GDN reach worth building a feed for today, or do we wait for YouTube, Discover, and Gmail support.” Here is how we’d slice it:

One structural note for agencies: the permanent feed-type lock turns campaign scaffolding into a client-facing decision. If a client’s inventory could plausibly fit two templates — a property developer with both listings and local services, say — the template choice deserves a documented rationale before anything is saved. This is exactly the kind of feed-architecture and campaign-structure work our paid media team handles when accounts adopt new Google formats early: the cost of a wrong structural choice here is a rebuild, not a settings edit.

Zoom out and July 17 stops looking like an isolated feature drop. Shopping campaigns run on Merchant Center feeds. Demand Gen gained Merchant-Center product feeds for ecommerce. May 2026 brought Merchant-Center automotive feeds to Demand Gen alongside Maps placements and AI campaign creation. Performance Max campaigns lean on the same structured-data substrate. Business data feeds extend the identical pattern — structured inventory in, machine-assembled ads out — to verticals that never had a feed entry point. Even the same news week carried a second Merchant-Center-adjacent change: on July 16, Google emailed advertisers that Local Inventory Ads will become a default in Shopping campaigns, a separate story we cover on its own.

The trend reading: Google is systematically converting ad creation from an asset-production problem into a data-engineering problem. Every new feed surface moves the advertiser’s job further from “make the ad” and closer to “maintain a clean, current, structured representation of what you sell” — and it moves creative assembly, placement, and increasingly bidding into the black box. For non-retail verticals, business data feeds are the admission ticket to that machine, and the price of admission is feed hygiene.

Looking forward — and this is projection, clearly labeled as such: Google calling the GDN restriction a “phase” in its own documentation is the strongest available signal that broader surface support is the intent, even though no expansion has been announced and no date exists. If the phase resolves the way Google’s phased rollouts usually aim to, advertisers who built clean feeds during the GDN-only window would inherit YouTube-and-Discover distribution with the structured data already in place. That possibility, not today’s display inventory, is the strategic case for building early — and it remains a possibility, not a promise.