Dossier Kobi Digital Ads · Board pack · v1.9.13 Board pack · v1.9.13

Platforms · Draft

DV360 (Display & Video 360)

Created 9 Jun 2026·Updated 11 Jun 2026

Latest change: Publish Dossier site and full doc pack to GitHub

Draft document — deep-dive spec incomplete; content will be updated before and during build. Do not treat as signed-off implementation detail. Pack overview

Priority: 4

Overview

DV360 handles programmatic display, video, and advanced audience buys — especially relevant for tourism, brand awareness, and retargeting at scale. Access is managed through Google Marketing Platform organization structure under agency control.

Account model

Element Approach
Partner / advertiser Kobi partner ID → advertiser ID per tenant
Client visibility None on DV360 UI; reporting via Kobi dashboard
Billing Kobi/agency billing profile; client invoiced monthly by Kobi
Naming kobi_{tenant_slug}_dv360

Access & API

  • Display & Video 360 API (Bid Manager API)
  • Service account / OAuth via Google Marketing Platform
  • IAM: separate from Google Ads API credentials

Readiness: GMP / DV360 sales contract required before API is usable — not self-serve. See Platform access & API readiness.

Onboarding checklist

  1. Create advertiser under Kobi partner
  2. Link CM360 / creative assets if using Campaign Manager (optional phase)
  3. Configure floodlight activities OR align with GA4 → Ads data path for attribution
  4. Audience lists: first-party uploads, Google audiences
  5. Brand safety / inventory source lists per vertical policy
  6. IO (insertion order) structure template per plan type

Conversion tracking

Method Use case
Floodlight (legacy GMP) If CM360 in stack
GA4 linkage Preferred modern path — GA4 as SoT
Offline imports CRM conversions via Google Ads offline path where shared

Note: DV360 attribution is complex; GA4 remains source of truth for cross-channel KPIs; DV360 metrics used for programmatic diagnostics.

Data to GA4

  • UTM on all click-through URLs
  • GA4 cross-domain if booking engines involved
  • Cost data may require manual or API export into warehouse (plan for BigQuery transfer)

Agent capabilities

  • IO / line item creation from approved plan templates
  • Budget flight dates and pacing
  • Audience and inventory application (within allowlists)
  • Pause / shift budget on optimization signals

Human touchpoints

  • Large budget IO approval
  • Inventory deals (PG/PMP) requiring sales contracts
  • Creative trafficking to CM360 (if used)
  • Brand safety exceptions

Dependencies

  • GA4 established
  • Google Ads MCC relationship (shared Google ecosystem credentials)
  • Often later phase due to complexity — see roadmap