Display & Video 360 Integration

Display & Video 360 is programmatic at Google scale. Every major exchange, premium inventory across display, video, audio, and CTV, the targeting depth of the Google stack, and the data infrastructure to back it. The complexity is the trade-off: insertion orders sitting above line items sitting above creative variants, multiple exchanges contributing to the same campaign, and reporting that's genuinely powerful but rarely fast enough to drive same-day decisions.

The Routy integration with DV360 pulls performance data into Routy on a continuous schedule so programmatic ends up in the same view as your search, social, and direct media spend. The cross-channel comparison stops being a quarterly spreadsheet exercise and starts being something you can look at on any given Tuesday afternoon.

After connecting, the following becomes available in your Routy reports:

• Spend at the insertion order, line item, and creative level, so the full DV360 hierarchy is measurable in the same place as the rest of your media
• Impressions, clicks, video completions, viewability metrics, and the engagement signals DV360 exposes
• Conversion attribution that ties every conversion Routy tracks back to the DV360 insertion order, line item, and creative behind the click or view
• Side-by-side reporting with your other media, so you can actually answer the question of what programmatic is producing relative to everything else you're running

Note that DV360, unlike most paid social and search platforms, does not have a public conversions API endpoint in the way Meta or Google Ads do. The integration is one-direction: data flows from DV360 into Routy, attribution happens in Routy, but the platform itself doesn't accept conversion uploads from third-party tools in the same standardised way. Floodlight tags and Campaign Manager handle that side of the picture in the Google stack.

You connect your DV360 account through Google's standard OAuth flow. The integration then pulls performance data from the DV360 Reporting API on a regular schedule and reconciles it with the conversions you're already tracking in Routy.

A few things worth knowing before you connect:

• DV360 requires an active seat to access. If your operation runs programmatic through an agency or trading desk, the seat is usually on their side, which means the connection needs to be authorised through their account or with their permission.
• DV360's Reporting API returns data at different schedules depending on the report type. Some metrics update within an hour; others (particularly aggregated viewability and brand-safety reports) update on a longer cadence. The integration surfaces whatever the API returns at whatever its current latency is.
• Floodlight conversion data and DV360 spend data can be combined inside the Google stack already, through Campaign Manager 360. If your operation is set up that way, the Routy integration is additive — it brings DV360 data into the same view as your non-Google channels, which Campaign Manager can't do.

Programmatic has a credibility problem in most affiliate operations, and it's not because it doesn't work. It's because the reporting lives in a different stack, the attribution conventions are different, and the conversation with anyone outside the programmatic team starts with twenty minutes of caveat before anyone can compare numbers. When the budget conversation rolls around and someone asks whether to keep DV360 running, the people defending the line item usually have to spend more time explaining the numbers than they spend on the numbers themselves.

Connecting Routy puts DV360 data on the same reporting surface as the rest of your media. The cross-channel comparison stops requiring context, the conversion attribution follows the same rules as everything else, and the case for programmatic (or against it) can be made on the same terms as the case for any other channel. For most operations running DV360 alongside search, social, and native, this is the missing piece that makes the cross-channel media planning conversation actually work.