> For the complete documentation index, see [llms.txt](https://docs.elitebundleapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elitebundleapp.com/grow-and-manage/analytics.md).

# Analytics

Understand Shopify bundle analytics for views, orders, revenue, conversion rate, average order value, and top-performing bundles in Elite Bundle Builder.

Analytics show which bundles attract attention, which turn shoppers into buyers, and where to improve the offer, design or promotion. The dashboard covers the last 30 days.

## Where to find it

* **Analytics** in the app navigation: store-wide, to compare bundles
* The analytics action on a bundle in the dashboard: one bundle, to improve it

## The metrics

| Metric              | What it means                | Why it matters                     |
| ------------------- | ---------------------------- | ---------------------------------- |
| Views               | Bundle page views            | Demand and traffic                 |
| Orders              | Orders that include a bundle | Buying activity                    |
| Revenue             | Sales attributed to bundles  | Financial impact                   |
| Conversion          | Orders ÷ views               | How well traffic turns into buyers |
| Average order value | Revenue ÷ bundle orders      | How valuable each bundle order is  |

Trend charts show views, orders and revenue over time. The store-wide page adds **top bundles by revenue** and **top bundles by conversion**.

## What to do with the numbers

{% tabs %}
{% tab title="High views, low orders" %}
The page gets traffic but does not convert. Reduce friction:

* Fewer steps, clearer first step
* Better product images
* Add or improve tiered discounts
* Make the add-to-cart button obvious
* Check the mobile experience
* Loosen required steps that are too strict
  {% endtab %}

{% tab title="Low views, good conversion" %}
The offer works; it needs traffic:

* Add it to navigation and the homepage
* Link it from related product pages
* Promote it in email or SMS
* Use a clearer bundle name
  {% endtab %}

{% tab title="Orders fine, revenue low" %}
Shoppers buy small bundles:

* Add higher-value products
* Reward larger selections with a higher tier
* Raise maximums where it makes sense
* Check whether the first tier is too generous
  {% endtab %}

{% tab title="Revenue fine, conversion low" %}
Keep the offer, cut friction:

* Move the selection area higher on the page
* Shorten the banner text
* Clearer discount messaging
* Try a simpler template
  {% endtab %}
  {% endtabs %}

{% hint style="info" %}
Do not judge a bundle on one day. Compare the days before and after a change (new tiers, a redesign, fewer steps, a homepage feature) and look for movement in views, orders, conversion and revenue together.
{% endhint %}

## Analytics look empty or low?

* Confirm the bundle is **Active** or **Unlisted** and has been viewed on the storefront
* Confirm **Elite Embed Core** is enabled on the live theme
* Confirm orders went through the bundle page, not as separate products
* Check [App settings](/get-started/settings.md#setup-status) for a failed web pixel
* Allow some time for new activity to appear

Customer details appear only where Shopify makes that context available. Use analytics in line with your store's privacy commitments.


---

# 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://docs.elitebundleapp.com/grow-and-manage/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.