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

Comparisons

CM360 vs DV360

Campaign Manager 360 and Display & Video 360 compared: ad serving and verification against programmatic buying, how they share data, and which teams use each.
Comparisonintermediate7 min readUpdated

Campaign Manager 360 and Display & Video 360 at a glance

CM360 sits at the end of the chain. When a publisher's ad server or a demand-side platform decides that an impression belongs to the advertiser, it returns the advertiser's CM360 tag; the browser calls CM360, which chooses an ad and creative by the advertiser's rules, serves it and counts the impression when the creative begins to render. Clicks pass through CM360's redirect, and Floodlight tags on the advertiser's site record conversions against the same record. The ad serving basics guide covers tags, counting and rotation, and the trafficking tutorial covers building the objects.

DV360 sits at the start of the chain. It receives bid requests from exchanges and supply-side platforms, applies the targeting, frequency, brand safety and pacing rules set on its line items, and bids. Its hierarchy of partner, advertiser, campaign, insertion order and line item is where budgets, goals and targeting live. The DV360 account structure guide explains what each level decides.

The two are separate on purpose. The site's programmatic ecosystem guide notes that the buy side has kept the ad server and the buying platform as distinct products, even inside Google's stack, because a buyer that wants a count it can defend keeps a system that does not also make the buying decision.

Compare table

Campaign Manager 360 vs Display & Video 360

Row labelCampaign Manager 360Display & Video 360
Primary jobServe, count and verify ads, and record conversionsBuy impressions programmatically
Who uses itAdvertiser and agency ad operations teams, traffickers and analystsProgrammatic traders in agencies, trading desks and in-house teams
What it buysNothing; media is bought elsewhereOpen auction inventory, private auctions, preferred deals and guaranteed deals
What it servesCreatives into any buy that can carry its tags, direct or programmaticCreatives on the impressions it wins, from its own library or as an ad server tag
Measurement roleAd server of record across every buy, with Floodlight conversionsDelivery and performance reporting for its own buys
Creative handlingHosts creatives once and serves them everywhereCreatives reviewed and assigned to line items at advertiser level
Data sharingFloodlight configuration and audiences shared with linked productsLinked CM360 advertiser brings Floodlight conversions and audiences into bidding
Cost modelA serving fee per thousand impressions, at the contract rateA platform fee on media, plus any data and partner costs
Best-fit advertiserSeveral buying routes, or a need for one independent countEnough programmatic spend to justify a self-serve buying platform

The two rows that separate them are what each buys and what each counts. CM360 buys nothing and counts everything that carries its tag; DV360 buys and counts its own purchases. The rest of the table follows from that division of labour.

When to choose Campaign Manager 360

Choose CM360 when there is more than one buying route to reconcile. A plan that mixes direct insertion orders with publishers, programmatic deals, open auction buying and perhaps search clicks needs one count under one method, one invalid traffic treatment and one reporting time zone. CM360 provides that, and it lets the advertiser manage frequency across routes because it sees the same browser whichever route served the impression.

Choose it when the conversion record matters across channels. Floodlight attributes a conversion across all the buys that carried CM360's tags rather than letting each platform claim it, and a linked DV360 advertiser can use the same Floodlight activities for bidding. The ad serving guide explains why an advertiser that keeps conversion tracking in the ad server can change buying platform without losing its history.

Choose it for creative control and verification. A creative trafficked once serves wherever its tag is used, so a change takes effect everywhere. Active View measures Viewability on the impressions CM360 counted, and the site's guide records that content and geography verification are available without a separate vendor, which is often enough unless a contract requires an independent count.

When to choose Display & Video 360

Choose DV360 when the plan includes programmatic buying at a scale that justifies a self-serve demand-side platform. It gives the buyer direct control over targeting, bids, frequency, pacing and inventory sources across exchanges, and it carries negotiated deals with publishers through the same pipes. The trade is that someone has to operate it: line items, insertion orders and deal setup are daily work for a trained team.

Choose it when programmatic is the main buying route and the advertiser wants that buying in its own or its agency's hands, rather than inside a managed service. Its structure lets the plan's budget lines become insertion orders that pacing reports and invoices can be reconciled against.

DV360 can serve creatives itself, so an advertiser whose only route is DV360 can run without a separate ad server. That is a legitimate setup for a single-route plan; the cost is that its counts are the buying platform's own, and conversions recorded there cannot be shared with buys made elsewhere. The programmatic versus direct buying comparison helps decide whether the plan will stay with one route.

Decision table

SituationChooseWhy
Direct publisher buys plus programmaticCM360, with DV360 for the programmatic partOne count across routes, one buying tool for auctions and deals
Programmatic through one DSP only, no direct buysDV360, with CM360 optionalDV360 can serve and count its own buys
Conversion tracking must be shared across display, video and searchCM360 with Floodlight, linked to DV360One conversion record used by every buy
Contract requires an independent delivery countCM360, plus a verification vendor if specifiedThe count does not come from the platform being judged
Advertiser buys only through Google Ads and social platformsNeitherThose platforms serve, count and report their own ads
Agency running programmatic for several clientsDV360 at partner level, CM360 per client where routes multiplyBuying and counting are scaled differently
Creative changes must take effect everywhere at onceCM360Creatives hosted once and served into every buy

How the two work together

In the usual arrangement, the advertiser's DV360 account is linked to its CM360 advertiser. The link brings the Floodlight configuration across, so DV360 line items can count and bid towards the same conversion activities CM360 records. Creatives are trafficked in CM360 and their tags used in DV360, so the ad server counts DV360's impressions alongside every direct placement. The academy exercise on moving display buying into DV360 for a hiking boot maker practises setting up the ad server first and linking the buying platform to it.

The counts will disagree. DV360 records auctions won; CM360 records creatives that began to render. The gap between them is normal and should be stable. Report delivery from the ad server, reconcile the difference each month, and investigate when it widens. Naming conventions that join DV360 insertion orders to CM360 placements make that reconciliation possible, and the DV360 structure guide treats naming as part of the build rather than an afterthought.

Costs stack. CM360 charges a serving fee per thousand impressions; DV360 charges a platform fee on media; data segments and verification add their own fees. The CPC versus CPM comparison explains the pricing unit most of these fees use, which is why a plan's real cost per thousand includes more than the media price.

Illustrative example — not a real result

A holiday company decides what it needs

Hartmoor Holidays spends £40,000 a month on display and video: £25,000 through DV360 and £15,000 in direct deals with two travel publishers. Each publisher reports its own impressions, DV360 reports its own, and the three conversion counts add up to 1,450 bookings in a month when the booking system shows 980. Hartmoor traffics all creatives through CM360, places Floodlight on the booking confirmation and links DV360 to the same advertiser. The next month CM360 attributes 720 bookings across all three routes, with no booking claimed twice. At a serving fee of £0.15 per thousand on about 9 million impressions, the ad server costs about £1,350 a month, which Hartmoor judges worth paying for a count it can reconcile with its sales.

Common mistakes

  • Treating CM360 as a buying platform, then wondering why trafficking it produces no delivery without a buy behind the tag.
  • Reporting delivery from DV360 when CM360 is in place, so direct and programmatic buys are counted under different rules.
  • Running two DSPs or direct buys without one ad server, which splits frequency, counting and conversions across systems that cannot see each other.
  • Leaving DV360 unlinked from the CM360 advertiser, so bidding cannot use the Floodlight conversions the business reports on.
  • Expecting the counts to match exactly, when the two systems count at different moments.
  • Buying a self-serve DSP for a small plan, when a managed buy or the platforms the advertiser already uses would do.
  • Ignoring stacked fees, so the plan's effective cost per thousand is higher than the media price suggests.

Frequently asked questions

Do I need CM360 if all my buying goes through DV360?

Not strictly. DV360 can host and serve creatives itself and reports its own impressions and clicks, so a plan with one buying route can run without a separate ad server. CM360 earns its place when there is more than one route to reconcile, such as direct publisher deals alongside programmatic, when Floodlight conversions need to be shared across display, video and search, or when creative hosting should sit apart from the buying tool so that a change of platform does not mean rebuilding every asset.

Can CM360 buy media?

No. CM360 serves and counts ads that have been bought elsewhere: through a publisher's insertion order, a demand-side platform such as DV360, or another buying route that can carry its tags. It decides which creative to show when its tag is called, but the decision to buy the impression, and the price, belong to the buying platform or the direct contract.

Why do CM360 and DV360 report different impression counts for the same campaign?

They count at different points. A demand-side platform records the auctions it won; CM360 counts an impression when the creative begins to render in the browser, which is later. People who leave the page, slow loads and blocked scripts all sit in the gap. A small, stable difference is normal and expected. A gap that widens suddenly is worth investigating, and most advertisers report delivery from the ad server's count because it applies one method to every buy.

Terms used on this page

Where this page is used

Also related

Sources

  1. Campaign Manager 360 Help — Google
  2. Display & Video 360 Help — Google

Related