Google 最近针对 Google Ads 应用转化跟踪和再营销推出了一种全新的 API。之所以开发出这款全新的 API，主要是为了让广告客户能更轻松地进行应用分析和归因，同时也让 Google Ads 归因合作伙伴能够提供更可靠的应用分析和归因结果。
从现在起，我们直接用“API”指代用于应用转化跟踪和再营销的新版 API。
概念
对于熟悉旧版 API 的用户来说，新版 API 中会有一些新概念。
应用事件
旧版转化跟踪 API 关注的是“转化 ID”和“转化标签”，新版 API 则一般关注“应用事件”。在旧版 API 集成中，应用事件与 Google Ads 应用转化事件之间在语法上的映射关系是在第三方分析系统中通过各自的配置面板加以处理的。因此，旧版集成需要先在 Google Ads 中生成所谓的“转化 ID”和“转化标签”，然后在第三方系统中进行映射。
不过，使用者通过新版 API 可按“名称”将应用事件以原子方式转发到 Google Ads。这样一来，广告客户无需在 Google Ads 中进行额外设置就可以从外部开始跟踪转化。
开发者令牌
新版 API 的所有使用者都需要生成开发者令牌。开发者令牌的用途是限制和控制对此 API 的访问，且充当静态共享密钥。此 API 的使用者将始终使用同一开发者令牌对所有应用转化跟踪和再营销请求进行签名，无论他们是代表哪个应用创建请求，都是如此。在填写令牌申请时，请务必指明令牌将用于应用转化和再营销 API。请注意，您需要点击申请基本访问权限来完成开发者令牌申请流程。您可以通过 Google Ads 内的 Google Ads API 中心来查看您当前的访问权限级别。此外，如果您将 Google Ads API 用于其他报告或广告系列管理功能，则需要单独创建与该 API 配合使用的经理账号和开发者令牌。
如果您是第三方提供商，则代表使用您服务的广告客户发出的所有请求都应该与您的开发者令牌一起发送。切勿要求每个客户申请自己的开发者令牌。相反，每个客户都应该使用您的提供商 ID 创建一个关联 ID（请参阅下面一节），然后向您提供他们的关联 ID。
如需创建与您的唯一开发者令牌相关联的关联 ID，请从应用分析工具提供商下拉列表中选择其他提供商。在标有输入您的提供商 ID 的输入框中，输入与您申请开发者令牌所在的 Google Ads 经理账号相关联的外部客户 ID。请输入 ID（不带破折号，例如，如果账号 ID 在 Google Ads 界面中显示为 123-456-7890，则输入 1234567890）。
跨广告网络归因
跨广告联盟删除重复数据是应用归因领域很多产品的一项核心功能。新版 API 将跨广告联盟删除重复数据的概念引入了 Google Ads，要求 API 使用者在收到 Google Ads 发来的转化确认后另外发送一个“跨广告联盟归因”请求。发送此跨广告联盟请求的目的是通知 Google Ads，收到转化确认的 API 使用者是否将该转化确认计为转化。
[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eGoogle Ads introduced a new API for app conversion tracking and remarketing, simplifying analytics and attribution for advertisers and partners.\u003c/p\u003e\n"],["\u003cp\u003eThis API utilizes "app events" to track conversions, allowing advertisers to track externally without additional Google Ads setup.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers need a developer token to access the API, obtainable via application and used for all app conversion requests.\u003c/p\u003e\n"],["\u003cp\u003eA Link ID uniquely connects an app to a developer token, enabling cross-account sharing and simplifying tracking identifier management.\u003c/p\u003e\n"],["\u003cp\u003eThe API supports cross-network attribution, requiring an additional request after conversion confirmation to manage deduplication across networks.\u003c/p\u003e\n"]]],[],null,["# App Conversion Tracking and Remarketing API\n\nIntroduction\n------------\n\nGoogle recently announced an entirely new API for Google Ads app conversion\ntracking and remarketing. The primary drivers for developing this new API are\nto make app analytics and attribution **simpler for advertisers** and **more\nreliable for Google Ads attribution partners**.\n\nFrom here on out, we'll simply refer to the new API for app conversion\ntracking and remarketing as \"the API\".\n\nConcepts\n--------\n\nThe API introduces several new concepts for those who are familiar\nwith the legacy API.\n\n### App events\n\nWhere the legacy conversion tracking API is concerned with \"conversion IDs\"\nand \"conversion labels,\" the API is concerned with \"app events\" in a\ngeneric sense. In the legacy API integration, the syntactic mapping between app\nevents and Google Ads app conversion events is handled in the third-party analytics\nsystems via their respective configuration panels. The legacy integration hence\nrequires the generation of said \"conversion IDs\" and \"conversion labels\" in\nGoogle Ads followed by a mapping in the third-party system.\n\nThe API, however, allows consumers to forward app\nevents by *name*, atomically, to Google Ads. With this, advertisers can begin\ntracking conversions externally without additional required setup in Google Ads.\n\n### Developer token\n\nAll consumers of the API will need to generate a [developer\ntoken](//support.google.com/adspolicy/contact/new_token_application). The\npurpose of the developer token is to restrict and control access to the API, and\nthis token will function as a static shared secret. A consumer of the API will\nalways use the same developer token to sign all app conversion tracking and\nremarketing requests, regardless of which app they are creating a request on\nbehalf of. When filling out your application for a token, please make sure that\nyou indicate the token will be used for the **App conversions and remarketing\nAPI** . Note that you need to complete the developer token application\nprocess by clicking on **Apply for Basic Access** . You can check your current\naccess level in the Google Ads API center within Google Ads. Also, if you use the\n[Google Ads API](/google-ads/api/docs/start)\nfor other reporting or campaign management functionalities, you'll need to\ncreate a separate Manager account and developer token for use with this API.\n| **Note:** if your third-party analytics provider is an [App Attribution Partner](//ads.google.com/lp/appcampaigns/attribution/), you do not need to generate a separate developer token from the one being used by your analytics provider for this integration.\n\nIf you are a third-party provider, all requests on behalf of advertisers using\nyour service should be sent with your developer token. **Do not ask each client\nto apply for their own developer token** . Instead, each client should create a\nLink ID using your Provider ID ([see section below](#link_id)) and then provide\nyou their Link ID.\n\n### Link ID\n\nA link ID is a unique identifier for binding a specific app to a specific\ndeveloper token. Here, a \"specific app\" refers to a single app on a single\nplatform (for example, `App123` on iOS). Link IDs can be\n[generated and shared](//support.google.com/google-ads/answer/7365001)\nbetween Google Ads accounts regardless of\n[Google Ads account management hierarchy](//ads.google.com/home/tools/manager-accounts/),\nand completely eliminate the need to manage multiple tracking identifiers for\nthe same app.\n\nTo create a link ID associated with your unique developer token, select **Other\nprovider** from the **app analytics provider** dropdown. In the input box labeled\n**Enter your provider's ID** enter the external customer ID associated with the\nGoogle Ads manager account where you applied for your developer token. Enter the ID\nwithout dashes (ex. 1234567890 for an account ID shown as 123-456-7890 in the\nGoogle Ads UI).\n\n### Cross-network attribution\n\nCross-network deduplication is a core feature of many products in the app\nattribution space. The API brings the concept of cross-network\nde-duplication to Google Ads by requiring API consumers to send an additional\n\"cross-network attribution\" request after receiving a conversion confirmation\nfrom Google Ads. The purpose of the cross-network request is to notify Google Ads\nwhether or not the conversion confirmation was counted as a conversion by the\nAPI consumer who received it.\n| **Note:** You can find more details in the [Request and\n| Response Specifications](/app-conversion-tracking/api/request-response-specs) section. Additionally, please follow our [Privacy\n| Compliant App Attribution](/app-conversion-tracking/api/privacy-compliant-guide) guide to ensure clicks from users that opt out of ad tracking or ads personalization are only attributed using privacy compliant workflows."]]
