> 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/manage-improve-product-data/insights/channable-analytics/review-google-analytics-performance.md).

# Review Google Analytics performance

View channel and product traffic, conversion, and revenue data in Channable.

You can use your connected Google Analytics data to review channel traffic, conversions, revenue, and product performance for your channels.

***

In your project, go to **Dashboard >** **Analytics**.

If you have Analytics set up, and channels, you should see two entries: **Analytics revenue**, and **Analytics revenue per channel**.

{% hint style="info" %}
Analytics data appears a few days after you set up the connection. If entries are missing or empty, [check your Google Analytics connection setup](/manage-improve-product-data/insights/channable-analytics/set-up-google-analytics-in-channable.md). If the download fails, [fix the failed Analytics download](/manage-improve-product-data/insights/channable-analytics/analytics-troubleshooting/fixing-a-failed-analytics-download-error.md).
{% endhint %}

#### Change the reporting period

1. Click the date range dropdown above **Analytics revenue**.
2. Select a date range.
3. Click **Apply**.

### **Analytics revenue**

The **Analytics revenue** graph compares channel revenue over time.

#### Show or hide channels

1. Below the **Analytics revenue** graph, click **Toggle visibility**.
2. Below the graph, click a channel name to show it again.

### **Analytics revenue per channel**

The **Analytics revenue per channel** table breaks down analytics data collected from Google on your channel levels.

It can detail:

* **Sessions:** Visits from a channel.
* **Transactions:** Completed purchases from a channel.
* **Conversion rate:** Percentage of sessions that resulted in a transaction.
* **Revenue:** Revenue attributed to a channel.
* **Bounces:** Sessions with no further interaction.
* **Bounce rate:** Percentage of sessions that bounced.

<figure><img src="https://content.gitbook.com/content/u8whzIfip72Kvn3M1bsc/blobs/BhYce0n0OE5xoLdDu3uY/19238252826002" alt="Analytics revenue per channel table showing traffic, transaction, conversion, revenue, and bounce metrics."><figcaption></figcaption></figure>

### Review performance on product/item level

In the **Analytics revenue per channel** table, click a channel in the **Channel** column.

<details>

<summary><strong>Sort products</strong></summary>

In the product table, click the <i class="fa-angles-up-down">:angles-up-down:</i> sort icon to sort by a metric in ascending or descending order.

</details>

<details>

<summary><strong>Change the reporting level</strong></summary>

In the **Dimension** menu, select the reporting level you need.

</details>

<details>

<summary><strong>Find products</strong></summary>

In the search bar, enter a title, description, or item ID.

</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 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://helpcenter.channable.com/manage-improve-product-data/insights/channable-analytics/review-google-analytics-performance.md?ask=<question>&goal=<endgoal>
```

`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.