Display & Video 360 API to Remove Certain Targeting Options and Update Pacing

On September 30, 2024, the majority of Digital Content Label and Other Content Types exclusion targeting will no longer be available for YouTube & partners line items. In the Display & Video 360 API, all TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION (excluding CONTENT_RATING_TIER_FAMILIES values) and TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION AssignedTargetingOptions will be removed. This will impact responses from assigned targeting LIST requests, and attempts to retrieve these resources using advertisers.lineItems.targetingTypes.assignedTargetingOptions.get will return a 404 error. In Structured Data Files, Line Item files will no longer use values like “Embedded Videos”, “Live Streaming”, “All Audiences”, “Younger Teens”, “Teens”, “Adults”, and “Not Yet Rated” in the “TrueView Category Exclusions Targeting” column. Generated files will no longer populate these values, and line item file entries using these configurations will fail on upload.

To prepare for the sunset of Oracle first- and third-party audiences on September 30, 2024, review the audiences used in your resource targeting and identify any Oracle audiences. Remove these audiences to avoid any interruption of service. If you cache audience IDs, make sure to remove any of these audiences from your cache. In the Display & Video 360 API, TARGETING_TYPE_AUDIENCE_GROUP AssignedTargetingOptions will be updated to remove sunset audiences, and requests to add sunset audiences will return a 400 error. In Structured Data Files, IDs of sunset audiences will no longer be included in relevant columns, and file entries using sunset audience IDs will fail on upload.

Starting September 30, 2024, line items using specific bid strategies will no longer be able to use optimized targeting. These bid strategies include:

• Maximum views with in-view time over 10 seconds
• Maximum completed in-view and audible views
• Maximum viewable impressions
• Target viewable CPM

In the Display & Video 360 API, LineItem resources with targetingExpansion.enableOptimizedTargeting set to True and specific performance goal types will be updated to set targetingExpansion.enableOptimizedTargeting to False. Requests creating or updating LineItem resources with these configurations will return a 400 error. In Structured Data Files, Line Item file entries with certain bid strategy types will be updated to set the “Optimized Targeting” column to False, and entries using sunset configurations will fail on upload.

To handle the sunset of 'Flight ASAP' pacing for insertion orders on November 5, 2024, update the pacing of any existing insertion orders currently using the 'Flight ASAP' configuration. In the Display & Video 360 API, InsertionOrder resources with a pacing.pacingPeriod of PACING_PERIOD_FLIGHT and a pacing.pacingType of PACING_TYPE_ASAP will be updated to use a pacing.pacingType of PACING_TYPE_AHEAD. Requests creating or updating InsertionOrder resources with this configuration will return a 400 error. In Structured Data Files, Insertion Order file entries with 'Flight' and 'ASAP' values in 'Pacing' and 'Pacing Rate' columns will be updated to an 'Ahead' value in the 'Pacing Rate' column. Entries using the sunset configuration will fail on upload.