排查客户名单问题
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本指南可帮助您排查目标客户匹配集成中可能出现的匹配率偏低问题和常见错误。
验证匹配率
请确保上传作业已完成,然后再尝试验证匹配率。
匹配率可能因多种原因而低于预期,包括:
广告客户可以触达其名单中 1% 到 99% 的用户,具体取决于这些用户在 Google 搜索、Gmail 或 YouTube 上的活跃程度。如需获取有关排查低匹配率问题的更详细指南,请访问帮助中心。
匹配率与名单规模之间的区别
请注意,名单规模和匹配率反映的是不同的值。匹配率会统计所有拥有 Google 账号的用户,即使实际上无法通过目标客户匹配名单触达这些用户。名单规模统计的是与 Google 账号匹配且能够通过广告个性化功能覆盖的活跃用户数。
调试常见错误
其他问题排查支持
如果您仍遇到问题,请通过目标客户匹配问题排查工具与我们联系。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-27。
[null,null,["最后更新时间 (UTC):2025-08-27。"],[[["\u003cp\u003eThis guide helps you troubleshoot low Customer Match rates and debug common errors during integration.\u003c/p\u003e\n"],["\u003cp\u003eLow match rates can stem from data formatting issues, hashing problems, or comparing against different systems.\u003c/p\u003e\n"],["\u003cp\u003eMatch rate and list size differ: match rate includes all matched Google Accounts, while list size only includes active, reachable users.\u003c/p\u003e\n"],["\u003cp\u003eCommon errors like permission issues, conflicting operations, and exceeding user identifier limits are addressed with solutions.\u003c/p\u003e\n"],["\u003cp\u003eFor persistent issues, consult the Customer Match troubleshooter or Help Center for detailed guidance.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot customer list issues\n\nUse this guide to help you troubleshoot low match rates and common errors that\nmight come up in your Customer Match integration.\n\nValidate match rate\n-------------------\n\nEnsure that your upload job has completed before attempting to validate your\nmatch rate.\n\nYour match rate might be lower than expected for a number of reasons, including:\n\n- The data was not hashed before it was uploaded.\n\n- The data was not correctly formatted before it was hashed.\n\n- You are comparing against match rates in a different system.\n\n- You are trying to add multiple user identifiers to a single `UserIdentifier`\n object. Instead, add multiple `UserIdentifier`s to a single `UserData`\n object as shown in this\n [code example](/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started#code_example).\n\nIt's possible for an advertiser to reach anywhere from 1% to 99% of their list,\nbased on how active their users are on Google Search, Gmail, or YouTube. For a\nmore detailed guide on troubleshooting low match rates, visit the [Help\nCenter](//support.google.com/google-ads/answer/7474166).\n\n### Differences between match rate and list size\n\nNote that list size and match rate reflect different values. Match rate\ncounts all users with a Google Account even if they are not actually able to be\nreached with the Customer Match list. List size counts\n[active](//support.google.com/google-ads/answer/7474166?#zippy=%2Ctroubleshoot-low-traffic)\nusers that matched a Google Account and are able to be reached by Ads\npersonalization.\n\nDebug common errors\n-------------------\n\n| Error ||\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [`USER_PERMISSION_DENIED`](/google-ads/api/reference/rpc/v21/AuthorizationErrorEnum.AuthorizationError#user_permission_denied) | You might run into permissions errors if you attempt to modify a list that was created by another account. You can only edit a list that your own account created. |\n| [`EXTERNAL_UPDATE_ID_ALREADY_EXISTS`](/google-ads/api/reference/rpc/v21/OfflineUserDataJobErrorEnum.OfflineUserDataJobError#external_update_id_already_exists) | This error can occur if you attempt to create multiple jobs with the same [`external_id`](/google-ads/api/reference/rpc/v21/OfflineUserDataJob#external_id). |\n| [`CONFLICTING_OPERATION`](/google-ads/api/reference/rpc/v21/OfflineUserDataJobErrorEnum.OfflineUserDataJobError#conflicting_operation) | This error can occur if `remove` operations are mixed with `create` operations in a single job. |\n| [`TOO_MANY_USER_IDENTIFIERS`](/google-ads/api/reference/rpc/v21/OfflineUserDataJobErrorEnum.OfflineUserDataJobError#too_many_user_identifiers) | The `create` operations in a single job contain more than 100,000 `user_identifiers` in total. Split the request into multiple requests that don't exceed that limit. |\n| [`CONCURRENT_MODIFICATION`](/google-ads/api/reference/rpc/v21/DatabaseErrorEnum.DatabaseError#concurrent_modification) | This error can occur if you try to operate on the same list at the same time. |\n| [`RESOURCE_EXHAUSTED`](/google-ads/api/reference/rpc/v21/QuotaErrorEnum.QuotaError#resource_exhausted) | This error can occur if you try to send too many requests. You can mitigate this by batching your operations as per the recommended [usage flow](/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started#usage-flow). You can also refer to the best practices guide for [API limits and quotas](/google-ads/api/docs/best-practices/quotas). |\n\nAdditional troubleshooting support\n----------------------------------\n\nIf you're still having issues, reach out to us through the Customer Match\n[troubleshooter](//support.google.com/google-ads/troubleshooter/10028577)."]]