Release notes

AI-generated Key Takeaways

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.

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.

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

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.

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:
Audiences managed using the Data Manager API are only eligible for targeting if they have at least 1,000 members.