Release notes

Page Summary

• The Data Manager API is now generally available as of v1.3.

• Version 1.3 introduced the RetrieveRequestStatus method for diagnostics, deprecated the product field, added support for specifying destination for audience members, and lowered the audience targeting threshold to 100 members.

• Version 1.2 added support for sending offline conversions and enhanced conversions for leads to Google Ads, introduced new EventSource values, added the user_properties field to Event, and added a destination_references field to CustomVariable.

• Version 1.1 added the IngestEvents method to the IngestionService to maximize ad interaction signals.

• The initial release, v1.0, supported sending audience data to Google Ads and Display & Video 360, included gRPC and REST support, and introduced the IngestionService for managing audience members with various data types.

Here's where you can learn what's changed in each Data Manager API release.

2026-05-07 v1.6

• Added support for sending Google Ads store sales conversions using an IngestEventsRequest. To use this feature, your Google Ads account must meet certain eligibility requirements.
  • Added the event_location field to Event, which supports providing a physical store_id.
  • Added the third_party_user_data field to Event, allowing ingested data to be explicitly flagged as being owned by a third party.
    • Populating this field is only allowed for data partners.
  • Added the following fields to the Item resource:
    • merchant_id
    • merchant_feed_label
    • merchant_feed_language_code
    • conversion_value
    • custom_variables (accepts a list of ItemCustomVariable objects)
  • Check out the following guides to get started:
    • Upgrade from Google Ads
    • Send events
• Added support for sending any web or app event to Google Analytics that isn't a reserved event.
  • Added the app_instance_id field to the Event resource.
  • Added fields to DeviceInfo to provide metadata about the user's device.
  • Added the mobile_device_id field to AdIdentifiers.
  • Added the event_location field to Event to capture fields like city, subdivision_code, region_code, subcontinent_code, and continent_code.
  • Check out the following guides to get started:
    • Send recommended and custom events
    • Upgrade from Measurement Protocol
    • Recommended events reference
• Added support for sending any event with a transaction ID to both web and app data streams as an additional data source for your tag or Google Analytics for Firebase (GA4F) SDK implementations.
  • This feature is limited to Google Analytics properties on an allowlist; fill out this form if you're interested in adding your property to the allowlist.
• Added the coupon_codes field to CartData to track all coupon codes applied to the cart for events sent to Google Ads and Google Analytics.
  • For coupon redemption use cases in Google Ads, use the OFFLINE_PROMOTION_REDEMPTION conversion type.
• Added a new OAuth scope, https://www.googleapis.com/auth/datamanager.partnerlink, for methods related to creating, searching, and deleting partner links.
• Added new values to the ErrorReason enum to support detailed validation for store sales and Google Analytics event ingestion.
• Added the youtube_members_count and gmail_members_count fields to the SizeInfo resource.

2026-03-26

• Added EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED to the ErrorReason enum.

  To comply with European Union Political Ads Regulation (EU PAR), Google requires all customers to self-declare whether their ads are considered political under EU PAR. Learn how an EU political ad is defined and Google's restrictions on political ads in the EU.

  Starting April 1, 2026, the following operations on accounts lacking this declaration may be restricted or fail with the error EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED.

  • UserListService (create, update, and delete)
  • IngestionService (ingestAudienceMembers)

  To resolve the error, advertisers must provide the mandatory declaration in the Google Ads UI. Learn more about how to confirm for your account.

• Added INVALID_MERCHANT_ID to the ErrorReason enum.

2026-02-17 v1.5

The Data Manager API now supports the entire end to end workflow for managing audiences, including audience creation, ingestion, and retrieval.

• Added the UserList resource and UserListService to allow for creating, retrieving, updating, and deleting user lists.
  • Check out the Google Ads or Display & Video 360 guides for an end-to-end walkthrough of how to create, populate, and verify Customer Match audiences using the Data Manager API.
  • See the Google Ads or Display & Video 360 upgrade guides for migration steps.
• Added support for sending User ID through audience member ingestion, enabling its use with Customer Match in Google Ads.
  • Added UserIdData to AudienceMember.
  • Added IngestUserIdDataStatus and RemoveUserIdDataStatus to the statuses returned by the RetrieveRequestStatus method. Use these fields to retrieve diagnostics information about User ID ingestion and removal.
• Added the PartnerLink resource and PartnerLinkService to create and manage links between advertiser and data partner accounts.
  • Check out the Partner links guides to get started.

2026-02-10

Sending conversions with multiple data sources to boost performance and data strength is now generally available to all Google Ads accounts.

This feature is still only available to Google Analytics properties on an allowlist. Fill out the form if you're interested in adding your Google Analytics property to the allowlist.

2025-11-05 v1.4

• Added support for sending Google Analytics purchase events as an additional data source for your tag conversions, to maximize ad interaction signals and strengthen your data and overall performance.

  • Added GOOGLE_ANALYTICS_PROPERTY to the AccountType enum.
  • Added multiple fields to Event:
    • event_name
    • client_id
    • user_id
    • additional_event_parameters
  • Added additional_user_properties to UserProperties.

  Read more about sending Google Analytics purchase events and how to map Google Analytics event parameters and user properties to their Data Manager API equivalents in the events guide.

• Added AwsWrappedKeyInfo to support using encryption keys from AWS Key Management Service.

• Added the following enum values to ErrorReason:

  • EVENT_TIME_INVALID
  • FIELD_VALUE_TOO_LONG
  • INVALID_EVENT_NAME
  • INVALID_PROPERTY_TYPE
  • INVALID_REQUEST_ID
  • INVALID_STREAM_TYPE
  • LINKED_ACCOUNT_ONLY_ALLOWED_WITH_DATA_PARTNER_LOGIN_ACCOUNT
  • MULTIPLE_DESTINATIONS_FOR_GOOGLE_ANALYTICS_EVENT
  • NOT_ALLOWLISTED
  • OPERATING_ACCOUNT_LOGIN_ACCOUNT_MISMATCH
  • RESERVED_NAME_USED
  • TOO_MANY_ELEMENTS
  • UNSUPPORTED_LINKED_ACCOUNT_FOR_DATA_PARTNER
  • UNSUPPORTED_OPERATING_ACCOUNT_FOR_DATA_PARTNER

2025-10-06 v1.3

• The Data Manager API is now generally available to all users.

  Sending conversions with multiple data sources to boost performance and data strength is still only available to accounts on an allowlist. Fill out the form if you're interested in adding your account.

  Fill out the partner interest form to express interest in becoming a data partner.

• Added the RetrieveRequestStatus method for retrieving diagnostic information for event and audience ingestion requests.

• The product field of ProductAccount and the Product enum have been deprecated. Use the account_type field and the new AccountType enum instead.

• Added support for specifying the destination for each AudienceMember in an IngestAudienceMembersRequest. Use this feature to send audience data to multiple, distinct destinations in a single request.

• Audiences ingested with the API are now eligible for targeting once they have at least 100 members. Previously, the member threshold was one thousand members.

• The transaction_id of an Event is now optional when sending offline conversions or enhanced conversions for leads. The transaction_id is still required when sending offline conversions as an additional data source to boost performance and data strength.

2025-08-06 v1.2

• Added support for sending offline conversions and enhanced conversions for leads to Google Ads destinations using the IngestEvents method. See the updated encryption guide for how to configure encryption for these conversions.
• Added APP, IN_STORE, PHONE, and OTHER values to the EventSource enum. An event_source is required for offline conversions and enhanced conversions for leads.
• Added the user_properties field to Event. Set this field to a UserProperties object to add advertiser-assessed information about a user when the event occurred.
• Added a destination_references repeated field to CustomVariable. Use this field to apply a custom variable value to only a subset of the destinations for an Event.
• Added the following errors for offline conversions and enhanced conversions for leads:
  • DESTINATION_ACCOUNT_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS
  • DESTINATION_ACCOUNT_DATA_POLICY_PROHIBITS_ENHANCED_CONVERSIONS
  • DESTINATION_ACCOUNT_ENHANCED_CONVERSIONS_TERMS_NOT_SIGNED

2025-06-25 v1.1

• Added the IngestEvents method to the IngestionService. Use IngestEvents as an additional data source for your tag conversions, to maximize ad interaction signals and strengthen your data and overall performance.

2025-04-02 v1.0

• First release of the Data Manager API, with support for sending audience data to Google Ads and Display & Video 360.
• Added support for gRPC and REST.
• Added the IngestionService with IngestAudienceMembers and RemoveAudienceMembers methods for managing audience members using the following data types:
  • Contact information
  • Mobile IDs
  • PAIR IDs
• Audiences managed using the Data Manager API are only eligible for targeting if they have at least 1,000 members.