Announced Deprecations

Timeline:

• May 17, 2023: line items using manual triggers will stop serving in Display & Video 360. If you activate a manual trigger linked to an active line item after this date, the line item will not serve ads.
• August 1, 2023: advertisers.manualTriggers service in DV360 API v1 and v2, LINE_ITEM_FLIGHT_DATE_TYPE_TRIGGER enum value in DV360 API v1, and the LineItemFlight.triggerId field in DV360 API v1 will be sunset. After this date, requests made to these services or to these fields will return an error.

Recommended actions:

• Immediately stop using manual triggers to start and stop line item serving.
• Stop making requests to the advertisers.manualTriggers service.
• Update the flight.flightDateType and flight.triggerId fields for all line items using manual triggers.

Timeline:

• May 20, 2023: You will no longer be able to assign GoogleAudience resources with a GoogleAudienceType of GOOGLE_AUDIENCE_TYPE_INSTALLED_APPS or GOOGLE_AUDIENCE_TYPE_NEW_MOBILE_DEVICES to line item or insertion order audience targeting. Requests assigning these audiences to a line item's audience targeting will return an error. This includes advertisers.lineItems.duplicate and advertisers.lineItems.generateDefault requests, if the created line item would include deprecated audiences in its audience targeting.
• June 8, 2023: Impacted audiences will be removed from all line item and insertion order targeting and from all combined audiences. If a line item is not able to serve ads when these audiences are removed, they will be paused. On this date, these audiences will also no longer be retrievable using the googleAudiences service.

Recommended Tasks:

• We recommend that you immediately stop using impacted audiences when making future updates to your line item targeting.
• Remove all impacted audiences from existing line item and insertion order targeting. Read about updating audience targeting in our Target Audiences guide.

Timeline:

• May 20, 2023: You will no longer be able to assign FirstAndThirdPartyAudience resources with a AudienceType of ACTIVITY_BASED or FREQUENCY_CAP to line item or insertion order audience targeting. Requests assigning these audiences to a line item's audience targeting will return an error. This includes advertisers.lineItems.duplicate and advertisers.lineItems.generateDefault requests, if the created line item would include deprecated audiences in its audience targeting.
• June 8, 2023: Impacted audiences will be removed from all line item and insertion order targeting and from all combined audiences. If a line item is not able to serve ads when these audiences are removed, they will be paused. On this date, these audiences will also no longer be retrievable using the firstAndThirdPartyAudiences service.

Recommended Tasks:

• We recommend that you immediately stop using impacted audiences when making future updates to your line item targeting.
• Remove all impacted audiences from existing line item and insertion order targeting. Read about updating audience targeting in our Target Audiences guide.

On May 30, 2023, existing usage limits will be replaced with a hybrid quota structure that does the following:

1. Eliminates the requests per day per project quota.
2. Institutes a requests per minute per advertiser per project quota for qualifying methods.

These new limits will allow greater flexibility in API usage and enable parallelization of requests across advertisers. Details of this change are in our existing quota limit documentation.

On June 21, 2023, LIST request filter parameters will no longer allow OR logical operators to be used between restrictions of different fields.

For example, resources identified with filter string lineItemType="LINE_ITEM_TYPE_DISPLAY_DEFAULT" OR insertionOrderId="123" must instead be retrieved using two LIST requests with the following filter strings:

• lineItemType="LINE_ITEM_TYPE_DISPLAY_DEFAULT"
• insertionOrderId="123"

Reference our how-to guide on filtering LIST requests for more details on the restrictions of logical operators.

Review the filter query parameters of all your existing LIST calls and verify that they are using the OR logical operator correctly before June 21, 2023 to avoid an interruption of service.

Initial Effective Date updated

On June 21, 2023, budget.budget_segments.date_range.end_date and flight.dateRange.endDate will no longer be accepted fields in advertisers.insertionOrders.list and advertisers.lineItems.list filter and orderBy query parameters, respectively. After this date, requests using these fields in the filter and orderBy query parameters will return an error.

Remove all filter and order logic using these two fields before June 21, 2023 to avoid an interruption of service.

On June 21, 2023, advertisers.lineItems.list will no longer support filtering by the following fields:

• flight.triggerId
• targetedChannelId
• targetedNegativeKeywordListId
• warningMessages

Remove all filter logic using these four fields before June 21, 2023 to avoid an interruption of service.

On August 1, 2023, insertion orders using outcome based buying, defined by a billableOutcome field value of BILLABLE_OUTCOME_PAY_PER_CLICK or BILLABLE_OUTCOME_PAY_PER_VIEWABLE_IMPRESSION, and their child line items will be archived.

This change will affect the following requests:

• Attempting to use advertisers.insertionOrders.create to create an insertion order using outcome based buying will return a 400 error
• Attempting to use advertisers.lineItems.create, advertisers.lineItems.duplicate, or advertisers.lineItems.generateDefault to create a line item under an insertion order using outcome based buying will return a 400 error
• Given that archived resources are not included in LIST requests by default, impacted resources will no longer be returned by advertisers.insertionOrders.list and advertisers.lineItems.list methods by default.