POST /v3/adgroup → adGroupCreate

Overview

Multi-step operations

Input field mapping

Input type: AdGroupCreateInput

GraphQL-only input fields (no REST equivalent)

Output field mapping

Output type: AdGroup (returned as data on PayloadWithErrorsOfAdGroup)

Endpoint-specific nested types and enums

AdGroupCreateROIGoalInput (create and update ROI goal)

NielsenSettingsCreateInput (create)

NielsenSettingsUpdateInput (update)

ComscoreSettingsInput (create and update)

AdGroupCreateKoaOptimizationSettingsInput (create)

AdGroupNewFrequencyConfigInput (create)

AdGroupMiaozhenSettingsInput (create and update)

REST nests these under MiaozhenSettings.MiaozhenTrackingAttributes. GraphQL flattens them onto miaozhenSettings. China-signed partners with an advertiser corporation ID only. On update, pass null to disable Miaozhen tracking.

AdGroupUpdateKoaOptimizationSettingsInput (update)

AdGroupUpdateAudienceInput (update audience)

IMPORTANT: The audience input on adGroupUpdate is in open beta, enabled by default. Clients who opted out must wait for general availability or contact their Technical Account Manager for access.

RTBAttributes → direct children (create input)

HighFillAttributes (create input)

RTBAttributes → response fields (create/update response)

AdGroup flattens RTB data to top-level fields and connections—there is no rTBAttributes parent on the response. See nested tables below for leaf mappings.

AdGroupCategory → industryCategory

RTBAttributes → Budget & pacing

RTBAttributes → Bids

RTBAttributes → Audience targeting

RTBAttributes → ROI goal

REST exposes a discriminated ROIGoal object with many optional metric fields. GraphQL models goals uniformly:

RTBAttributes → Frequency

RTBAttributes → Creatives

RTBAttributes → Dimension bid adjustments

REST inlines dimension adjustments (geo, browser, device, video, language, etc.) under RTBAttributes. GraphQL models these through bid lists and bid factors instead of a flat adjustment object on AdGroup.

RTBAttributes → Auto-optimization & KOA

RTBAttributes → Contract / private marketplace targeting

RTBAttributes → Viewability

RTBAttributes → Site quality providers (Integral / DoubleVerify / Peer39)

REST returns large provider-specific fee and rating trees inline. GraphQL does not mirror those trees on AdGroup; brand-safety, contextual, and viewability provider settings are bid-list and dimension backed.

RTBAttributes → Nielsen / Comscore / Miaozhen

AssociatedBidLists

HighFillAttributes (REST-only envelope)

Code examples

Example—create ad group (GraphQL subset)

REST example

POST /v3/adgroup HTTP/1.1
Content-Type: application/json
TTD-Auth: AUTH_TOKEN_PLACEHOLDER

{
  "CampaignId": "cmp123",
  "AdGroupName": "My RTB Ad Group",
  "IsEnabled": false,
  "ChannelId": "Display",
  "FunnelLocation": "Awareness",
  "RTBAttributes": {
    "BaseBidCPM": { "Amount": 1.50, "CurrencyCode": "USD" },
    "MaxBidCPM": { "Amount": 5.00, "CurrencyCode": "USD" }
  }
}

GraphQL example

POST /graphql HTTP/1.1
Content-Type: application/json
TTD-Auth: AUTH_TOKEN_PLACEHOLDER

mutation CreateAdGroup($input: AdGroupCreateInput!) {
  adGroupCreate(input: $input) {
    data {
      id
      name
      campaign { id }
      isEnabled
      channel
      funnelLocation
      baseBidCPMInAdvertiserCurrency
      maxBidCPMInAdvertiserCurrency
    }
    userErrors {
      message
      field
    }
  }
}

Variables:

{
  "input": {
    "campaignId": "cmp123",
    "name": "My RTB Ad Group",
    "isEnabled": false,
    "channel": "DISPLAY",
    "funnelLocation": "AWARENESS",
    "baseBidCPMInAdvertiserCurrency": 1.50,
    "maxBidCPMInAdvertiserCurrency": 5.00
  }
}

The REST example includes RTB budget settings and other nested objects that are not all available on AdGroupCreateInput. Bid lists, campaign defaults, and full RTB targeting still require additional GraphQL mutations or remain REST-only.