Release notes

Page Summary

outlined_flag

• 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-07-30 v1.8

• Added the RemoveAllAudienceMembers method to the IngestionService to remove or replace all audience members for the specified user lists.
  • To get started, review the guide on removing all members from an audience for your specific integration. For example, see the Customer Match guides for Google Ads or Display & Video 360.
• Added support for returning detailed warnings during event and audience ingestion.
  • Added the field_warnings field to IngestEventsResponse and IngestAudienceMembersResponse which contains a list of FieldWarning objects.
  • Added the FieldWarning resource, which contains a reason (WarningReason ), description, and field path.
  • Added the WarningReason enum to define reasons for warnings, such as custom variables not being enabled or missing merchant IDs in cart data.
• Added support for sending additional address fields for Google Analytics event ingestion.
  • Added the address_line, city, and administrative_area fields to AddressInfo (used in UserData).
• Added the INVALID_REMOVE_AS_OF_TIME and REQUIRED_PREREQUISITE_LINK_MISSING error reasons to the ErrorReason enum.

2026-05-28 v1.7

• Added support for sending offline conversion events to Google Marketing Platform products, including Campaign Manager 360, Search Ads 360, and Display & Video 360, using an IngestEventsRequest.

  • Added FLOODLIGHT_CONFIG to the AccountType enum to support Floodlight destinations.
  • Added the dclid, impression_id, match_id, and encrypted_user_ids fields to AdIdentifiers.
  • Added the conversion_count field to the Event resource to support tracking conversion quantities.

  Check out the send events guide to get started, or learn how to upgrade from the Campaign Manager 360 API.

• Added the composite_data field to the AudienceMember resource, which accepts a CompositeData object and lets you combine multiple types of identifiers, such as UserData and IpData. See Composite data for more information.

  • Added new statuses IngestCompositeDataStatus and RemoveCompositeDataStatus that include diagnostics (record_count and data_type_counts) for audience member requests that use CompositeData.

• Added support for the ingestion of IP addresses for Google Ads Customer Match by sending IpData in composite data.

• Added new error reasons FIELD_VALUE_TOO_SHORT, TOO_FEW_ELEMENTS, BASELINE_LOCATION_AUTO_DETECTION_FAILED, and INSIGHTS_MISSING_FOR_DIMENSION to the ErrorReason enum.

• Added new diagnostic values to ProcessingErrorReason to provide more granular feedback for failures during event ingestion.

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