DV360 Explained: Campaign Settings, Hierarchy & Reporting

Most people who pick up DV360 after running Google Ads assume the mental model transfers cleanly. It doesn't. The hierarchy is different, the levers are different, and the settings buried deep in the UI can quietly drain budget for weeks before anything surfaces in performance data. The account structure questions we see repeated most often — across forums, tutorial comment sections, and support tickets — aren't about basic setup. They're about the gaps between what a campaign looks like when you create it and what it actually does when it runs.

This post covers those gaps: account hierarchy, the campaign settings that actually matter, and how to read DV360 reporting without fooling yourself.

The Hierarchy Is Not Just Organizational — It's Functional

DV360 runs on a five-layer hierarchy: Partner → Advertiser → Campaign → Insertion Order → Line Item. Most tutorials introduce this as a filing system. It isn't. Each layer does real work, and conflating them causes real problems.

The Partner level is where billing, user access, and cross-advertiser data sharing live. If you're an agency managing multiple brands, the Partner is your master account. Brand safety allowlists and blocklists set at Partner level cascade down — which means a blocklist added for one client can affect inventory availability for another if you're not careful about scope.

The Advertiser level is where conversion tracking, audience lists, and creative assets attach. Floodlight tags — DV360's conversion tracking mechanism — are configured here. If you set up Floodlight at the wrong advertiser, your line item optimization has nothing real to learn from.

Campaigns are primarily a budgeting and date-range container. You set a total budget and flight dates. The campaign itself does almost nothing else. Many advertisers over-configure at this layer and then wonder why line-item-level frequency caps aren't behaving — it's because the campaign layer doesn't own frequency.

Insertion Orders (IOs) are where pacing and budget allocation between line items get controlled. IO-level pacing determines how evenly budget flows over the flight. Set it to "ASAP" when you meant "even" and you'll burn through budget in the first few days of a flight.

Line Items are where targeting, bidding, and creative assignment happen. This is the layer most people spend their time in, which makes sense — but it also means that mistakes at the IO or campaign level above stay invisible longer.

The table below maps the major controls to the exact layer that owns them. When two layers appear to cover the same setting, the lower layer narrows — it can never expand what the layer above permits.

What "Additional Campaign Settings" Actually Controls

The additional campaign settings in DV360 — covered in depth in Lesson 10 of the DV360 tutorial series — are where a lot of quiet waste hides. These settings sit outside the core campaign creation flow, so many advertisers skip them on first setup and never come back.

The settings that matter most in practice:

Demographic targeting at campaign level. You can restrict delivery by age, gender, and parental status here. The catch: if you leave this open at campaign level but restrict it at line item level, you're applying two independent filters. An impression only serves if it passes both. Depending on how you've set them up, you may be targeting a far narrower slice than you intended — or a far wider one.

Geography and language. DV360 lets you set geography at multiple layers. Line-item-level geography overrides campaign-level settings for that line item, but only in one direction — you can narrow, not expand, what the campaign allows. If your campaign is restricted to the US and you try to target Canada at the line item, Canada won't serve.

Brand safety controls. At the campaign level, you set the baseline content exclusions — sensitive content categories, digital content labels, and so on. These are not optional cleanup steps. Programmatic inventory includes a long tail of placements that automated filters alone won't fully cover for every brand's specific standards. Setting these once, correctly, at the right layer is cheaper than auditing placement reports after the fact.

Viewability threshold. DV360 lets you set a minimum Active View viewability threshold. Set it too high and you exclude a large share of available inventory. Set it too low and you pay for impressions that were never seen. The right level depends on your campaign goal — awareness campaigns benefit from higher thresholds; reach-focused campaigns may need to accept lower thresholds to hit scale.

Why DV360 Has Access Other DSPs Don't

One of the clearest explanations of DV360's structural advantages appears in Lesson 4 of the tutorial series. The short version: DV360 is Google's own DSP, which means it has native, direct access to Google's full inventory stack.

That includes:

• Google Display Network
• YouTube (including non-skippable, bumper, and connected TV)
• Google Ad Manager publisher inventory
• Audio inventory via Google Audio Ads
• Connected TV and streaming inventory

Third-party DSPs can access some of this through open auction, but not all of it — and not at the same priority. YouTube non-skippable inventory, for instance, is not available programmatically outside of DV360 and Google Ads. If YouTube is central to your media plan, DV360 isn't optional.

The second structural advantage is audience data. DV360 integrates directly with Google Analytics 4, Google Ads audiences, and first-party CRM data uploaded through Customer Match. Combined with Floodlight conversion data, this means your bidding algorithms have more signal than they would on an independent DSP pulling the same audience segments through a third-party data marketplace.

This doesn't make DV360 automatically better for every use case. It makes it specifically better for advertisers whose media plans are heavily weighted toward Google-owned and Google-monetized inventory, and who have clean first-party data to feed the system.

Account Hierarchy in Practice — Where Things Break

Lesson 5 on account hierarchy covers the structure well, but the places where real accounts actually break tend to be more specific:

Budget Doesn't Respect Line Item Priorities Without IO Configuration

A common failure mode: an advertiser sets a campaign budget, creates an IO with no budget cap (inheriting from the campaign), then creates multiple line items with individual budgets that sum to more than the campaign total. DV360 doesn't error on this at setup. It runs until it hits the campaign cap, then stops everything — including high-performing line items — because budget was exhausted by less efficient ones.

The fix is IO-level budget allocation with line-item prioritization configured explicitly. This is not a default — you have to set it.

User Permissions Are Inherited But Scoped

Partner-level users can see everything. Advertiser-level users can see only their advertiser. This matters when you're onboarding a client into your Partner account — give them advertiser-level access, not partner-level, or they can see every other advertiser in your account. This is a basic point that costs real relationships when it goes wrong.

Floodlight Configuration Errors Are Silent

If a Floodlight tag is misconfigured — wrong advertiser ID in the tag, tag firing on the wrong page, conversion window set incorrectly — DV360 doesn't alert you. Campaigns run. Conversions don't track. Bidding algorithms optimize toward nothing. The only way to catch this is proactive verification: check the Floodlight activity report within the first 48 hours of any new campaign.

Reading DV360 Reports Without Fooling Yourself

DV360 reporting has two main modes: the Report Builder (also called Offline Reporting) and Instant Reporting. Understanding when to use which one matters.

Instant Reporting is fast — data updates hourly and you can pivot it quickly in the UI. Use it for same-day pacing checks, creative rotation monitoring, and quick sanity checks on delivery. Do not use it for performance conclusions. The attribution models in Instant Reporting default to last-click in many views, and the data isn't fully de-duplicated across channels.

Report Builder queries are slower — reports can take minutes to hours to generate — but they support cross-channel attribution, more granular dimensions (down to individual placement and creative size), and proper de-duplication. Use this for weekly analysis, creative performance reviews, and anything that informs budget decisions.

Key dimensions worth adding to every standard report:

• Exchange — tells you where impressions are actually serving across the Google inventory ecosystem
• App/URL — essential for identifying low-quality placements that should be excluded
• Line item type — if you're running multiple formats, this keeps them separated cleanly
• Creative size — shows which formats are actually serving vs. which you uploaded but aren't winning auctions

The Optimization Levers Most People Set Once and Forget

Bidding strategy in DV360 operates at the line item level. The options range from fixed CPM to automated strategies like Target CPA and Maximize Conversions. The automated strategies require Floodlight conversion data to work — without signal, they don't optimize toward anything meaningful.

Frequency management, as noted above, needs to be set at the IO level to be effective across multiple line items. But frequency alone doesn't tell you much without looking at frequency-to-conversion rate curves in your report data. Most accounts show diminishing returns on conversion rate past a certain frequency threshold — the exact point varies by audience and creative, but it's almost always visible in the data within the first few weeks of a campaign running.

Creative rotation defaults to "optimize" in DV360, which means the algorithm weights toward the creative that wins auctions most efficiently — not necessarily the one that converts best downstream. If you have Floodlight data, switch rotation to conversion-optimized. If you don't, run equal rotation and pull the data yourself.

FAQ

What is the DV360 account hierarchy? DV360 organizes accounts across five layers: Partner, Advertiser, Campaign, Insertion Order, and Line Item. Each layer controls different things — billing and access at Partner, conversion tracking and audiences at Advertiser, budget and dates at Campaign, pacing at Insertion Order, and targeting plus bidding at Line Item. Misconfiguring any layer affects everything below it.

What are the advantages of DV360 over other ad platforms? DV360's primary structural advantage is direct access to Google-owned inventory, including YouTube non-skippable formats and connected TV inventory that isn't available to third-party DSPs through open auction. It also integrates natively with GA4, Google Ads audiences, and Floodlight conversion tracking, giving bidding algorithms stronger signal than most independent DSPs can access.

What are common DV360 campaign settings mistakes? The most expensive ones are: setting frequency caps only at line item level (leaving cross-line-item frequency uncapped), leaving viewability thresholds at defaults without checking inventory impact, and skipping brand safety content exclusions on the assumption that automated filtering is sufficient. These are all set in what DV360 calls "additional campaign settings" and are easy to miss on initial setup.

How does DV360 reporting work? DV360 has two reporting modes. Instant Reporting updates hourly and is useful for same-day pacing checks but defaults to attribution models that can overstate performance. Report Builder generates deeper queries with proper de-duplication and cross-channel attribution support. For any decision that involves budget or creative strategy, use Report Builder, not Instant Reporting.

What is a Floodlight tag in DV360? A Floodlight tag is DV360's conversion tracking mechanism. It's configured at the Advertiser level and fires on conversion pages on your site. Without a correctly configured Floodlight tag, automated bidding strategies have no signal to optimize toward, and your conversion reporting will be empty or wrong. Verify Floodlight firing within 48 hours of any new campaign launch.

How does budget work across the DV360 hierarchy? Campaign budget sets the outer limit for a flight. Insertion Order budget allocates within that limit across line items. Line item budgets operate within the IO allocation. If line item budgets sum to more than the IO budget, the IO cap wins — the excess line item budgets are theoretical. Set IO budgets explicitly and verify the math before launch.

What's the difference between DV360 and Google Ads for display? Google Ads display targets primarily Google Display Network inventory. DV360 adds access to Google Ad Manager publisher inventory, YouTube connected TV formats, audio, and a broader programmatic exchange ecosystem — all through a single DSP interface. DV360 also offers more granular targeting controls, creative formats, and reporting dimensions. The tradeoff is significantly higher setup complexity and, typically, higher minimum spend expectations.

If you're auditing a DV360 account that someone else set up, start at the IO level before you look at line items. That's where the structural errors that affect everything downstream are most often hiding — and they're almost always invisible from the campaign view alone.