> For the complete documentation index, see [llms.txt](https://bogos-guideline.gitbook.io/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bogos-guideline.gitbook.io/user-guide/detailed-guide/analytics/bundle-analytics.md).

# Bundle Analytics

{% embed url="<https://youtu.be/vd_Z9KEHm-8?si=fq5pADgSH6H4vU6O&t=155>" %}

## 1. Filter&#x20;

<figure><img src="/files/2yjS3ISxD1xPcUWybZLt" alt=""><figcaption></figcaption></figure>

### Filter by timeframe&#x20;

Filter a fixed timeframe to analyze the performance of campaigns within a period.&#x20;

### Filter by offer&#x20;

This filter will help you to analyze the performance of each offer.&#x20;

{% hint style="info" %}
All bundles that resulted in an order will appear in the filter to be selected, even deleted/expired bundles.
{% endhint %}

## 2. Big numbers

<figure><img src="/files/cGQ0tBUccCEzQIqHdvjz" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="246">Field</th><th>Definition</th></tr></thead><tbody><tr><td>Total order revenue</td><td>The total revenue from all orders that include a bundle.</td></tr><tr><td>Total bundle revenue</td><td>The total revenue generated from the bundles within orders.</td></tr><tr><td>Orders with bundles</td><td>The total number of orders that contain at least one bundle</td></tr><tr><td>Average order value (AOV)</td><td>The average revenue per order that contains a bundle (Total order revenue/Orders with bundles)</td></tr><tr><td>Add to cart value</td><td>The average revenue generated each time a customer clicks “Add to Cart” on a bundle (Bundle revenue/number of "Art to cart" clicks)</td></tr><tr><td>Total bundles purchase</td><td>The total number of bundles purchased</td></tr></tbody></table>

## 3. Overview funnel

The overview funnel gives you a view into how your bundles convert through 3 important stages:

<table><thead><tr><th width="246">Field</th><th>Definition</th></tr></thead><tbody><tr><td>Bundle view</td><td>The number of times a product page containing a bundle has been viewed.</td></tr><tr><td>Total bundle revenue</td><td>The number of clicks on the “Add to Cart” button from the bundle widget</td></tr><tr><td>Orders</td><td>The total number of orders that include a bundle</td></tr></tbody></table>

## 4. Order details

<table><thead><tr><th width="129">Field</th><th width="172">Format </th><th>Definition</th></tr></thead><tbody><tr><td>Order</td><td>string</td><td>The name of the order, similar to Orders admin in Shopify</td></tr><tr><td>Date</td><td>date time</td><td>The time when the order is created</td></tr><tr><td>Gift</td><td>text</td><td>Product title of the gift product included in the order</td></tr><tr><td>Total </td><td>currency</td><td>Revenue of the order</td></tr><tr><td>Action</td><td>button</td><td><ul><li>View: Open order details in Shopify Admin </li><li>Delete: Delete order from Analytics</li></ul></td></tr></tbody></table>


---

# 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://bogos-guideline.gitbook.io/user-guide/detailed-guide/analytics/bundle-analytics.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.