The Data Manager API is in closed beta. To express interest in joining the closed beta, fill out this form
.
Release notes
Stay organized with collections
Save and categorize content based on your preferences.
Here's where you can learn what's changed in each Data Manager API release.
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:
- Audiences managed using the Data Manager API are only eligible for targeting
if they have at least 1,000 members.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-05 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-05 UTC."],[],[],null,["# Release notes\n\nHere's where you can learn what's changed in each Data Manager API release.\n\n2025-08-06 v1.2\n---------------\n\n- Added support for [sending offline\n conversions and enhanced conversions for leads](/data-manager/api/get-started/quickstart/send-events) to Google Ads destinations using the [`IngestEvents`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) method. See the [updated encryption guide](/data-manager/api/get-started/encryption) for how to configure encryption for these conversions.\n- Added `APP`, `IN_STORE`, `PHONE`, and `OTHER` values to the [`EventSource`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#eventsource) enum. An `event_source` is required for offline conversions and enhanced conversions for leads.\n- Added the `user_properties` field to [`Event`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#event). Set this field to a [`UserProperties`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#userproperties) object to add [advertiser-assessed\n information](//support.google.com/google-ads/answer/14007601) about a user when the event occurred.\n- Added a `destination_references` repeated field to [`CustomVariable`](/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`.\n- Added the following errors for offline conversions and enhanced conversions for leads:\n - `DESTINATION_ACCOUNT_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS`\n - `DESTINATION_ACCOUNT_DATA_POLICY_PROHIBITS_ENHANCED_CONVERSIONS`\n - `DESTINATION_ACCOUNT_ENHANCED_CONVERSIONS_TERMS_NOT_SIGNED`\n\n2025-06-25 v1.1\n---------------\n\n- Added the [`IngestEvents`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) method to the `IngestionService`. [Use\n IngestEvents](/data-manager/api/get-started/quickstart/send-events) as an additional data source for your tag conversions, to maximize ad interaction signals and strengthen your data and overall performance.\n\n2025-04-02 v1.0\n---------------\n\n- First release of the Data Manager API, with support for sending audience data to [Google Ads](//ads.google.com/) and [Display \\& Video\n 360](//marketingplatform.google.com/about/display-video-360/).\n- Added support for [gRPC](/data-manager/api/reference/rpc/google.ads.datamanager.v1) and [REST](/data-manager/api/reference/rest).\n- Added the [IngestionService](/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice) with `IngestAudienceMembers` and `RemoveAudienceMembers` methods for managing audience members using the following data types:\n - [Contact information](/data-manager/api/reference/rpc/google.ads.datamanager.v1#useridentifier)\n - [Mobile IDs](/data-manager/api/reference/rpc/google.ads.datamanager.v1#mobiledata)\n - [PAIR IDs](/data-manager/api/reference/rpc/google.ads.datamanager.v1#pairdata)\n- Audiences managed using the Data Manager API are only eligible for targeting if they have at least 1,000 members."]]
