常見問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
- 上傳內容是否有任何限制？
請注意以下幾項限制：
- 個別
batchinsert 和 batchupdate 要求的上限為 1,000 個轉換。
- 轉換時間戳記最長可回溯至提交時間的 28 天前。
- 您只能將轉換提交至 Campaign Manager 360 使用者設定檔有存取權的 Floodlight 設定。
- 我該使用 Campaign Manager 360 還是 Search Ads 360 上傳轉換資料？
如要進一步比較兩項產品提供的功能，請前往 Search Ads 360 說明中心。
- 如果我同時在 Campaign Manager 360 和 Search Ads 360 中插入相同的轉換，會發生什麼情況？
如果您在 Campaign Manager 360 和 Search Ads 360 中插入相同的轉換，系統不會去除重複的項目。在這種情況下，請使用單獨的 Floodlight 活動。
- 什麼是序數值？如何使用？
序數值會控制重複轉換的處理方式。如果插入的轉換有相同的 Floodlight 值、使用者 ID 和轉換日期，系統會使用序數判斷下列情況：
- 系統會去除重複的轉換，只保留一個。如果所有轉換都具有相同序數值，就會發生這種情況。
- 轉換會個別處理，且全部都會保留。如果所有轉換的序數值不同，就會發生這種情況。
值本身不必有意義。一般來說，如果所有轉換都使用固定值 (例如 1)，系統就會啟用去重功能。為每次轉換使用隨機或不重複的值會停用該轉換。
- 如果
mobileDeviceId 上傳作業因 NOT_FOUND 錯誤而失敗，代表什麼意思？
這項錯誤最常見的原因包括：
mobileDeviceId 無效。- Search Ads 360 無法辨識
mobileDeviceId。這表示裝置尚未收到 Campaign Manager 360 放送的廣告。
- 如果
gclid 上傳作業因 NOT_FOUND 錯誤而失敗，代表什麼意思？
這項錯誤最常見的原因包括：
gclid 無效。gclid 與 Search Ads 360 廣告活動或 Display & Video 360 YouTube 委刊項無關。如果 gclid 是從未經過 Search Ads 360 (例如點選位置擴充功能) 的 Google Ads 點擊重新導向收集，或是從未與 Display & Video 360 YouTube 委刊項相關聯的 YouTube 廣告點擊重新導向收集，就可能會發生這種情況。- 與
gclid 相關的點擊發生時間過於久遠。轉換只能插入 60 天內的點擊。
- 與
gclid 相關的點擊發生時間太近。建議您將以 gclid 為基礎的轉換上傳作業延遲 1 小時，確保 gclid 已處理並可供比對。
- 如果
dclid 上傳作業因 NOT_FOUND 錯誤而失敗，代表什麼意思？
這項錯誤最常見的原因包括：
dclid 無效。- 與
dclid 相關的點擊發生時間過於久遠。轉換只能插入 60 天內的點擊。
- 與
dclid 相關的點擊發生時間太近。建議您將以 dclid 為基礎的轉換上傳作業延遲 1 小時，確保 dclid 已處理並可供比對。
- 如果
matchId 上傳作業因 NOT_FOUND 錯誤而失敗，代表什麼意思？
這項錯誤最常見的原因包括：
- Campaign Manager 360 無法識別
matchId。如果 matchId 是從 Floodlight 呼叫收集，但未正確傳送至 Campaign Manager 360 (請確認 Floodlight 呼叫 (包括 matchId 代碼參數) 運作正常)，就可能發生這種情況。
- 與
matchId 相關聯的 Floodlight 呼叫未包含 Cookie。Floodlight 呼叫必須包含 Cookie / ID，才能讓 Campaign Manager 360 正確儲存 matchId (也就是使用者可能已封鎖 Cookie 或選擇停用)。
- 與
matchId 相關聯的 Floodligh 呼叫發生在太久以前。離線轉換上傳作業必須在包含 matchId 的 Floodlight 通話後的 60 天內完成。
- 與
matchId 相關聯的 Floodlight 呼叫發生時間過於近期。建議您將以 matchId 為基礎的轉換上傳作業延遲 2 小時，確保 matchId 已處理並可供比對。
- 報表中是否包含建立 Floodlight 活動之前的離線轉換？
上傳的離線轉換資料如果含有時間戳記，且是在建立 Floodlight 活動之前，最多可回報為 Floodlight 曝光和未歸因/歸因轉換，回溯至提交時間前 28 天。不過，我們無法保證這項行為，因此不建議您依賴這項行為。最佳做法是在離線轉換最早的時間戳記之前建立 Floodlight 活動。
- 使用離線轉換插入功能建立目標對象名單時，需要取得哪些同意聲明？
除了廣告使用者資料同意聲明外，您還必須明確將 nonPersonalizedAd 欄位設為 false，才能建立目標對象名單。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-31 (世界標準時間)。
[null,null,["上次更新時間：2025-08-31 (世界標準時間)。"],[[["\u003cp\u003eConversion uploads are restricted by quantity (1,000 per request), recency (28 days old maximum), and user profile access.\u003c/p\u003e\n"],["\u003cp\u003eDuplicate conversions can be controlled using ordinal values; identical values deduplicate, while unique values allow all conversions.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eNOT_FOUND\u003c/code\u003e errors for identifiers (\u003ccode\u003emobileDeviceId\u003c/code\u003e, \u003ccode\u003egclid\u003c/code\u003e, \u003ccode\u003ematchId\u003c/code\u003e) often indicate invalid IDs, unknown IDs to the system, or timing issues.\u003c/p\u003e\n"],["\u003cp\u003eAlthough conversions with timestamps before a Floodlight Activity's creation might be reported, it's best to create the activity beforehand for reliable reporting.\u003c/p\u003e\n"]]],[],null,["# Frequently asked questions\n\nAre there any restrictions on what I can upload?\n\n: There are a few restrictions to be aware of:\n\n - Individual `batchinsert` and `batchupdate` requests are limited to 1,000 conversions.\n - The timestamp of a conversion can be **at most** 28 days old from the time of submission.\n - You can only submit conversions to a Floodlight configuration to which your Campaign Manager 360 user profile has access.\n\nShould I use Campaign Manager 360 or Search Ads 360 to upload conversions?\n\n: Refer to the [Search Ads 360 help center](//support.google.com/searchads/answer/7384231) for a detailed\n comparison of features offered by both products.\n\nWhat if I insert the same conversion to both Campaign Manager 360 and Search Ads 360?\n\n: If you insert the same conversion to both Campaign Manager 360 and Search Ads\n 360, the entries will not be deduplicated. Please use separate Floodlight\n activities in this case.\n\nWhat is an ordinal value and how is it used?\n\n: Ordinal values control how duplicate conversions are processed. If multiple\n conversions are inserted with the same Floodlight values, user identifier, and\n conversion date, the ordinal is used to determine whether:\n\n - The conversions are deduplicated and only one survives. This happens if all conversions have the **same** ordinal value.\n - The conversions are processed individually and all survive. This happens if all conversions have a **different** ordinal value.\n\n The values themselves don't need to be meaningful. In general, using a fixed\n value (such as `1`) for all conversions will enable deduplication.\n Using a random or unique value for each conversion will disable it.\n\nWhat does it mean when a `mobileDeviceId` upload fails due to a `NOT_FOUND` error?\n\n: The most common causes of this error are:\n\n - The `mobileDeviceId` is invalid.\n - The `mobileDeviceId` is unknown to Search Ads 360. This means that the device has yet to be served an ad by Campaign Manager 360.\n\nWhat does it mean when a `gclid` upload fails due to a `NOT_FOUND` error?\n\n: The most common causes of this error are:\n\n - The `gclid` is invalid.\n - The `gclid` is not associated with a Search Ads 360 campaign or a Display \\& Video 360 YouTube line item. This may occur if the `gclid` was collected from a Google Ads click redirect which did not pass through Search Ads 360 (e.g., clicks on location extensions) or collected from a YouTube ad click redirect not associated with a Display \\& Video 360 YouTube line item.\n - The click associated with the `gclid` occurred too far in the past. Conversions may only be inserted for clicks up to 60 days old.\n - The click associated with the `gclid` occurred too recently. We recommend delaying `gclid`-based conversion uploads by 1 hour to ensure that the `gclid` is processed and available for matching.\n\nWhat does it mean when a `dclid` upload fails due to a `NOT_FOUND` error?\n\n: The most common causes of this error are:\n\n - The `dclid` is invalid.\n - The click associated with the `dclid` occurred too far in the past. Conversions may only be inserted for clicks up to 60 days old.\n - The click associated with the `dclid` occurred too recently. We recommend delaying `dclid`-based conversion uploads by 1 hour to ensure that the `dclid` is processed and available for matching.\n\nWhat does it mean when a `matchId` upload fails due to a `NOT_FOUND` error?\n\n: The most common causes of this error are:\n\n - The `matchId` is unknown to Campaign Manager 360. This may occur if the `matchId` was collected from a Floodlight call which did not properly pass through Campaign Manager 360 (make sure your Floodlight calls are working correctly including the `matchId` tag parameter).\n - The Floodlight call associated with the `matchId` didn't contain a cookie. The Floodlight call must contain a cookie / identifier for Campaign Manager 360 to store the `matchId` correctly (ie. user may have blocked cookies or opted out).\n - The Floodligh call associated with the `matchId` occurred too far in the past. Offline Conversion uploads must be made within 60 days of the Floodlight call containing the `matchId`.\n - The Floodlight call associated with the `matchId` occurred too recently. We recommend delaying `matchId`-based conversion uploads by 2 hours to ensure that the `matchId` is processed and available for matching.\n\nAre offline conversions with a timestamp prior to the creation of the Floodlight Activity included in reports?\n\n: The upload of offline conversions with a timestamp prior to the creation of\n the Floodlight Activity could be reported as Floodlight impressions and as\n unattributed/attributed conversions, up to 28 days prior from the time of\n submission. However, this behavior is not guaranteed and shouldn't be relied\n upon. The best practice is to create Floodlight Activities before the earliest\n timestamp of an offline conversion.\n\nWhat consent is necessary to use Offline Conversion Insertion for audience list creation?\n\n: In addition to ad user data consent, the `nonPersonalizedAd` field must be\n explicitly set to `false` to enable audience list creation."]]
