If you’re experiencing errors after uploading your store sales data, review the steps below for error messages and the recommended next steps to fix the issue. Keep in mind that this isn’t an exhaustive list of error messages. You may get additional errors.
- Ensure that you’re using the correct template to upload store sales data and that it contains all of the required rows and columns. To download the store sales upload templates, refer to Store sales uploads: Format and hash your data.
- Ensure that the parameters and headers are in English as per the default template. The rest of the submitted data may be in any language, but the parameters and headers must remain in English.
- If you’re creating and uploading in a CSV format, open and review the parameter and header rows in a basic text editor to ensure no unexpected characters were added. For example, ensure that:
- There are no quotation marks (") surrounding the Parameters row.
- Different parameter values are separated by a single semicolon (;).
- Header columns are comma-separated (,) with a single comma.
- Ensure that the following columns are present in the file: Conversion Name, Conversion Time, Conversion Value, and Conversion Currency.
- You must also include at least one user identifier, such as Email, Phone Number, or Address (First Name, Last Name, City, State, Zip, and Country).
- If you’re uploading a CSV file and choose to hash the data yourself, review Store sales uploads: Format and hash your data.
This error indicates that there’s a potential issue with the parameter or header formatting for your store sales upload. Review the following if you encounter this error:
- Ensure that you’re using the correct template to upload store sales data and that it contains all of the required rows and columns. To download the store sales upload templates, refer to Store sales uploads: Format and hash your data.
- Ensure that the parameters and headers are in English as per the default template. The rest of the submitted data may be in any language, but the parameters and headers must remain in English.
- If you’re creating and uploading in a CSV format, open and review the parameter and header rows in a basic text editor to ensure no unexpected characters were added. For example, ensure that:
- There are no quotation marks (") surrounding the Parameters row.
- Different parameter values are separated by a single semicolon (;).
- Header columns are comma-separated (,) with a single comma.
- Ensure that the following columns are present in the file: Conversion Name, Conversion Time, Conversion Value, and Conversion Currency.
- You must also include at least one user identifier such as Email, Phone Number, or Address (First Name, Last Name, City, State, Zip, and Country).
- If you’re uploading a CSV file and choose to hash the data yourself, review Store sales uploads: Format and hash your data.
This error indicates that the upload couldn’t be completed due to taking too much time or a network interruption. Review the following steps to try and improve this:
- Review your file and ensure that it meets the upload file size requirements listed in Store sales uploads: Format and hash your data.
- If your file is near or over the limit, try splitting the file into separate smaller files.
- If you’re uploading multiple files, try uploading one file at a time.
- If the file size is within the limits, try uploading the file at a later time or from a different network connection.
This error indicates that the system was unable to find or access, the file at the requested location.
Review your upload settings and verify that your SFTP URL, name, and/or password are correct.
This error indicates that the transaction upload has a significantly higher or lower average transaction value compared with the account’s 90-day historical average. Such uploads are initially blocked in order to prevent potentially incorrect data from being ingested which could result in reporting errors. If you receive this error when uploading, follow the below steps:
- Review the intended transaction upload file and confirm that the provided transaction values are correct and the upload average is aligned with your expectations.
- If there‘re any errors in the file values, correct them and try to upload again.
- You can review the average order value for the last 90 days within your Google Ads account.
- If the file contents and transaction values are correct and intended, reach out to your Google Ads account management team or Google Ads support to request an exemption to allow the file to be processed.
- Note that the validation exemption for these errors can only be reprocessed if the upload attempt happened within the last 25 days.
This error indicates that the currency code within the upload data doesn't match the historic values within the account. Such uploads are initially blocked in order to prevent potentially incorrect data from being ingested which could result in reporting errors. If you receive this error when uploading, follow the below steps:
- Review the intended transaction upload file and confirm that the provided currency code values are correct and aligned with your expectations.
- If there’re any errors in the currency code values, correct them and try to upload again.
- If the file contents and currency code values are correct and intended, reach out to your Google Ads account management team or Google Ads support to request an exemption to allow the file to be processed.
- Note that the validation exemption for this can only be reprocessed if the upload attempt happened within the last 25 days.
Insufficient matched transactions
This error indicates that the uploaded data didn’t have sufficient new transactions that Google was able to match to. If you receive this error during an upload, follow the below steps:
- Review the upload file and make sure that the volume of uploaded transactions is sufficient. The ideal upload should have at least 30,000 transactions per month.
- Ensure that your upload doesn’t include duplicate transactions.
- If the volume is too low, try uploading additional new eligible transactions.
- Review the format for the provided data to ensure it’s correct.
- Ensure that any user personally identifiable information (PII) is properly hashed where applicable. Also, check that all other fields are provided and formatted correctly.
- Ensure that any provided transactions are from the last 90 days.
- Any transactions older than 90 days won’t be processed.
