> 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-uploads-and-connections.md).

# Troubleshoot Product Catalog Uploads & Connections

Before impact.com can process a product catalog, it must successfully receive the catalog file. This guide is organized by upload method, so go to the section for the method your catalog uses: [*Pull From URL*](#pull-from-url-recommended), [*Integrated Shopping Cart Import*](#integrated-shopping-cart-import-recommended), [*impact.com FTP server*](#impact.com-ftp-server), [*impact.com SFTP server*](#impact.com-sftp-server), or [*Direct Upload*](#direct-upload). If you’re not sure which method your catalog uses, edit the catalog and check its [*Upload Method* settings](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/add-product-catalogs-as-a-brand.md#upload-your-product-catalog).

impact.com recommends *Pull From URL* or *Integrated Shopping Cart Import*, because impact.com controls when your catalog is pulled and how often it updates. If you use the impact.com FTP server, the impact.com SFTP server, or *Direct Upload*, you're responsible for providing updated catalog data regularly, preferably daily, though weekly also works.

If impact.com received your file but your catalog shows errors or warnings, see [Troubleshoot Product Catalog Errors & Warnings](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/troubleshoot-product-catalog-errors-and-warnings.md).

## Pull From URL (recommended)

Supported protocols for *Pull From URL* are `http://`, `https://`, `ftp://`, and `sftp://`. If your catalog isn't loading, updating, or processing correctly, use the table below to identify and resolve the issue.

| Issue                                  | What to check                                                                                                                                                                                                                                                                                                       | How to fix it                                                                                                                                                                                                                                                                                                     |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| URL isn't a direct download link       | Open your URL in a browser. If it redirects to a login page, a cloud storage landing page, or returns a 404 or 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 mismatch                     | The *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* to match your file name exactly. A small mismatch causes a *No catalog found for the request* error.                                                                                                                                                                                |
| Format or delimiter mismatch           | Confirm that the format selected (CSV, TXT, XML, GMC) matches your file. If you use 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 path  | Verify 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 (for example, `@` becomes `%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 connect     | Your 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 authentication            | This upload method does not support session-based or cookie-based authentication.                                                                                                                                                                                                                                   | Use 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 your catalog to a different upload method, such as *Direct Upload* or the *impact.com FTP server*. |
| URL exceeds 2,048 characters           | Signed 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 Pending | Check 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](https://app.impact.com/support/portal.ihtml) to request a manual reprocess.                                                                                                                                  |
| Catalog stopped auto-updating          | Check 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 (1,000,000+ items), consider reducing the pull frequency to avoid timeouts.                                                                                                         |
| Fields or data missing after upload    | Confirm that your field names match the selected format's specification, for example [Google Merchant Center fields](https://support.google.com/merchants/answer/7052112) for GMC format. Map custom fields outside the standard specification to impact.com's custom field slots (`Numeric1`, `Text1`, and so on). | Download your uploaded catalog from impact.com and compare it to your source file to find where data is being lost. Update field names or mappings as needed, then re-upload.                                                                                                                                     |

## Integrated Shopping Cart Import (recommended)

This method pulls your catalog from an existing e-commerce platform. Most connection problems come down to incorrect credentials or missing read permissions. Find your platform below.

### Shopify (recommended)

If you see an error such as *Unsuccessful HTTP status code when connecting to Shopify: 401* or *No valid records were found in the catalog file*, your authentication details or permissions are usually the cause.

* Your password must be the **Admin API access token**, which starts with `shpat_` (or `shap_`). You'll find it in your Shopify Admin under **Apps** **→** **API Credentials** **→** **Admin API access token**.
* If you don't see the **Admin API access token**, select **Install app** in Shopify to generate it.
* Confirm the `read_products` permission (scope) is granted to the app. Without it, Shopify returns an error stating the action requires merchant approval for the `read_products` scope.
* For collections, find the collection ID in your Shopify Admin under **Products** **→** **Collections**. Select the collection; its ID appears at the end of the page URL.

For full setup steps, see the [Shopify product catalog integration guide](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/e-commerce/integrate-with-shopify/shopify-product-catalog).

### Amazon (recommended)

Amazon shopping cart integration is exclusive to brands with [Seller subscriptions](https://help.impact.com/brand/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-program-explained.md) and isn't a self-serve feature. Automatic catalog import from Amazon is limited to 1,000 products due to Amazon API restrictions. If your Seller catalog has more than 1,000 products, use a file upload method, such as *Pull From URL*, instead.

For setup steps, see the [Amazon integration guide](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/e-commerce/integrate-with-amazon).

### BigCommerce

Connecting BigCommerce requires two values and the correct read-only permissions.

* Enter your **Store Hash** and **Access Token** in the impact.com UI. Your store hash is the identifier in your store's API path.
* Set the **Products** and **Information & settings** permissions to read-only when you create the API account in BigCommerce.

For reference, see BigCommerce's guide to [creating API tokens](https://developer.bigcommerce.com/docs/storefront-auth/tokens#create-a-token).

### WooCommerce

If you see *Connection to WooCommerce was unsuccessful. Please try again*, check your credentials and API settings.

* Your **API Username** is your WooCommerce *Consumer Key*, and your **API Password** is your *Consumer Secret*.
* Enable the Legacy REST API in WooCommerce: **WooCommerce** **→** **Settings** **→** **Advanced** **→** **Legacy API**, then select the checkbox to enable it.

For reference, see the [WooCommerce REST API documentation](https://woocommerce.com/document/woocommerce-rest-api/).

### Shoplazza

Your Shoplazza private app needs read access to the following resources: `product`, `collection`, and `shop`.

For setup steps, see Shoplazza's guide to [building private apps](https://www.shoplazza.dev/reference/quick-construction-of-private-apps).

## impact.com FTP server

Most FTP issues come down to connection settings or credentials.

| Issue                       | What to check                                                           | How to fix it                                                                                                                                                                                            |
| --------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Can't connect to the server | Confirm you are connecting to host `products.impact.com` on port `21`.  | Update your FTP client with the correct host and port, then reconnect.                                                                                                                                   |
| Missing FTP credentials     | You need the FTP login and password issued for your account to connect. | Locate your *FTP Product Data System credentials* in your account's technical configuration settings. If you cannot find or access them, [contact support](https://app.impact.com/support/portal.ihtml). |

## impact.com SFTP server

The impact.com SFTP server is a specialized upload method reserved for specific integrations.

| Issue                            | What to check                                                                                                                                  | How to fix it                                                                                                                                                                                               |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your feed platform can't connect | Confirm your platform is connecting to host `products.impact.com` on port `22`, and that the credentials are the ones issued for your account. | Test the same credentials in a standard SFTP client such as FileZilla or Cyberduck. If the client connects but your feed platform still can't, switch the catalog to *Pull From URL* using the steps below. |

### Switch from a push to a pull

impact.com recommends pulling your feed rather than pushing it. When impact.com pulls the feed directly from your feed platform's SFTP server (for example, SFTPGo), impact.com controls when and how often your catalog updates, and you no longer rely on impact.com's SFTP server. Switching to a pull also resolves connection errors your feed platform (for example, Feedonomics) may have when pushing files to impact.com's SFTP server.

Before you switch, ask your feed platform (for example, Feedonomics) to set up an outbound SFTP location for your feed and provide:

* SFTP/FTP host and port (for example, sftpgo.feedonomics.com:22)
* Username and password
* File path (for example, incoming/catalog\_feed.txt.gz)

{% hint style="warning" %}
**Warning:** Update your existing catalog rather than creating a new one. A new catalog using the same *Upload File Name* returns a *File name already in use* error, and your existing catalog may already power other programs.
{% endhint %}

1. From the left navigation menu, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** **→** **Content** **→** **Products** **→** [**Product Catalogs**](https://app.impact.com/secure/advertiser/engage/ads/productcatalogs/manage-ads-product-catalog-flow.ihtml).
2. Hover over your existing catalog, then select **Edit**.
3. In the *Upload Method* section, select **Pull From URL**.
4. Select the **Format** that matches your feed file.
5. Enter your **Upload File Name**, matching the file name exactly, including its extension.
6. Enter your **Pull URL** in the format `sftp://[username]:[password]@[host]:22/[path/to/file]`.
   * URL-encode any special characters in your credentials, for example `@` becomes `%40`.
7. Select your **Fetch Frequency**, **Fetch Time**, and **Time Zone**.
8. Select **Save**.

## Direct Upload

Direct Upload issues are usually a format or file-name mismatch, or a file that exceeds the 1 GB limit.

| Issue                         | What to check                                                                                                                                                 | How to fix it                                                                                                                                         |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Wrong format selected         | The format you chose (for example, TXT) does not match the file you uploaded (for example, XML).                                                              | Re-upload and select the format that matches your file. XML files use the `.xml` extension, CSV files use `.csv`, and TAB-delimited files use `.txt`. |
| File name mismatch            | The name of the file you uploaded must exactly match the *Upload File Name* set in your catalog settings, including the extension.                            | Rename your file, or update the *Upload File Name* so the two match exactly.                                                                          |
| Compressed file won't process | impact.com supports gzip and standard zip-compressed files. A compressed file can use a second extension to denote compression, for example `catalog.xml.gz`. | Confirm your compression type is gzip or zip, and that the file uses the correct extensions for both its format and its compression.                  |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/troubleshoot-product-catalog-uploads-and-connections.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
