AI-generated Key Takeaways
-
The content provides a comprehensive list of possible errors that can occur during a request related to user data uploads and store sales.
-
Errors range from issues with user list IDs and types to invalid formats for mobile IDs and SHA256 encoded values.
-
There are specific errors related to customer allow-listing, incompatible upload key types, missing user identifiers, and exceeding the maximum number of user identifiers per request.
-
The list also includes errors concerning invalid partner IDs, encoding issues, country codes, transaction times, and conversion actions.
-
Several errors pertain to unsupported or conflicting operations, such as invalid operation order, external update ID conflicts, and limitations on remove or remove-all operations.
-
Additional errors cover issues with custom keys, customer data terms acceptance, incompatible user identifiers for attributes, and errors related to lifetime value, purchase times, and event attributes.
Enum describing possible request errors.
| Enums | |
|---|---|
|
Enum unspecified. |
|
The received error code is not known in this version. |
|
The user list ID provided for the job is invalid. |
|
Type of the user list is not applicable for the job. |
|
Customer is not allowisted for using user ID in upload data. |
|
Upload data is not compatible with the upload key type of the associated user list. |
|
The user identifier is missing valid data. |
|
The mobile ID is malformed. |
|
Maximum number of user identifiers allowed per request is 100,000 and per operation is 20. |
|
Customer is not on the allow-list for store sales direct data. |
|
Customer is not on the allow-list for unified store sales data. |
|
The partner ID in store sales direct metadata is invalid. |
|
The data in user identifier should not be encoded. |
|
The country code is invalid. |
|
Incompatible user identifier when using third_party_user_id for store sales direct first party data or not using third_party_user_id for store sales third party data. |
|
A transaction time in the future is not allowed. |
|
The conversion_action specified in transaction_attributes is used to report conversions to a conversion action configured in Google Ads. This error indicates there is no such conversion action in the account. |
|
Mobile ID is not supported for store sales direct data. |
|
When a remove-all operation is provided, it has to be the first operation of the operation list. |
|
Mixing creation and removal of offline data in the same job is not allowed. |
|
The external update ID already exists. |
|
Once the upload job is started, new operations cannot be added. |
|
Remove operation is not allowed for store sales direct updates. |
|
Remove-all is not supported for certain offline user data job types. |
|
The SHA256 encoded value is malformed. |
|
The custom key specified is not enabled for the unified store sales upload. |
|
The custom key specified is not predefined through the Google Ads UI. |
|
The custom key specified is not set in the upload. |
|
The customer has not accepted the customer data terms in the conversion settings page. |
|
User attributes cannot be uploaded into a user list. |
|
Lifetime bucket value must be a number from 0 to 10; 0 is only accepted for remove operations |
|
Identifiers not supported for Customer Match attributes. User attributes can only be provided with contact info (email, phone, address) user identifiers. |
|
A time in the future is not allowed. |
|
Last purchase date time cannot be less than acquisition date time. |
|
Only emails are accepted as user identifiers for shopping loyalty match. {-- api.dev/not-precedent: The identifier is not limited to ids, but also include other user info eg. phone numbers.} |
|
Provided item ID is invalid. |
|
First purchase date time cannot be greater than the last purchase date time. |
|
Provided lifecycle stage is invalid. |
|
The event value of the Customer Match user attribute is invalid. |
|
All the fields are not present in the EventAttribute of the Customer Match. |
|
Consent was provided at the operation level for an OfflineUserDataJobType that expects it at the job level. The provided operation-level consent will be ignored. |