What if I insert the same conversion to both Campaign Manager 360 and Search Ads 360?
If you insert the same conversion to both Campaign Manager 360 and Search Ads
360, the entries will not be deduplicated. Please use separate Floodlight
activities in this case.
What is an ordinal value and how is it used?
Ordinal values control how duplicate conversions are processed. If multiple
conversions are inserted with the same Floodlight values, user identifier, and
conversion date, the ordinal is used to determine whether:
The conversions are deduplicated and only one survives. This happens if
all conversions have the same ordinal value.
The conversions are processed individually and all survive. This happens
if all conversions have a different ordinal value.
The values themselves don't need to be meaningful. In general, using a fixed
value (such as 1) for all conversions will enable deduplication.
Using a random or unique value for each conversion will disable it.
What does it mean when a mobileDeviceId upload fails due to a NOT_FOUND error?
The most common causes of this error are:
The mobileDeviceId is invalid.
The mobileDeviceId is unknown to Search Ads 360. This means that the
device has yet to be served an ad by Campaign Manager 360.
What does it mean when a gclid upload fails due to a NOT_FOUND error?
The most common causes of this error are:
The gclid is invalid.
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.
The click associated with the gclid occurred too far in the past.
Conversions may only be inserted for clicks up to 60 days old.
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.
What does it mean when a dclid upload fails due to a NOT_FOUND error?
The most common causes of this error are:
The dclid is invalid.
The click associated with the dclid occurred too far in the past.
Conversions may only be inserted for clicks up to 60 days old.
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.
What does it mean when a matchId upload fails due to a NOT_FOUND error?
The most common causes of this error are:
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).
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).
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.
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.
Are offline conversions with a timestamp prior to the creation of the Floodlight Activity included in reports?
The upload of offline conversions with a timestamp prior to the creation of
the Floodlight Activity could be reported as Floodlight impressions and as
unattributed/attributed conversions, up to 28 days prior from the time of
submission. However, this behavior is not guaranteed and shouldn't be relied
upon. The best practice is to create Floodlight Activities before the earliest
timestamp of an offline conversion.
What consent is necessary to use Offline Conversion Insertion for audience list creation?
In addition to ad user data consent, the nonPersonalizedAd field must be
explicitly set to false to enable audience list creation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\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."]]
