Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Programmatic Advertising › Display & Video 360

DV360 Account Structure

How DV360 is structured: partner, advertiser, campaign, insertion order and line item, what each level controls, inherited settings, naming and reportability.
Guideintermediate10 min readUpdated

The five levels and what each decides

LevelUsually representsWhat is decided hereApplied to the levels below
PartnerAgency, trading desk or holding companyWhich exchanges are enabled, users and roles, billing profiles, partner-level costs, default settings for new advertisersExchange availability, user access, partner costs added to insertion orders
AdvertiserA brand or clientCurrency, time zone, the Campaign Manager 360 link and Floodlight configuration, creative library, audiences, default brand-safety settingsConversion data, creatives and audiences available to every line item under it
CampaignOne objective over one periodGoal, KPI, planned spend and dates, campaign-level frequency cap, optional targetingFrequency cap and any targeting applied to insertion orders and line items created afterwards
Insertion orderOne budget line of the planBudget and budget segments, flight dates, pacing, performance goal, frequency cap, optimisation, partner costsBudget ceiling, dates, pacing rules and targeting applied to new line items
Line itemOne tacticLine item type, targeting, bid strategy, budget share, pacing, frequency cap, creatives, conversion countingNothing below it except ad groups on YouTube line items

The table is the whole model, and two patterns in it matter more than any single row. First, the further down the tree a setting sits, the more often it changes: partner settings are set once a year, line item settings every week. Second, settings at the campaign and insertion order level are applied to things created afterwards, which is why the Help Centre is careful to say that changing targeting on an insertion order does not rewrite its existing line items. A demand-side platform (DSP) is still, in the end, a list of line items bidding independently, and the levels above them exist to organise that list.

Partner and advertiser settings

The partner is created by Google or a reseller when the contract is signed. Day to day it is where users are added and given roles, where the exchanges and sub-exchanges the partner may buy from are switched on, and where billing profiles and partner-level costs (the fees an agency adds for its own services or for third-party tools) are defined so they can be applied to insertion orders. Some partners also keep shared channels, shared inventory sources and shared audiences at this level so every advertiser can use them. The documented list of partner-only settings is on the Help Centre's partner settings page and changes occasionally.

The advertiser is the level that most teams underestimate. Its currency and time zone govern every report and every budget below it, and the help pages describe which of these cannot be changed after creation, so they deserve a careful decision rather than a default. The link to a Campaign Manager 360 advertiser brings across the Floodlight configuration, which is what turns site activity into conversions, audiences and automated bidding signals. Creatives are uploaded and reviewed at advertiser level and then assigned to line items; first-party audiences are built here too. Brand-safety defaults, including the digital content labels and sensitive categories a new line item starts with, can be set once at the advertiser so that nobody has to remember them on every line item. The tutorial on setting up a new advertiser in DV360 and CM360 makes these advertiser-level decisions in order, with the ad server and Floodlight settled first, before the first line item exists.

Campaigns and insertion orders: goals, budgets, dates

A campaign in DV360 is lighter than the word suggests. It carries a goal chosen from a documented list, a KPI with a target value, planned spend and planned dates, and an optional frequency cap. None of these bid. They exist so that the people running the account and the reports they pull can see what the plan intended, and so that pacing views can compare delivery against the planned figure. Treat the campaign as a folder with a label: one objective, one period, one planning owner.

The insertion order is where money becomes real. It holds the budget, which can be split into segments that each have their own amount and date range so that a plan with monthly allocations does not need a new insertion order each month. It holds the flight dates, the pacing mode (daily or flight) and the pacing rate (as soon as possible, even, or ahead), and a performance goal expressed in the unit the plan was sold on. It can also hold a frequency cap, insertion-order-level optimisation that moves budget between its line items, and the partner costs that are added on top of media. The bidding and pacing guide covers how these pacing and optimisation settings behave once live; the structural point is that every insertion order should be a line on the media plan that somebody has agreed to spend, because the insertion order is what the pacing report and the client invoice are reconciled against.

Dates deserve a note. Line items can inherit the insertion order's dates or carry their own narrower ones, and an insertion order whose segments end before its line items do stops spending without warning. The common convention is to set dates on the insertion order and let line items inherit unless a tactic genuinely runs for a shorter window.

Line items: where targeting and bidding live

The line item is the unit that bids. It has a type (display, video, audio, or YouTube and partners), and the type decides which inventory, creatives and bid strategies are available to it. It has flight dates and a budget, which may be a share of the insertion order or unlimited within it. It has a pacing setting, a bid strategy, a frequency cap, a list of assigned creatives, and the conversion activities it counts towards automated bidding and reports. And it has targeting: audiences, geography, language, demographics, devices, environments, viewability, brand safety, inventory sources and deals, keywords, categories, channels of URLs and apps, day and time, position on page, and authorised-seller status.

Because all of this sits on one object, the structural question is how many line items to create. The answer is one per combination that needs its own budget, its own bid or its own report line. A prospecting audience and a remarketing audience need separate line items because they need separate bids and caps. A deal with one publisher and the open exchange need separate line items because deal delivery has to be monitored on its own. Two creative sizes do not need separate line items, because rotation handles that inside one. Over-splitting is the commoner error: a plan with dozens of thin line items spreads budget so thinly that automated strategies have nothing to learn from and pacing reports become noise. Several objects built around the same audience with no cap above them also multiply the exposure each person receives, which the troubleshooting page for a frequency cap that is not working traces back to the structure.

Line items can be duplicated within and across insertion orders, and bulk changes are made with Structured Data Files, the spreadsheet import and export format the Help Centre documents for every level of the hierarchy. Teams that run many advertisers usually keep a template insertion order with its standard line items and copy it rather than building from blank. Before anything is created, a programmatic campaign build sheet records each insertion order and line item with the reason it is separate from its neighbours.

Naming and reportability

Every level of the hierarchy is a dimension in DV360 reports, with both a name and an ID. IDs never change; names can be edited at any time. That makes the name the right place to encode the plan, and the ID the right join key for anything outside DV360, such as the finance spreadsheet or a Campaign Manager 360 placement. Reports filter and group by these names, so a convention that puts the same fields in the same order on every object lets a report be sorted into the plan's shape with no manual mapping.

A workable convention names the campaign for the objective and period, the insertion order for the channel and budget line, and the line item for the tactic: inventory approach, audience, format and any variant being tested. Separators should be consistent, and abbreviations should be written down somewhere outside the platform. The Google Ads naming conventions guide sets out the same discipline for Google Ads, and the fields carry over almost unchanged. What does not carry over is the Google Ads habit of encoding targeting in the campaign name; in DV360, targeting is a line item property and belongs in the line item name.

The DV360 reporting guide explains which report types expose which levels. The short version is that any structure can be reported on, but only a structure that matches the plan can be reported on without a lookup table. Before a flight starts, the DV360 campaign launch checklist checks budgets, dates and names against the signed plan.

Structures for common plans

PlanCampaignsInsertion ordersLine items
Always-on prospecting and remarketing, one marketOne per quarter or one evergreenOne for prospecting, one for remarketingPer audience and inventory approach
Launch with publisher dealsOne per launchOne for deals, one for open exchangeOne per deal; open exchange split by audience
Multi-market brandOne per market or one per objective, depending on who reportsOne per market per channelPer audience and format within each market
Video plus display reach planOneOne per channel so pacing is visible per channelPer inventory approach and device environment
Agency with several clientsOne advertiser per client; campaigns per client objectiveMirror each client's plan linesPer tactic, with templates copied between clients

The pattern across all of these is that insertion orders mirror budget lines and line items mirror tactics, and campaigns are whatever grouping the person reading the report needs. If two people need two groupings, pick the one that matches how budget is approved, because that is the grouping that the pacing view and the invoice will follow. The Google Ads account structure guide argues the same from the other platform's side, and the two accounts are easier to reconcile when their structures rhyme.

Illustrative example — not a real result

Restructuring a travel advertiser's DV360 account

A travel operator inherits a DV360 advertiser with one campaign, one insertion order of £180,000 and thirty-one line items, several of them paused duplicates. Reports cannot say what prospecting spent against remarketing, and the client's finance team receives a monthly spreadsheet rebuilt by hand. The agency creates three insertion orders under a new campaign: prospecting at £110,000 across the twelve-week season, remarketing at £45,000, and a £25,000 insertion order for two programmatic guaranteed deals with ski publishers. Prospecting keeps six line items split by audience and inventory approach; remarketing keeps three; each deal gets one. Names follow one pattern, such as "PRO-OpenEx-InMarketSki-Display-UK". The next month's report is a pivot on insertion order and line item name with no manual mapping, and the pacing view shows that remarketing is running at 70 per cent of plan while prospecting is on target, which the old structure had hidden.

How this buying platform divides the work with the advertiser's ad server is covered in the comparison of CM360 and DV360, including why the two are usually linked.

Common mistakes

  • Treating the campaign as the budget holder. The campaign's planned spend is a reference; the insertion order's budget is the ceiling. Reports that compare the two are checking plan against delivery, not controlling anything.
  • One insertion order for everything. Pacing, invoicing and reporting all happen per insertion order, so a single one hides which part of the plan is behind.
  • Encoding targeting in campaign names. Targeting lives on the line item; the name should too.
  • Changing an insertion order and assuming its line items changed. Settings applied downward reach only what is created afterwards.
  • Fixing currency and time zone without checking. The Help Centre lists what cannot be changed after the advertiser is created; those decisions are cheap on day one and expensive later.
  • Splitting line items by creative size. Rotation inside a line item does that job; extra line items only dilute budget and learning.
  • Leaving paused duplicates in place. They clutter every report and every Structured Data File export, and somebody eventually unpauses one.

The DV360 hub introduces the other guides; the structure described here is the frame each of them assumes.

Frequently asked questions

Can one insertion order hold line items of different types?

Yes. Display, video and audio line items can sit under the same insertion order and share its budget, dates and pacing. Most teams still separate channels into their own insertion orders, because the insertion order is the budget line that reports and pacing are judged against, and a mixed one hides which channel is spending.

Does the campaign goal or KPI change how DV360 bids?

No. The campaign goal and KPI are plan references that appear in reports and help people reading the account; bidding is decided by the strategy on each line item and, where enabled, the optimisation settings on the insertion order. Set them honestly so the reports stay meaningful, but do not expect them to act.

How many advertisers should a brand have in DV360?

One per combination of currency, time zone and Floodlight configuration, because those are fixed at the advertiser level. A brand selling in several markets with separate conversion tracking usually needs one advertiser per market, while a brand with one currency and one Floodlight configuration is better served by one advertiser and separate campaigns.

Terms used on this page

Where this page is used

Part of these learning paths

Also related

Sources

  1. Display & Video 360 Help — Google

Related