DV360 User Management — Partner & Advertiser Roles, | OpsBlu Docs

DV360 User Management — Partner & Advertiser Roles,

Complete guide to Display & Video 360 permission model including partner-level vs advertiser-level roles, Floodlight ownership, API access, and reporting.

DV360 Permission Model

Display & Video 360 uses a two-tier permission structure: partner level and advertiser level. A partner is the top-level entity (typically your agency or organization), and advertisers sit underneath it. Where you assign a user determines what they can see and do.

  • Partner-level users inherit access to every advertiser under that partner. Use this for internal platform leads and senior traders who need cross-advertiser visibility.
  • Advertiser-level users see only the specific advertiser(s) they are assigned to. Use this for client-specific team members, external agency contacts, or anyone who should not see other advertisers' data.

This distinction matters because partner-level Admin access includes Floodlight configuration, billing, and cross-advertiser audience management -- permissions that are difficult to scope down after granting.

Available Roles

DV360 offers four roles at both the partner and advertiser level:

Role Campaign Access Audience / Floodlight Billing & Invoices User Management
Admin Full create/edit/delete Full Floodlight config, audience creation and sharing View and manage invoices Add, edit, remove users
Standard Full create/edit/delete Use existing audiences, cannot modify Floodlight No access No access
Read-only View campaigns, line items, IOs View audiences and Floodlight tags No access No access
Billing No campaign access No access View and download invoices No access

Additional role behaviors to note:

  • Admin at partner level can create new advertisers, manage Floodlight globally, configure first-party audiences across advertisers, and control data partner integrations.
  • Standard at advertiser level is the typical role for agency traders. They can build campaigns and optimize bids but cannot touch Floodlight tags or add users.
  • Read-only users cannot export raw data through the UI but can access scheduled reports if an Admin shares them.
  • Billing is a standalone role -- it cannot be combined with other roles on the same user record.

Admin UI Path for User Management

Partner-level user management:

DV360 sidebar
  > Settings (gear icon, bottom left)
    > Partner settings
      > Users tab
        > + New user

Advertiser-level user management:

DV360 sidebar
  > Advertiser dropdown (top left, select specific advertiser)
    > Settings (gear icon)
      > Advertiser settings
        > Users tab
          > + New user

Checking a user's current access:

Partner settings > Users tab
  > Search by email
    > Shows role and advertiser scope

When removing a user, check both partner-level and advertiser-level user lists. A user removed from partner settings may still have direct advertiser-level assignments.

API Access Management

DV360 API access is managed through Google Cloud Platform (GCP) service accounts and OAuth 2.0 credentials, separate from the DV360 UI roles.

  • DV360 API (v3) -- uses GCP service accounts. The service account email must be added as a user in DV360 partner or advertiser settings with an appropriate role (typically Admin for full API access, Standard for campaign management only).
  • SDF (Structured Data Files) -- bulk campaign management via download/upload. Requires Standard or Admin role. SDF operations run under the user's permission scope.
  • Bid Manager API -- legacy API name, same as DV360 API. If you see references to "DBM API," it is the same system.
  • Reporting API -- generates DV360 reports programmatically. The service account needs at least Read-only access to the partner or advertiser whose data it queries.

To audit API access: review GCP IAM for service accounts with DV360 API enabled, then cross-reference those service account emails against DV360 partner/advertiser user lists.

Analytics and Reporting Permissions

DV360 reporting permissions are tightly coupled to role and scope:

  • Cross-advertiser reporting -- only available to partner-level users. Advertiser-level users see data for their assigned advertiser(s) only.
  • Floodlight reporting -- conversion data visibility follows Floodlight access. Admin users see all Floodlight activities; Standard and Read-only users see only activities associated with their advertiser scope.
  • Custom report scheduling -- Admin and Standard users can create and schedule reports. Read-only users can view shared reports but cannot create their own.
  • Data Transfer files -- log-level data exports require separate Google Cloud setup and Admin-level partner access. This is a distinct permission from UI reporting.
  • Campaign Manager 360 integration -- if CM360 and DV360 share a Floodlight configuration, user access in DV360 does not automatically grant CM360 access. Manage these separately.
  • Google Analytics linking -- linking DV360 to GA4 requires Admin access in DV360 and Edit permission on the GA4 property. Standard users cannot create or modify links.

Partner vs. Advertiser Scoping Decision

Use this to decide where to place a user:

  • Partner level -- platform administrators, agency leadership, billing contacts, anyone who needs to see or compare data across all advertisers.
  • Advertiser level -- campaign traders working on a single client, external client contacts who should only see their own data, temporary contractors, audit or compliance reviewers.

Moving a user from partner level to advertiser level requires removing them from partner settings and re-adding them at the advertiser level. There is no "downgrade scope" button.

Step-by-Step Guides

Back to top