The Data Manager API is in closed beta. To express interest in joining the closed beta, fill out
this form.
最佳实践
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
使用 Data Manager API 时,请牢记以下最佳实践。
发送所有用户标识符
无论是使用 UserData
发送受众群体成员还是事件,请添加尽可能多的 user_identifiers
,包括发送同一类型的多个标识符。
例如,如果用户有多个电子邮件地址,请为每个电子邮件地址添加单独的 UserIdentifier
。同样,如果您有用户的不同类型标识符(例如电子邮件地址、电话号码和地址),请为每个标识符添加单独的 UserIdentifier
,最多不超过标识符数量上限。
优化请求
为了降低超出每日请求数限制的可能性,请在每个请求中批量处理尽可能多的项,但不得超过每个请求的限制。
例如,如果您想向某个受众群体添加 1 万名受众群体成员,请在一个 IngestAudienceMembersRequest
中添加 audience_members
列表中的所有 1 万名成员。与为添加每个受众群体成员而发送单独的请求相比,在单个请求中批量添加所有 10,000 名成员的效率要高得多。
发送并发请求
如需缩短提取数据所需的总时间,请向 IngestionService
发送并发请求。我们建议您最多同时发送 10 个请求,以降低超出每分钟请求数限制的可能性。
您可以发送并发请求,即使这些请求具有相同的 destinations
也是如此。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[],[],null,["# Best practices\n\nKeep the following best practices in mind when using the Data Manager API.\n\nSend all user identifiers\n-------------------------\n\nWhether sending audience members or events with [`UserData`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#userdata), include as many\n`user_identifiers` as possible, including sending multiple identifiers of the\nsame type.\n\nFor example, if you have multiple email addresses for a user, include a separate\n[`UserIdentifier`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#useridentifier) for each email address. Similarly, if you have identifiers of\ndifferent types for a user, such as email addresses, phone numbers, and\naddresses, add a separate `UserIdentifier` for each identifier, up to the\n[maximum identifier count](/data-manager/api/limits#request_limits).\n\nOptimize requests\n-----------------\n\nTo reduce the likelihood of exceeding daily request limits, batch as many\nitems as possible in each request, up to the [per-request\nlimits](/data-manager/api/limits#request_limits).\n\nFor example, if you want to add 10,000 audience members to an audience, add all\n10,000 members in the `audience_members` list in one\n[`IngestAudienceMembersRequest`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestaudiencemembersrequest). Batching all 10,000 members\nin a single request is far more efficient than sending a separate request to add\neach audience member.\n\nSend concurrent requests\n------------------------\n\nTo reduce the overall time required to ingest data, send concurrent requests\nto the [`IngestionService`](/data-manager/api/reference/rpc/google.ads.datamanager.v1#ingestionservice). We recommend sending up to 10\nrequests concurrently to reduce the likelihood of exceeding the [requests per\nminute limit](/data-manager/api/limits#project_limits).\n\nYou can send concurrent requests even if the requests have the same\n`destinations`."]]