- 对于可以上传的内容,是否存在任何限制?
上传转化数据时,要注意以下限制:
- 单个
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 值、用户标识符和转化日期,则使用序数确定采用以下哪种处理方式:
- 这些转化是重复的,只能保留一个。如果所有转化的序数值相同,就会出现这种情况。
- 逐个处理这些转化,保留所有转化。如果所有转化的序数值各异,则会出现这种情况。
值本身不需要有意义。一般来说,对所有转化使用固定值(例如
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
是从未正确通过 Campaign Manager 360 的 Floodlight 调用中收集的,就可能会出现这种情况(请确保您的 Floodlight 调用(包括matchId
代码参数)正常运行)。 - 与
matchId
关联的 Floodlight 调用不包含 Cookie。Floodlight 调用必须包含 Cookie / 标识符,以便 Campaign Manager 360 正确存储matchId
(即用户可能已屏蔽 Cookie 或选择停用)。 - 与
matchId
相关联的泛光灯调用发生日期过于久远。您必须在包含matchId
的 Floodlight 调用后 60 天内上传线下转化数据。 - 与
matchId
相关联的 Floodlight 调用发生时间过于近期。 我们建议您将基于matchId
的转化上传延迟 2 小时,以确保matchId
已处理完毕且可用于匹配。
- Campaign Manager 360 无法识别
- 报告中是否包含创建 Floodlight 活动之前的时间戳的线下转化?
如果上传的时间戳早于 Floodlight 活动创建时间的线下转化,系统可能会将其报告为 Floodlight 展示次数和未归因/归因转化,最早可回溯到提交时间前 28 天。不过,我们无法保证系统会自动删除重复的数据,因此请勿依赖于此行为。最佳做法是在线下转化的最早时间戳之前创建 Floodlight 活动。
- 若要使用线下转化插入功能创建受众群体名单,需要征得哪些用户意见?
除了征得用户同意使用其广告数据外,您还必须将
nonPersonalizedAd
字段明确设置为false
,才能创建受众群体名单。
常见问题解答
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-31。
[null,null,["最后更新时间 (UTC):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."]]