Q2 2024
Report and Optimize
Real-time bidding update
On April 15, 2024, Google will deprecate video_completion_rate and click_through_rate metrics under the BidRequest.Imp.metric field in OpenRTB bid requests along with BidRequest.AdSlot.video_completion_rate and BidRequest.AdSlot.click_through_rate fields in Google RTB bid requests.
Other product or Help Center updates
Google RTB Protocol Sunset
Google will sunset the Google Authorized Buyers protocol on February 15, 2025 to more closely align with the industry. Bidders should migrate to OpenRTB protocol prior to this time. More information will be provided to assist with migration.
Publisher Provided ID for RTB
Publisher Provided Identifiers (PPIDs), now in open beta, allow publishers to send an identifier for frequency capping and interest-based ads personalization across devices. Publishers manage which Authorized Buyers, Open Bidders, and SDK bidders receive PPIDs. Only Authorized Buyers, Open Bidders, and SDK bidders opted-in by a given publisher will receive PPID from that publisher. Publisher Provided ID (PPID) is not available with 3P user ids, such as google_user_id, hosted_match_data, device ids, and is not available in the EEA. See the Developer release notes for proto specs.
SKOverlay now supported across all full screen mApp formats
We now support SKOverlay across all mApp full-screen formats on iOS.
To determine SKOverlay eligibility, bidders can reference skadn.skoverlay in the bid request. To use this feature, bidders will need to first set a value for skadn.itunesitem in the SKAdNetworkResponse object back to Google. Bidders also need to set the skadn.skoverlay object in the bid response back to Google with the below.
Q1 2024
Policy
Updates to Personalization & Tracking on Mobile Devices
Beginning March 21, 2024, bid requests will no longer disallow ad personalization based on a user not consenting to App Tracking Transparency (ATT) on iOS 14.5+ or deleting their Advertising ID on Android. The below fields should continue to be used to understand a user’s personalization and tracking settings:
-
We will continue to populate the non_personalized_ads_reason field with the appropriate reason for other situations where personalization is not permitted. This field will no longer be set on the basis of a user not consenting to App Tracking Transparency (ATT) on iOS 14.5+ or deleting their Advertising ID on Android.
-
When a user has not consented to ATT on iOS 14.5+ or has deleted their Advertising ID on Android, we will continue to set
limit_ad_tracking = true / lmt = 1. For granular ATT status information, continue to refer to theapp_tracking_authorization / attsfields.
Other product or Help Center updates
Provide Consent for Cookie Matching Requests from EEA+UK
Partner-initiated requests to Google's real-time cookie matching flows from the EEA+UK must provide end-user consent, in accordance with Google's EU User Consent Policy, through one of two mechanisms:
- A TCFv2 string in the
gdpr_consentURL parameter - The
process_consent=TURL parameter, after gathering affirmative consent
Starting March 6, 2024, requests that are subject to the EU User Consent Policy and fail to provide affirmative consent signals will receive an error response.
Removing Seller Network ID from Google Proto
Seller Network ID was removed from the Google Proto in February 2024. To receive the similar information to identify a publisher, please begin using the publisher ID field (BidRequest.publisher_id). Learn more about the existing publisher ID.
There were no release notes for February 26, 2024.
There were no release notes for February 12, 2024.
There were no release notes for January 29, 2024.
Troubleshoot
VAST Error reasons displaying in Creatives UI
More information is provided within the Creatives UI to troubleshoot error reasons. Learn more about each of these errors and how to resolve them.
Policy
Bulk Uploader API
Partners should obtain end-user consent, in accordance with Google's EU User Consent Policy, before adding a user to a user list. Ad tech partners using the Bulk Upload API must indicate that they have gathered the proper legal consent using the process_consent flag.
Starting January 2024, requests without process_consent=true will return a missing consent error but continue to be processed without change. Starting March 2024, requests without process_consent=true will be dropped entirely.
Cookie Matching
Partner-initiated requests to Google's real-time cookie matching flows from the EEA+UK must provide end-user consent, in accordance with Google's EU User Consent Policy, through one of two mechanisms:
- A TCFv2 string in the gdpr_consent URL parameter
- The
process_consent=TURL parameter, after gathering affirmative consent
Starting March 2024, requests that are subject to the EU User Consent Policy and fail to provide affirmative consent signals will receive an error response.