The Diagnostics section displays errors and warnings that affect items in the catalog and errors in the product feed import. This includes errors that prevent loading goods from the feed, as well as warnings about the correctness of the product information.
Viewing catalog problems
- Open the Commerce Center tab.
- Select the desired directory from the list.
- Click the Diagnostics tab.
- Problems with the catalog will be displayed on this page.
Each catalog problem can have one of the following levels of criticality:
- Errors: feed loading errors and errors in goods. Upload errors prevent successful import of product feeds (for example, if there is no feed file at the specified address). Errors in the goods prevent the item from being loaded into the catalog (for example, if the goods contain incorrect or invalid field values in the mandatory fields).
- Warnings: products with warnings will be added to the catalog, but they degrade the catalog because they contain incomplete or incorrect information about the product.
On the Diagnostics tab, all errors and warnings found are grouped by type, such as The required description field is missing or The required price field contains an empty value.
Each such group of errors and warnings displays the number of items in which the problem was found, in absolute and percentage values of the total number of items in the catalog.
For convenience of viewing, each such group of errors and warnings does not display all found items of the catalog, because there can be quite a lot of such items, which will complicate viewing.
Downloading the full report with errors
To view the full list of items with errors and warnings, download the full report.
To do this, on the Diagnostics tab, click Download Full Report.
Catalog problems filter
You can view only a certain type of errors in the catalog. To do this, select the desired option in the Diagnostics tab in the drop-down list:
- Warnings
- Errors
| Message | Recommendations |
|---|---|
| Invalid feed file URL | Make sure that the feed file URL uses only protocols allowed by the ad system and conforms to the RFC3986 standard. |
| Failed to open product page | The advertising system failed to open the pages of the first five products in the catalog due to network problems, server errors, etc. |
Failed to save image: Attempts to download product image are over | The advertising system is trying to download the product image six times consecutively. Make sure that the image at the specified address exists, that the server responds to requests, etc. |
| Invalid csv file header | Make sure the header of the CSV file has the correct name |
| Field contains a non float value | Make sure that the specified field contains a fractional value |
| There are no products in stock in the feed | Make sure that at least 3 items in the catalog are in stock |
| Response time exceeded when uploading an image | Make sure that the server hosting the image is responding to requests in a reasonable time. |
| HTTP download error | |
| Incorrect app ID format | Make sure the format of the app ID from Google Play and App Store matches the correct naming pattern. For apps from Google Play, the name must match the regular expression: ^[a-z][a-z0-9_]*(\.[a-z0-9_]+)+[0-9a-z_]$ For apps from the App Store - regular expression: ^[1-9][0-9]*$ |
| Error during TLS connection establishment | TLS connection could not be established. Probably problems with the certificate on the partner side (expired or invalid) |
| API download error | The error occurs when a marketplace sends data via API not in the format expected by the advertising system. |
| Product page domain does not match the domain of other products | Make sure that the domain in the URL field of the specified products in the catalog matches the domain of other products. In other words, all products in the catalog must have the same domain as the product page domain |
| There is no pending deep link | Make sure that the specified items have a pending deep link added to the tracking links |
| The field contains a invalid pending deep link | Ensure that the deep link URL schema conforms to the RFC3986 standard. |
| The field contains an invalid domain | Make sure that the tracking link is located on one of the supported domains (depending on the application tracker). |
| Deep link scheme does not match | Make sure the deep link URL schemes for Android and iOS are the same |
| Currency code is different from the main currency code | Make sure that the same currency codes are used in the fields for different prices (old price, minimum price, maximum price). |