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. |
|
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 value bucket must be a number from 1-10, except for remove operation where 0 will be accepted. |
|
Identifiers not supported for Customer Match attributes. User attributes can only be provided with contact info (email, phone, address) user identifiers. |