> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/css/css-troubleshooting.md).

# CSS troubleshooting

Fix setup issues and common errors in Channable CSS

<details>

<summary>My merchant is missing in <strong>Merchant Overview</strong>, but it's active in Google</summary>

{% stepper %}
{% step %}

### Check your access

1. Double-check that your Google connection has admin access to Merchant Center and Google Ads.
2. Wait a few hours after connecting or refreshing the connection.
   {% endstep %}

{% step %}

### Check your sources in Google

If you're sure you have admin access, your issue may lie in with your data sources in Google Merchant Center.

1. In Google Merchant Center, go to **Settings > Data sources**.
2. Check whether your account relies on any of the following data sources:
   * **API data sources**
   * **Google UI/Manual data sources** (with multiple feed labels)
   * **Found by Google** (autofeed) data sources

These specific data source types prevent Channable from reading your product data. Because they can support multiple targets without fixed settings, Google doesn't return `feedLabel` or `language` fields for them.
{% endstep %}

{% step %}

### Add a file data source

If you relied on one of those sources, add an additional public product data file to your Merchant Center account so Channable can access required product values:

1. In Google Merchant Center, open **Settings > Data sources**.
2. At **Provided by you**, click **Add product source**.
3. Upload your product data in a CSV, XML, or Google Sheet file.
   {% endstep %}

{% step %}

### Refresh your data

1. Back in Channable, go **CSS Merchants >** **Merchant Overview**.
2. Click **Refresh**.

If you don't see the option to refresh, please [contact Support](/get-started/contact-support.md).
{% endstep %}
{% endstepper %}

</details>

<details>

<summary>Error: "We couldn’t retrieve your performance data"</summary>

<figure><img src="https://825581969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbBY5zPT0WiTFQ8xha2EA%2Fuploads%2FKf1SoTin0YCzzrbaxSjU%2FPH-feature-integration-%E2%80%93-Figma-02-25-2026_09_03_AM.png?alt=media&amp;token=5ededfcd-8ed7-488a-a22d-a1d7b2864c50" alt=""><figcaption></figcaption></figure>

If you have the status “We couldn’t retrieve your performance data” at your Dashboard, try the following to retrieve your performance data:<br>

1. Make sure that the Google account you linked as a CSS merchant has access [to a Google Ads account](https://helpcenter.channable.com/list-advertise/google/manage-and-optimize-google-ads/google-text-ads/set-up-text-ads/adding-a-new-google-ads-connection) that is linked to the same merchant center OR link another Google account that has access to Google Ads. Click **Manage connections** to check this.
2. Once you have made these access changes, click **Retry connection** to try to retrieve your performance data.

</details>

<details>

<summary>Error: "Unsupported country for CSS program" issue</summary>

If you encounter the **Unsupported country for CSS program** error while using Channable’s CSS, it almost always means your Merchant Center is set to a country outside the 21 supported regions in the EU.

This issue arises when switching to a Google CSS partner while being active in countries outside the CSS program.

#### How to solve the issue: <a href="#h_01hz4sbnzw18gbkp78r2vxt63j" id="h_01hz4sbnzw18gbkp78r2vxt63j"></a>

1. Create a new Merchant Center account [here](https://www.google.com/intl/en_us/retail/). This account must be created with a Gmail account that is not connected to the Merchant Center. If you don't have an account, you can create a new Google account.
2. Claim the same URL and Google CSS, to access the CSS Dashboard. It is not necessary to include any products in it, you only have to claim the URL.
3. Within your **CSS Dashboard** in your new shell account (click the cog wheel and then **“Comparison Shopping Services”**), ensure your CSS partner is set for both EU and non-EU countries. Look for the **"Selected for placing products outside of Europe"** option and enable it, if it's not already active.

If you are experiencing ongoing issues, [contact our support team](https://www.channable.com/contact). We're here to ensure your products are correctly listed in all markets.

</details>

<details>

<summary>Error: "CSS not selected for this destination" for Google Free Listings</summary>

If your Free Listings appear as disapproved, open **Diagnostics** in Merchant Center. Check whether Google reports **CSS not selected for this destination**.

If you can't select a CSS for Free Listings, another Merchant Center shell account may have already claimed your website URL. Find that account and select Channable CSS there.

If you can't find the shell account, create one using a Google account that isn't connected to Merchant Center. Then verify and claim the same website URL.

For the complete resolution steps, see [Solve “CSS not selected for this destination” for Free Listings](/css/readme/free-listings/solve-css-not-selected-for-this-destination-for-free-listings.md).

</details>


---

# 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://helpcenter.channable.com/css/css-troubleshooting.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.
