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

## 2026-11-04 v1.9

- Added support for sending Google Ads
  [call conversions](https://developers.google.com/data-manager/api/devguides/events/google-ads/call).

  - Added the `call_info` field to [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.Event). Use the `start_timestamp` field of [`CallInfo`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.CallInfo) to specify when the phone call that led to the conversion started.

  Check out the
  [send call conversions guide](https://developers.google.com/data-manager/api/devguides/events/google-ads/call/send-events)
  to get started, or
  [learn how to upgrade from the Google Ads API](https://developers.google.com/data-manager/api/devguides/events/google-ads/call/upgrade).
- Added the `record_indices` field to
  [`ErrorCount`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.ErrorCount) and
  [`WarningCount`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.WarningCount) to
  identify the records in the ingestion request that had each processing
  error or warning. For details on how to use this field, see
  [Check affected records](https://developers.google.com/data-manager/api/devguides/diagnostics#record_indices).

- Added the `lead_id` field to
  [`AdIdentifiers`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.AdIdentifiers) to
  support sending the Google-generated ID issued when a user submits a lead
  form.

- Added the `ENCRYPTION_NOT_SUPPORTED`, `DUPLICATE_ELEMENTS`,
  `UNSUPPORTED_BASELINE_LOCATION`, `CONVERSION_PRECEDES_CALL`,
  `INVALID_AD_IDENTIFIER_FOR_ACCOUNT`,
  `CONVERSION_ACTION_TOO_RECENTLY_CREATED`, `REQUEST_TOO_OLD`, and
  `INVALID_DATE` error reasons to the
  [`ErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.ErrorReason) enum.

- Added the `PROCESSING_ERROR_REASON_DESTINATION_TOO_RECENTLY_CREATED`,
  `PROCESSING_ERROR_REASON_TOO_RECENT_CALL`,
  `PROCESSING_ERROR_REASON_EXPIRED_CALL`, and
  `PROCESSING_ERROR_REASON_INVALID_CALL` error reasons to the
  [`ProcessingErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.ProcessingErrorReason)
  enum.

- Added the `PROCESSING_WARNING_REASON_CUSTOM_VARIABLE_NOT_ENABLED` and
  `PROCESSING_WARNING_REASON_CUSTOM_VARIABLE_NOT_PREDEFINED` warning reasons
  to the
  [`ProcessingWarningReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.ProcessingWarningReason)
  enum.

- Added the `WARNING_REASON_INVALID_NUMBER_FORMAT` warning reason to the
  [`WarningReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.WarningReason) enum.

## 2026-07-30 v1.8

- Added the [`RemoveAllAudienceMembers`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.IngestionService.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](https://developers.google.com/data-manager/api/devguides/audiences/google-ads/customer-match/remove-all-members) or [Display \& Video 360](https://developers.google.com/data-manager/api/devguides/audiences/display-video/customer-match/remove-all-members).
- Added support for returning [detailed
  warnings](https://developers.google.com/data-manager/api/devguides/concepts/understand-errors#ingestion-warnings) during event and audience ingestion.
  - Added the `field_warnings` field to `IngestEventsResponse` and `IngestAudienceMembersResponse` which contains a list of [`FieldWarning`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.FieldWarning) objects.
  - Added the [`FieldWarning`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.FieldWarning) resource, which contains a `reason` ([`WarningReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.WarningReason) ), `description`, and `field` path.
  - Added the [`WarningReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.AddressInfo) (used in `UserData`).
- Added the `INVALID_REMOVE_AS_OF_TIME` and `REQUIRED_PREREQUISITE_LINK_MISSING` error reasons to the [`ErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.ErrorReason) enum.

## 2026-05-28 v1.7

- Added support for [sending offline conversion events](https://developers.google.com/data-manager/api/devguides/events)
  to Google Marketing Platform products, including Campaign Manager 360,
  Search Ads 360, and Display \& Video 360, using an
  [`IngestEventsRequest`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingesteventsrequest).

  - Added `FLOODLIGHT_CONFIG` to the [`AccountType`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#accounttype) enum to support [Floodlight
    destinations](https://developers.google.com/data-manager/api/devguides/concepts/destinations#floodlight-advertiser).
  - Added the `dclid`, `impression_id`, `match_id`, and [`encrypted_user_ids`](https://developers.google.com/data-manager/api/devguides/events/cm360/offline/send-events#add_encrypted_user_ids) fields to [`AdIdentifiers`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#adidentifiers).
  - Added the `conversion_count` field to the [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.Event) resource to support tracking conversion quantities.

  Check out the [send events guide](https://developers.google.com/data-manager/api/devguides/events/cm360/offline/send-events)
  to get started, or [learn how to upgrade from the Campaign Manager 360
  API](https://developers.google.com/data-manager/api/devguides/events/cm360/offline/upgrade).
- Added the `composite_data` field to the
  [`AudienceMember`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#audiencemember) resource, which accepts a
  [`CompositeData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#compositedata) object and lets you
  combine multiple types of identifiers, such as
  [`UserData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.UserData) and
  [`IpData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ipdata). See [Composite
  data](https://developers.google.com/data-manager/api/devguides/audiences/send-audience-members#composite-data) for more
  information.

  - Added new statuses [`IngestCompositeDataStatus`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestcompositedatastatus) and [`RemoveCompositeDataStatus`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#removecompositedatastatus) that include diagnostics (`record_count` and `data_type_counts`) for audience member requests that use [`CompositeData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#compositedata).
- Added support for the [ingestion of IP addresses for Google Ads Customer
  Match](https://developers.google.com/data-manager/api/devguides/audiences/send-audience-members#send-ip-timestamp)
  by sending [`IpData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#errorreason)
  enum.

- Added new diagnostic values to
  [`ProcessingErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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](https://developers.google.com/data-manager/api/devguides/events/google-ads/store-sales) using an [`IngestEventsRequest`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingesteventsrequest). To use this feature, your Google Ads account must meet certain [eligibility
  requirements](https://support.google.com/google-ads/answer/15885010).
  - Added the `event_location` field to [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.Event), which supports providing a physical `store_id.`
  - Added the `third_party_user_data` field to [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.Event), allowing ingested data to be explicitly flagged as being owned by a third party.
    - Populating this field is only allowed for [data
      partners](https://developers.google.com/data-manager/api/devguides/events/google-ads/store-sales/send-events#data-partner).
  - Added the following fields to the [`Item`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#item) resource:
    - `merchant_id`
    - `merchant_feed_label`
    - `merchant_feed_language_code`
    - `conversion_value`
    - `custom_variables` (accepts a list of [`ItemCustomVariable`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.ItemCustomVariable) objects)
  - Check out the following guides to get started:
    - [Upgrade from Google Ads](https://developers.google.com/data-manager/api/devguides/events/google-ads/store-sales/upgrade)
    - [Send events](https://developers.google.com/data-manager/api/devguides/events/google-ads/store-sales/send-events)
- Added support for sending any web or app event to Google Analytics that isn't a [reserved
  event](https://support.google.com/analytics/answer/13316687#reserved).
  - Added the `app_instance_id` field to the [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.Event) resource.
  - Added fields to [`DeviceInfo`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#deviceinfo) to provide metadata about the user's device.
  - Added the `mobile_device_id` field to [AdIdentifiers](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#adidentifiers).
  - Added the `event_location` field to [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#google.ads.datamanager.v1.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](https://developers.google.com/data-manager/api/devguides/events/analytics/recommended-custom-events)
    - [Upgrade from Measurement Protocol](https://developers.google.com/data-manager/api/devguides/events/analytics/measurement-protocol/upgrade)
    - [Recommended events reference](https://developers.google.com/data-manager/api/reference/analytics/recommended-events)
- Added support for sending [*any event with a transaction
  ID*](https://developers.google.com/data-manager/api/devguides/events/analytics/online) to both web and app data streams as an additional data source for your tag or [Google Analytics for Firebase
  (GA4F)
  SDK](https://firebase.google.com/docs/analytics/get-started) implementations.
  - This feature is limited to Google Analytics properties on an allowlist; [fill out this form](https://forms.gle/PUT2AsLVM1krd5zm6) if you're interested in adding your property to the allowlist.
- Added the `coupon_codes` field to [`CartData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#sizeinfo) resource.

## 2026-03-26

- Added `EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED` to the
  [`ErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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](https://support.google.com/adspolicy/answer/6014595).

  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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#userlistservice) ([`create`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#createuserlistrequest), [`update`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#updateuserlistrequest), and [`delete`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#deleteuserlistrequest))
  - [`IngestionService`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) ([`ingestAudienceMembers`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestaudiencemembersrequest))

  To resolve the error, advertisers must provide the mandatory declaration in
  the Google Ads UI. [Learn more about how to confirm for your
  account](https://support.google.com/adspolicy/answer/15577076).
- Added `INVALID_MERCHANT_ID` to the
  [`ErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#userlist) resource and [`UserListService`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#userlistservice) to allow for creating, retrieving, updating, and deleting user lists.
  - Check out the [Google Ads](https://developers.google.com/data-manager/api/devguides/audiences/google-ads/customer-match) or [Display \& Video 360](https://developers.google.com/data-manager/api/devguides/audiences/display-video/customer-match) 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](https://developers.google.com/data-manager/api/devguides/audiences/google-ads/customer-match/upgrade) or [Display \& Video 360](https://developers.google.com/data-manager/api/devguides/audiences/display-video/customer-match/upgrade) upgrade guides for migration steps.
- Added support for sending **User ID** through audience member ingestion, enabling its use with [Customer Match](https://developers.google.com/data-manager/api/devguides/audiences/google-ads/customer-match) in Google Ads.
  - Added [`UserIdData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#useriddata) to [`AudienceMember`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#audiencemember).
  - Added [`IngestUserIdDataStatus`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestuseriddatastatus) and [`RemoveUserIdDataStatus`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#removeuseriddatastatus) to the statuses returned by the `RetrieveRequestStatus` method. Use these fields to [retrieve diagnostics information](https://developers.google.com/data-manager/api/devguides/diagnostics) about User ID ingestion and removal.
- Added the [`PartnerLink`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#partnerlink) resource and [`PartnerLinkService`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#partnerlinkservice) to create and manage links between advertiser and data partner accounts.
  - Check out the [Partner links guides](https://developers.google.com/data-manager/api/devguides/accounts/partner-links) 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](https://forms.gle/PUT2AsLVM1krd5zm6) 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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#event):
    - `event_name`
    - `client_id`
    - `user_id`
    - `additional_event_parameters`
  - Added `additional_user_properties` to [`UserProperties`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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](https://developers.google.com/data-manager/api/devguides/events/analytics/online/send-events).
- Added [`AwsWrappedKeyInfo`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#awswrappedkeyinfo)
  to support using [encryption](https://developers.google.com/data-manager/api/devguides/concepts/encryption) keys from
  [AWS Key Management Service](https://docs.aws.amazon.com/kms/).

- Added the following enum values to [`ErrorReason`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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](https://forms.gle/UiqvKxMUZ9eJJEVL9) if you're interested in adding your
  account.

  Fill out the [partner interest
  form](https://docs.google.com/forms/d/e/1FAIpQLScFEkLVqElsjYJ21h7z0mSUk8Tj1M3TEMwouFPQb7qyM-oI5w/viewform)
  to express interest in becoming a data partner.
- Added the `RetrieveRequestStatus` method for
  [retrieving diagnostic information](https://developers.google.com/data-manager/api/devguides/diagnostics) for event and
  audience ingestion requests.

- The `product` field of [`ProductAccount`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#productaccount) and
  the [`Product`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#product) enum have been deprecated. Use the
  `account_type` field and the new [`AccountType`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#accounttype)
  enum instead.

- Added support for specifying the `destination` for each
  [`AudienceMember`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestaudiencemembersrequest) in an
  [`IngestAudienceMembersRequest`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#destination). 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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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](https://developers.google.com/data-manager/api/devguides/events) to Google Ads destinations using the [`IngestEvents`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) method. See the [updated
  encryption guide](https://developers.google.com/data-manager/api/devguides/concepts/encryption) for how to configure encryption for these conversions.
- Added `APP`, `IN_STORE`, `PHONE`, and `OTHER` values to the [`EventSource`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#eventsource) enum. An `event_source` is required for offline conversions and enhanced conversions for leads.
- Added the `user_properties` field to [`Event`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#event). Set this field to a [`UserProperties`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#userproperties) object to add [advertiser-assessed
  information](https://support.google.com/google-ads/answer/14007601) about a user when the event occurred.
- Added a `destination_references` repeated field to [`CustomVariable`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#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`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) method to the `IngestionService`. [Use
  IngestEvents](https://developers.google.com/data-manager/api/devguides/events) 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](https://ads.google.com/) and [Display \& Video
  360](https://marketingplatform.google.com/about/display-video-360/).
- Added support for [gRPC](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1) and [REST](https://developers.google.com/data-manager/api/reference/rest).
- Added the [IngestionService](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) with `IngestAudienceMembers` and `RemoveAudienceMembers` methods for managing audience members using the following data types:
  - [Contact information](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#useridentifier)
  - [Mobile IDs](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#mobiledata)
  - [PAIR IDs](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#pairdata)
- Audiences managed using the Data Manager API are only eligible for targeting if they have at least 1,000 members.