> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/troubleshoot-product-catalog-errors-and-warnings.md). # Troubleshoot Product Catalog Errors & Warnings Each product catalog has a health score that indicates which, if any, problems are present in your catalog. To get your catalog into the *excellent* range, you must troubleshoot and rectify any errors, warnings, and duplicates present in it. {% embed url="" %} 1. From the left navigation menu, select ![](/files/CDnwOBeIdds9r3Z6zTnO) **\[Engage]** → **Content** → **Products** → [**Product Catalogs**](https://app.impact.com/secure/advertiser/engage/ads/productcatalogs/manage-ads-product-catalog-flow.ihtml). 2. If a catalog has any errors, warnings, or duplicate line items, you will see how many of each are present in the *Health* column.
* Upload methods that automatically fetch the catalog should automatically update when the next fetch event happens.
Health descriptions | Health indicator | Description | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Pending** | Your product catalog is being uploaded. | | **Processing** | Your product catalog is being processed. | | **Excellent** | Indicates a healthy catalog—this product data set is complete and well-structured, giving it the best chance of performing effectively. | | **Good** | Indicates that certain suggested fields that contain crucial data like category or status could be missing. Addressing these gaps will improve the overall quality of your catalog. | | **Poor** | Indicates that required information is missing in more than 10% of the records you sent in. This catalog will have to be fixed and re-uploaded. |
#### View errors & warnings 1. In the *Health* column, select the **errors**, **warnings**, or **duplicates** link. * You'll be redirected to a page with more details about the errors or warnings. Only the first item in a set of duplicates will be represented in impact.com; all items duplicating the first will be ignored. 2. Optionally, use the *Search* field and filters at the top of the page to sort through the issues.
Filter descriptions | | | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Error Type** | You can filter specifically for *Errors*, *Warnings*, *Duplicates*, or *All* issues. | | **Required** | You can filter for any specific missing required product catalog fields or *All* fields. | | **Suggested** | You can filter for any specific missing recommended product catalog fields or *All* fields. | | **Invalid** | You can filter for any specific validation-based error. This can be either a duplicate SKU, an invalid Google Category Code, or other errors. |
3. Review the issues and make changes as required. Then, re-upload your product catalog.
Common error & warning messages | Error Message | Explanation | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Record 'X': Required field(s) missing: (field name)* | The specified line is missing one or more required fields. | | *Record 'X': CatalogItemId(CatalogItemId): Required field(s) missing: (field name)* | A line in the data file is missing a required field. | | *No catalog found for the request. Check if the file name of uploaded file is the same as the one registered with the catalog* | The *Upload File Name* set in the *Upload Method* section when creating a product catalog doesn't exactly match the name of the file you uploaded. | | *No attributes present in the catalog file* | The product catalog data file doesn't have any processable data. | | *Catalog item with ID occurs more than once in the catalog, and those after the first will be ignored* | 2 or more items have the same ID—all products require a unique value. Duplicate items will not be processed. | | *Record 'X' has an error: (line X) invalid char between encapsulated token and delimiter* | A line in the data file contains an invalid use of double-quotes. These need to be handled properly by enclosing the field in double-quotes and replacing all other double quotes with 2 double quotes (e.g., *3" floppy* becomes *"3"" floppy"*). | | *(Startline X) EOF reached before encapsulated token finished* |

EOF means "end of file". The startline mentioned has an opening double quote without a closing double quote. This error has occurred because a closing double quote was not found, even when reading to the end of the file.

Alternatively, an unexpected line break could have interrupted the data stream.

| | *Error parsing (catalog type) field: with value: (field)* | The product field is invalid and cannot be accepted. | | *Record (recordNumber) has an error: The number of delimited values (FieldsLength) does not match the expected (ColumnNamesLength)* | For a given row of data, if data exists in a column without a header, this error will occur. | | *No valid records were found in the catalog file* | Either the data file is empty (i.e., no data), the data detected isn't valid, or the file name specified is incorrect. | | *More than 10% of the records in the file had errors.* | The data file cannot be processed if this error occurs. | | *The processing failed because of an internal system error. No action is required from the user. Our Engineering team has been notified and is looking to resolve the issue. The last catalog successfully processed will continue to be available to Media Partners. Please reach out to impact.com support if you require further information.* | Refer to the [impact.com status page](https://status.impact.com/) for details on service interruptions. | | *Field (field name) with value (field value) does not have a valid protocol* | The field value is not a properly formatted URL. |
#### Google Merchant Format errors There are 2 issues you may run into if you're using the Google Merchant Center format as your product catalog taxonomy, and the issues will likely arise around the format's `Category` section. {% tabs %} {% tab title="Missing Google Product Category" %} When you select *errors* on the *Product Catalogs* screen, you may see *Missing Google Product Category* in the *Suggestions* column. This means that no Google Category Code or Full Google Category String was included in your catalog. To solve this problem, refer to your Google Merchant Center account. Google automatically suggests categories for items—this suggestion should be used when uploading the corrected catalog.
{% endtab %} {% tab title="Google Product Category Mismatch" %} When you select *errors* in the *Product Catalogs* screen, you may see *Google Product Category Mismatch* in the *Invalid* column. This means that the category used for items in your catalog does not match the expected [taxonomy code](https://www.google.com/basepages/producttype/taxonomy-with-ids.en-US.txt) (e.g., 7386) or full category format Google provides. See the example below of a full Google category format. `Animals & Pet Supplies > Pet Supplies > Bird Supplies > Bird Cage Accessories > Bird Cage Food & Water Dishes` To solve this problem, correct the format in which the Google Product Categories are listed in your catalog, then re-upload your catalog.
{% endtab %} {% endtabs %} #### Troubleshoot *Pull From URL* issues If your catalog is configured to pull from a URL and isn't loading, updating, or processing correctly, use the table below to identify and resolve the issue.
IssueWhat to checkHow to fix it
URL isn't a direct download linkOpen your URL in a browser. If it redirects to a login page, cloud storage landing page, or returns a 404/403 error, the URL is not a direct download link.Update the URL to one that downloads the file directly or displays it as raw data when opened in a browser.
File name mismatchThe Upload File Name in your catalog settings must exactly match the actual file name at the URL, including the extension (.csv, .xml, .txt, .gz).Update the Upload File Name in your catalog settings to match your file name exactly—a small mismatch causes a No catalog found for the request error.
Format or delimiter mismatchConfirm that the format selected (CSV, TXT, XML, GMC) matches your file. If using a delimited file, confirm the delimiter (comma, tab, pipe) matches what's configured.Correct the format or delimiter in your catalog settings. A mismatch causes No valid records found errors.
FTP/SFTP: invalid credentials or pathVerify that your URL uses the format: sftp://{username}:{password}@{host}/{file_path}. The path must point to the exact file, not just a directory. Special characters in credentials must be URL-encoded (e.g., @ → %40).Test your credentials with an FTP client such as FileZilla. Update the URL with corrected credentials and the full file path.
Pull times out or fails to connectYour server's firewall may be blocking impact.com's requests.Contact your hosting provider or IT team to allowlist impact.com's IP address ranges.
URL requires authenticationPull From URL does not support session-based or cookie-based authentication.Use one of the following instead: a publicly accessible direct download URL, HTTP Basic Auth embedded in the URL (https://user:pass@host/path), or FTP/SFTP with credentials in the URL. If your feed requires browser-based login, switch to Direct Upload or FTP Push.
URL exceeds 2,048 charactersSigned cloud storage URLs can exceed the 2,048-character limit and may be truncated.Use a URL shortener that preserves the direct download, or host the file at a shorter URL.
Catalog stuck in Processing or PendingCheck whether the file is still accessible at the URL and whether the file size is unusually large for your pull frequency.Verify the file is available. If the catalog remains in Processing or Pending, contact support to request a manual reprocess.
Catalog stopped auto-updatingCheck whether the file is still available at the same URL, and whether the file name, format, or server access settings have changed.Restore the file at the original URL, or update your catalog settings to reflect the new URL or file name. For large catalogs (1M+ items), consider reducing the pull frequency to avoid timeouts.
Fields or data missing after uploadConfirm that your field names match the selected format's specification—for example, Google Merchant Center fields for GMC format. Map custom fields outside the standard specification to impact.com's custom field slots (Numeric1, Text1, etc.).Download your uploaded catalog from impact.com and compare it to your source file to identify where data is being lost. Update field names or mappings as needed, then re-upload.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/troubleshoot-product-catalog-errors-and-warnings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.