Google 近期為 Google Ads 應用程式轉換追蹤和再行銷推出了全新的 API。開發這項新版 API 的主要動機，是為了簡化廣告主的應用程式數據分析和歸因工作，並提升 Google Ads 歸因合作夥伴的可靠性。
從現在起，我們將簡稱為「API」。
概念
如果您熟悉舊版 API，可能會發現新版 API 導入了幾項新概念。
應用程式事件
舊版轉換追蹤 API 著重於「轉換 ID」和「轉換標籤」，而 API 則著重於一般意義的「應用程式事件」。在舊版 API 整合中，應用程式事件與 Google Ads 應用程式轉換事件之間的語法對應，是由第三方數據分析系統透過各自的設定面板處理。因此，舊版整合功能需要在 Google Ads 中產生「轉換 ID」和「轉換標籤」，然後在第三方系統中進行對應。
不過，消費者可透過 API，以名稱將應用程式事件以不可分割的方式轉送至 Google Ads。廣告主可藉此開始從外部追蹤轉換，不必在 Google Ads 中進行額外設定。
開發人員權杖：
API 的所有消費者都需要產生開發人員權杖。開發人員權杖的用途是限制及控管 API 存取權，這個權杖會做為靜態共用密鑰。無論是代表哪個應用程式建立要求，API 消費者一律會使用相同的開發人員權杖，簽署所有應用程式轉換追蹤和再行銷要求。填寫權杖申請表時，請務必指出權杖將用於 App conversions and remarketing API。請注意，您必須點選「申請基本存取權」，才能完成開發人員權杖申請程序。您可以在 Google Ads 的 Google Ads API 中心查看目前的存取層級。此外，如果您使用 Google Ads API 執行其他報表或廣告活動管理功能，則必須建立專用的管理員帳戶和開發人員權杖，才能搭配使用這項 API。
如果您是第三方供應商，代表使用您服務的廣告主發送的所有請求，都應附上您的開發人員權杖。請勿要求每個客戶申請自己的開發人員權杖。每個客戶都應使用供應商 ID 建立連結 ID (請參閱下方的章節)，然後將連結 ID 提供給您。
連結 ID
連結 ID 是專屬 ID，用於將特定應用程式繫結至特定開發人員權杖。這裡的「特定應用程式」是指單一平台上的單一應用程式 (例如 iOS 上的 App123)。連結 ID 可在 Google Ads 帳戶之間產生及共用，不受Google Ads 帳戶管理階層限制，完全免除管理同一應用程式多個追蹤 ID 的需求。
如要建立與專屬開發人員權杖相關聯的連結 ID，請從「應用程式分析供應商」下拉式選單中選取「其他供應商」。在標示為「輸入供應商 ID」的輸入框中，輸入與您申請開發人員權杖的 Google Ads 管理員帳戶相關聯的外部客戶 ID。輸入 ID，
不要加上破折號 (例如 (如果 Google Ads 使用者介面顯示的帳戶 ID 為 123-456-7890，請輸入 1234567890)。
跨聯播網歸因
在應用程式歸因領域，跨聯播網重複資料刪除是許多產品的核心功能。API 會要求 API 消費者在收到 Google Ads 的轉換確認後，傳送額外的「跨聯播網歸因」要求，將跨聯播網去重複的概念帶入 Google Ads。跨聯播網要求的目的是通知 Google Ads，API 消費者收到轉換確認後，是否將其計為轉換。
[null,null,["上次更新時間：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."]]
