The Data Manager API is in closed beta. To express interest in joining the closed beta, fill out
this form.
版本说明
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
您可以在此处了解每个数据管理器 API 版本中的变化。
2025-08-06 v1.2
- 新增了对使用
IngestEvents
方法向 Google Ads 目标平台发送线下转化数据和增强型潜在客户转化数据的支持。如需了解如何为这些转化配置加密,请参阅更新后的加密指南。
- 向
EventSource
枚举添加了 APP
、IN_STORE
、PHONE
和 OTHER
值。线下转化和增强型潜在客户转化需要 event_source
。
- 向
Event
添加了 user_properties
字段。将此字段设置为 UserProperties
对象,以在发生相应事件时添加有关用户的广告客户评估信息。
- 向
CustomVariable
添加了 destination_references
重复字段。使用此字段可仅将自定义变量值应用于 Event
的部分目的地。
- 针对线下转化和增强型潜在客户转化添加了以下错误:
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
2025-04-02 v1.0
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-08。
[null,null,["最后更新时间 (UTC):2025-08-08。"],[],[],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."]]