Troubleshoot catalogs
Catalog errors prevent products from being shown in ads, while warnings may affect product information or performance. Rokt recommends checking your catalogs regularly to make sure they contain accurate, up-to-date products.
Resolve as many issues as you can to maximize the products available to serve. After making a change, upload a new file or use Fetch now.
View overall catalog healthLien direct vers View overall catalog health
In the Catalog Manager, your catalogs list shows:
- Catalog health: whether the catalog is ready for ads or needs attention.
- Product counts: total products, and how many have issues.
- Last updated: when the catalog was most recently updated.
Select a row to open the catalog's details.
See your sourcesLien direct vers See your sources
The Sources tab lists every source on the catalog with its status, last run, next scheduled run, and last successful run. This distinguishes a source that has not run yet from one that ran and failed.
See run historyLien direct vers See run history
The data source details show the outcome of each upload or fetch.
| Status | Description |
|---|---|
| Complete | The run finished successfully. No further action is required. |
| Complete with errors | The run finished, but at least one product was not ingested. Those products do not serve until the errors are fixed. |
| Failed | The run did not finish, so no changes were applied. Products from your last successful run keep serving. A new catalog has no products until a run completes. |
| Processing | The run is still in progress. Check again shortly. |
Choose a run to see the number of changes and a report breaking down rows read, products created and updated, and every issue detected. The report can be downloaded.
When a fetch failsLien direct vers When a fetch fails
A fetch can fail in ways a file upload cannot. The run names the cause:
- Address could not be resolved: check the hostname.
- Secure connection failed: check the certificate on the host.
- File not found: the URL returned a 404. Check the path and file name.
- Credentials rejected: update the username and password in the source settings.
- Timed out: the host did not respond in time.
- File too large: the file exceeded the size limit for a single run.
- Unexpected file type: the URL returned something other than a CSV.
Find product issuesLien direct vers Find product issues
Open the Products tab to see your products.
- Sort and filter: search for a product, or filter to only products that need attention.
- See product details: select a product's row to open its information.
- View issues: where there is a problem, an issue status appears. Select it to see the field and value that caused each issue.
See Common catalog issues for what each one means and how to fix it.
When a product is in your catalog but not servingLien direct vers When a product is in your catalog but not serving
Not every reason is a feed problem. Before changing your feed, check:
- The product is not in a product set that a live campaign is using.
- The product is out of stock, or its availability value says so.
- The product has no category. It is held until a category is set or suggested.
- A partner has excluded it. Partners control what appears on their own confirmation pages and can keep categories or individual products off them.