Gold IRA Buyers on Demand Gen: The Placement Controls That Survived the Display Migration (and the Two That Quietly Didn’t)

Questions this article answers:

• Which placement exclusion lists still work after the Display-to-Demand Gen migration?
• Does the GDN inventory only toggle actually exclude YouTube inventory?
• How do I keep Demand Gen from blending YouTube inventory into a gold IRA campaign?
• What is the right account structure for gold IRA advertisers after the Demand Gen migration?
• How do I stop Smart Bidding from optimizing toward lead-form spam?
• How do I audit a Demand Gen campaign for unenforced exclusions?

Demand Gen placement controls for gold IRA advertisers look almost identical to the old standalone Display ones. The lists are still there. The toggles are still there. The enforcement scope is not.

A precious-metals media buyer migrates Display into Demand Gen, sees the exclusion list carry over, and goes back to monitoring CPL. A few weeks later the lead CPL still looks fine and funded-rollover CPA has quietly drifted. The leak is real. The report is honest. The controls the buyer thinks are protecting them are no longer scoped to the inventory doing the damage.

The two controls that broke are the two that flat-CPL gold IRA economics depend on most. This piece names them, shows where the enforcement actually lives, and gives you the two-account-group split you should be running by Monday.

Why The Migration Hit Gold IRA Harder Than Most Verticals

Gold IRA runs on flat-CPL economics where one bad inventory category eats the entire margin. The maximum profitable CPL is a direct function of gross profit per funded rollover and the lead-to-funded-rollover conversion rate. Funded rollover (an actual retirement account moved into precious metals at the custodian) is the only event that matters. A lead form fill is not revenue. It is a signal, and not always a clean one.

That math is brutal on blended inventory. Search lead-gen verticals can absorb a noisy placement category because their funnel qualifies downstream. Gold IRA cannot. Per Google Ads Help, Demand Gen serves across YouTube, Shorts, Discover, and Gmail, with Display now managed through the same campaign type. For a precious-metals buyer who used to run a clean GDN-only Display object, the inventory surface they are exposed to grew.

The controls that policed standalone Display did not all expand with it.

What Demand Gen Inherited From Display, And What It Quietly Re-Scoped

Google’s 2026 product update confirmed that Display is being managed through Demand Gen rather than as a separate campaign type (Google Ads Blog). The GDN-only inventory toggle survived as a sub-control. The standalone Display enforcement model did not.

Controls that carried over with their enforcement intact:

• Topic exclusions at the campaign level
• Content-label exclusions (sensitive content categories)
• Content suitability settings (limited, standard, expanded inventory)
• Account-level placement exclusions for direct URLs
• Negative keyword lists at the campaign level

Controls that look the same but no longer cover the inventory you assumed:

• Negative placement lists that were scoped to your old Display campaign
• The mental model that “GDN only” means “not YouTube”

Those two are the failure modes worth naming separately.

Which Placement Exclusion Lists Still Work After The Display-To-Demand Gen Migration

Placement exclusion lists from your old Display campaign still exist in the UI, but their enforcement does not extend to the YouTube and Shorts inventory Demand Gen blends into the same campaign by default. They police GDN domain placements. They do not police video inventory that was never part of the original list’s scope.

There is also a practical ceiling problem. Long brand-safety block lists built up over years on standalone Display, often pulled from DV360 MFA categories and shared industry block lists, can run into UI and account-level limits when imported. In our experience, the failure modes vary by tool and import path, so treat any large imported list as suspect until you have spot-checked that the entries you care about are actually still listed in the destination account.

The practical implication: stop treating the legacy URL exclusion list as your primary brand-safety surface. It was the right tool for standalone Display. It is the wrong altitude for Demand Gen. Rebuild around three layers:

1. Content-label exclusions set to exclude sensitive social issues, tragedy and conflict, sensational and shocking, and any embedded MFA-adjacent labels. These apply across the blended surface.
2. Topic exclusions covering gambling, crypto, sensational news, and politics. Topic-level guards survive the migration with their scope intact.
3. A managed-placements allowlist for the content-only side of your structure (covered below). This is what replaces the URL block list for the inventory you actually want exposure to.

Does The GDN Inventory Only Toggle Actually Exclude YouTube Inventory

The GDN-only inventory toggle inside Demand Gen limits where new ads serve, but it does not reproduce the old standalone Display enforcement model. Treating it as a hard wall is the failure mode. It is one layer of a stack, not the whole stack.

The toggle is doing what Google says it does. The problem is that buyers read it as a hard wall and treat the rest of the placement-control stack as redundant. It is not redundant. It is the only thing standing between your funded-rollover budget and a blended video surface.

How Do I Keep Demand Gen From Blending YouTube Inventory Into A Gold IRA Campaign

Demand Gen does not expose a per-asset-group control that lets you run prospecting and funded-rollover creative under the same campaign while isolating YouTube inventory for one and not the other. This is the altitude mismatch that burns precious-metals buyers most often.

Asset groups do not independently constrain inventory exposure inside a single Demand Gen campaign. Inventory choices that exist at the campaign level apply to every asset group inside that campaign. If you need different inventory exposure for prospecting versus funded-rollover creative, you need different campaigns. In the gold IRA case you usually need different account groups.

The broader point: account structure has to do the work the UI doesn’t. If Google won’t let you isolate inventory by asset group, you isolate it by campaign. If campaign-level controls don’t get you what you need, you isolate by account group.

What Is The Right Account Structure For Gold IRA Advertisers After The Demand Gen Migration

Split into two account groups: one Demand Gen object configured for blended reach with the tightest available exclusions, and one content-only object with a managed-placements allowlist of pre-vetted finance publishers. This is the structural fix. Run it by Monday.

Group A: Demand Gen, locked-down version

Configure this campaign as your blended-reach prospecting object, with the inventory surface tightened as far as the platform allows:

• Content suitability: limited inventory
• Topic exclusions: gambling, crypto, sensational and shocking, politics, tragedy and conflict
• Content-label exclusions: every available MFA-adjacent and sensitive-content label
• Conversion event: funded rollover only (covered in the next section)

This is the version of Demand Gen you can actually live with. It will reach less. It will also stop training Smart Bidding on inventory that converts forms and never funds accounts.

Group B: Content-only object with a managed-placements allowlist

This is your direct-response surface, scoped tight:

• Inventory: managed placements only, no open inventory, no blended YouTube
• Allowlist: a hand-built set of finance and retirement-adjacent publishers (the Kiplinger, Barron’s, MarketWatch tier, plus the vertical-trust sites your audience actually reads)
• Same content-label and topic exclusions as Group A, as defense in depth
• Same funded-rollover-only conversion event

Build the allowlist by hand. Pull from your historical site-level placement reports on standalone Display, filter for publishers with meaningful impression volume and a meaningful assist-to-funded-rollover ratio, and discard anything that looks programmatic-resold. The list is small on purpose. A bloated allowlist defeats the point.

For more on how account structure replaces UI controls in this vertical, see our two-pool media buying structure for precious-metals advisors.

How Do I Stop Smart Bidding From Optimizing Toward Lead-Form Spam

Feed Smart Bidding only the server-side funded-rollover conversion, and demote every upstream lead event to observation-only or secondary. If the algorithm trains on form fills, it will find made-for-advertising inventory that converts the form at a great rate and never funds an account.

The mechanism is straightforward. Smart Bidding optimizes toward whatever you tell it counts. Low-quality publishers can be very good at producing form fills from low-intent users, and very bad at producing funded retirement rollovers. If your conversion action set includes the form submit as a primary conversion, Demand Gen will learn the shape of users who fill forms on those sites and bid up to find more of them.

The fix has two parts:

1. Use offline conversion import or enhanced conversions for leads to send only the funded-rollover event back to Google as the primary conversion (see Google Ads Help on enhanced conversions for leads). The funding event happens days or weeks after the form fill, lives in your CRM or custodian system, and is the only signal worth training on.
2. Set every upstream event to observation-only, secondary, or not-a-conversion. Form fills, qualified-lead designations, appointment-set, even verbal-commitment events. They give you reporting visibility without contaminating the bid model.

The formula that anchors this: effective CPA on funded rollover = total campaign cost ÷ funded rollovers. That is the only number Smart Bidding should be optimizing against in this vertical. For the broader two-event discipline that holds up under Smart Bidding pressure, see server-side conversion tracking for insurance lead buyers. Same idea, different vertical.

How Do I Audit A Demand Gen Campaign For Unenforced Exclusions

Pull the placement report, segment by inventory surface, and check whether your negative placement list is actually preventing the impressions you assume it is. This is a 30-minute audit that catches most of the silent leakage.

The checklist:

1. Open the placement report and segment by inventory surface. YouTube, GDN, Discover, Gmail. Look at what is still visible and what now rolls up under “Other.” The opaque bucket is where MFA exposure hides.
2. Cross-reference your negative placement list against actual YouTube Shorts and in-stream impressions. If you have impressions on channels or video categories your list “covered” on standalone Display, the enforcement gap is confirmed.
3. Inspect the conversion action set powering Smart Bidding. Is the primary conversion the form fill or the funded rollover? If it is the form fill, the bid model is training on the wrong signal regardless of how clean your placements are.
4. Check content suitability vs. managed placements. These are two different enforcement layers. Buyers conflate them all the time. Content suitability is the category filter. Managed placements is the allowlist. You need both, configured deliberately, not one as a stand-in for the other.
5. Spot-check imported exclusion lists. Pick fifteen domains you know were in your old Display block list and confirm they are still listed in Demand Gen. If any are missing, treat the whole list as suspect and rebuild from topic and content-label exclusions plus the managed-placements allowlist.

What “enforcing correctly” looks like: your placement report shows impressions concentrated on publishers and YouTube channels you explicitly approved, the conversion action set lists the funded rollover as primary and everything else as secondary, and your topic and content-label exclusions are tight.

What “enforced on paper but leaking” looks like: a giant negative placement list nobody has audited, form fill as the primary conversion, and a placement report where a large share of impressions rolls up under “Other.”

For a broader walkthrough of the audit workflow across account types, see our lead-gen operator’s guide to auditing Google Ads placements after the Demand Gen migration.

Frequently Asked Questions

Which placement exclusion lists still work after the Display-to-Demand Gen migration?

Topic exclusions, content-label exclusions, content suitability settings, and account-level URL exclusions all carried over with their enforcement scope intact. What did not carry over cleanly is the negative placement list from your standalone Display campaign, which does not extend to the YouTube and Shorts inventory Demand Gen blends in by default. Rebuild around topic and content-label exclusions plus a managed-placements allowlist, not the legacy URL list.

Does the GDN inventory only toggle actually exclude YouTube inventory?

The GDN-only inventory toggle limits where new ads serve, but it lives inside a Demand Gen object and does not reproduce the old standalone Display enforcement model. Treat it as one layer of a stack, not as a hard wall. The isolation you need for flat-CPL economics comes from account structure, not a single toggle.

How do I keep Demand Gen from blending YouTube inventory into a gold IRA campaign?

Demand Gen does not expose per-asset-group controls that isolate YouTube inventory inside a single campaign, so the answer is structural. Split prospecting creative and funded-rollover creative into different campaigns, and run your content-focused inventory through a separate object with managed placements only. Account structure is the only altitude where this isolation actually holds.

What is the right account structure for gold IRA advertisers after the Demand Gen migration?

Split into two account groups: a Demand Gen object configured for blended reach with the tightest available topic and content-label exclusions, plus a content-only object with a managed-placements allowlist of pre-vetted finance publishers. Feed both groups only the server-side funded-rollover conversion so Smart Bidding does not learn the shape of MFA-site form fillers. Account structure does the work the UI no longer does for this vertical.

How do I stop Smart Bidding from optimizing toward lead-form spam?

Set the funded-rollover event as the only primary conversion in Smart Bidding, and demote every upstream lead event to observation-only or secondary. Use offline conversion import or enhanced conversions for leads to send the funding signal back to Google days or weeks after the form fill. If the algorithm trains on form submits, it will find inventory that converts the form and never funds an account.

How do I audit a Demand Gen campaign for unenforced exclusions?

Pull the placement report, segment by inventory surface, and check whether the primary conversion is the funded rollover, not the form fill. Look for impressions on YouTube Shorts and in-stream that your old negative placement list should have caught, and watch the size of the “Other” bucket in your placement report. The leakage shows up there before it shows up in funded-rollover CPA.

Talk To Elevarus About Auditing Your Demand Gen Configuration

For flat-CPL verticals like gold IRA, the placement-control altitude inside Demand Gen no longer matches the economics. Account structure has to carry the brand-safety load the UI used to. That is structural work, not a checkbox flip, and it is worth doing before your next funded-rollover cohort comes in showing a CPA you cannot explain.

If you are spending $25k to $500k a month in precious-metals paid media and want a practitioner audit of your Demand Gen configuration, book a free consultation with Elevarus. We will look at your campaign settings, your conversion action set, your exclusion lists, and whether your account structure actually isolates the inventory your funded-rollover math depends on.