應用程式轉換歸因的資料不一致
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
無法避免的差異
由於多種無法避免的因素，Google Ads 記錄到的安裝次數和應用程式內轉換次數，與第三方報表記錄到的次數之間，會出現合理程度的差異。
- 使用第三方追蹤多個聯播網時，系統會跨聯播網將轉換資料去重複。
- Google Ads 會根據廣告互動 (例如點擊、曝光等) 發生日期記錄轉換，而不是轉換事件發生日期。
- Google Play 追蹤的 Android 安裝轉換資料會計算應用程式安裝次數，而第三方安裝資料則會計算應用程式初次開啟次數。
- 請注意，如果是 iOS 應用程式，由於部分轉換是由 Google Ads 模擬，因此來自搜尋聯播網的轉換不會顯示在第三方資訊主頁。詳情請參閱 Google Ads 說明中心。
- 報表可能有時區差異。Google 會使用廣告主帳戶中設定的當地時間。
- Google Ads 會收到第三方傳送的轉換信號，但轉換資料可能需要數小時 (有時最多 24 小時) 才會處理完畢，並顯示在 Google Ads 轉換報表中。
- Google Ads 會將 Android 安裝和重新安裝 (由解除安裝的使用者執行) 追蹤為安裝轉換，但並非所有第三方都會追蹤 Android 重新安裝。
- 如果 Google Ads 轉換設定為計算「每次」轉換，追蹤到的轉換次數會比第三方報表多，因為許多第三方只會計算「一次」轉換。進一步瞭解 Google Ads 轉換計數設定。
- Google Ads 和第三方設定的轉換回溯期可能不同。根據預設，Google Ads 會追蹤廣告互動後 30 天內的初次開啟或安裝轉換，以及廣告互動後 90 天內的應用程式內轉換。
找出差異
找出 Google Ads 安裝次數和應用程式內轉換次數與第三方追蹤次數之間的差異時，請務必考量歸因方法上的差異。
由於 Google Ads 是根據廣告互動的發生日期記錄轉換，而大多數第三方是根據轉換事件的發生日期記錄轉換，因此建議您比較特定時間範圍內的轉換次數和廣告點擊次數。
範例
- 在 Google Ads 中，查看特定日期範圍內的轉換次數，例如從 1 月 1 日起算的 7 天。
- 在第三方中，查看歸因於設定日期範圍內廣告點擊的轉換次數 (例如，從 1 月 1 日開始的 7 天內點擊次數)，但擷取轉換資料時，請從設定日期範圍的第一天 (1 月 1 日) 開始，並延長時間範圍，以配合 Google Ads 轉換回溯期 (30 天的轉換回溯期會導致系統評估 1 月 1 日至 1 月 31 日的轉換資料)。
排解差異問題
除了上述預期會出現的差異外，還有其他因素可能導致 Google Ads 安裝次數和應用程式內轉換次數，與第三方追蹤的次數有所出入。如要進一步排解這些差異，請按照下列步驟操作：
- 確認事件已匯入相關的 Google Ads 帳戶。
- 確認所有事件都已傳送給 Google，以利 Google Ads 歸因。
- 確認第三方資訊主頁中的歸因回溯期，與 Google Ads 中設定的轉換回溯期一致。
- 確認 Google Ads 帳戶已啟用自動標記。
- 確認所有事件都已傳遞正確的開發人員權杖和連結 ID。
- 確認正確的連結 ID 已分享給相關帳戶。
- 如要查看 Android 裝置上的重新安裝百分比，請前往 Google Play 管理中心。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-26 (世界標準時間)。
[null,null,["上次更新時間：2025-07-26 (世界標準時間)。"],[[["\u003cp\u003eDiscrepancies between Google Ads and third-party conversion data are expected due to differences in attribution methodologies, including how conversions are deduplicated and attributed across networks.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Ads attributes conversions based on the day of the ad interaction, while most third parties attribute them based on the day of the conversion event, leading to reporting differences.\u003c/p\u003e\n"],["\u003cp\u003eTime zone differences, conversion processing times, and variations in conversion counting methods (e.g., "Every" vs. "One") can also contribute to discrepancies.\u003c/p\u003e\n"],["\u003cp\u003eWhen troubleshooting discrepancies, ensure that events are correctly imported, passed to Google Ads with the correct parameters, and that attribution settings (lookback windows, auto-tagging) are aligned between platforms.\u003c/p\u003e\n"],["\u003cp\u003eConsider factors such as re-installs on Android, which Google Ads tracks but not all third parties do, and modeled conversions for iOS apps from the search network, which are not surfaced on third-party dashboards.\u003c/p\u003e\n"]]],[],null,["# Discrepancies in App Conversion Attribution\n\nUnavoidable discrepancies\n-------------------------\n\nThere are several unavoidable factors that result in reasonable levels of\ndiscrepancies between the number of install and in-app conversions reported in\nGoogle Ads compared with those reported by a third party.\n\n- When tracking more than one network with a third party, conversion data will be deduplicated across networks.\n- Google Ads reports conversions by the day of the ad interaction (for example: click, impression, etc.), not the day of the conversion event.\n- Android install conversion data tracked from Google Play measures the number of app installs, whereas third-party install data measures the number of times the app is first opened.\n- For iOS apps, note that conversions coming from the search network will not be surfaced on third-party dashboards since some of these conversions are modeled by Google Ads. Visit our [Google Ads Help\n Center](//support.google.com/google-ads/answer/6100665) to learn more.\n- There might be time zone differences in reporting. Google uses the local time as set in the advertiser's account.\n- Google Ads receives conversion pings from third-parties, but it can take several hours (sometimes up to 24 hours) for the conversion data to be processed and shown in Google Ads conversion reporting.\n- Google Ads tracks Android installs and re-installs (by uninstalled users) as install conversions, but not all third parties track Android re-installs.\n- Google Ads conversions set to count \"Every\" conversion will track more conversions than third-party reports, as many third parties count only \"One\" conversion. Read more about the [Google Ads conversion count\n setting](//support.google.com/adwords/answer/3438531).\n- The conversion lookback window might be set differently between Google Ads and the third party. By default, Google Ads tracks first open or install conversions within 30 days of the ad interaction, and in-app conversions within 90 days of the ad interaction.\n\nIdentifying discrepancies\n-------------------------\n\nWhen identifying discrepancies between Google Ads install and in-app conversion\nnumbers versus those tracked by a third party, it is important to consider the\ndifference in attribution methodology.\n\nSince Google Ads reports conversions by the day of the ad interaction and the\nmajority of third parties report conversions based on the day of the conversion\nevent, it is recommended to compare conversion numbers with ad clicks from a\nspecific time frame.\n\n#### Example\n\n- In Google Ads, view conversion numbers within a specific date range, for example, 7 days starting on January 1st.\n- In the third party, view conversion numbers attributed to ad clicks from the set date range (for example, clicks for 7 days starting on January 1st), but when pulling conversion data start on day 1 of the set date range (January 1st) and extend the time frame to accommodate the Google Ads conversion window (a 30-day conversion window would result in evaluation of conversion data from January 1st to January 31st).\n\nTroubleshooting discrepancies\n-----------------------------\n\nThere are several factors that may impact discrepancies between Google Ads install\nand in-app conversion numbers versus those tracked by a third party, outside of\nthe expected unavoidable discrepancies listed above. Below are additional steps\nthat can be taken to troubleshoot these discrepancies:\n\n- Confirm the event has been imported into the relevant Google Ads account.\n- Confirm all events are being passed to Google for Google Ads attribution.\n- Confirm the attribution lookback window in the third-party dashboard is aligned with the conversion window set in Google Ads.\n- Ensure that [auto-tagging](//support.google.com/adwords/answer/1752125) is enabled in the Google Ads account.\n- Confirm all events are being passed with the correct [Developer\n Token](/app-conversion-tracking/api#developer_token) and [Link\n ID](/app-conversion-tracking/api#link_id).\n- Confirm the correct [Link ID](/app-conversion-tracking/api#link_id) is being shared with the relevant account.\n- For re-installs on Android, check the Google Play Developer Console to view percent of re-installs."]]
