> For the complete documentation index, see [llms.txt](https://docs.overse.app/hubble/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overse.app/hubble/analytics/customer-insights-admin-block.md).

# Customer insights - Admin Block

The **Customer Insights block** brings key Hubble-specific data directly into your Shopify Admin so your team can see exactly what our targeting engine sees — no confusion, no missing context.

## Why use the Customer Insights block?

Shopify doesn’t always show the full picture. For example, **test orders** are excluded from the default order count in the customer profile. Hubble, however, uses all data — including test orders — when evaluating [conditions](/hubble/conditions/intro-to-conditions.md).

By installing the **Customer Insights block**, you get:

* ✅ Accurate **number of orders**, including test orders
* ✅ Account creation date
* ✅ Marketing opt-in status
* ✅ Full alignment between what Hubble sees and what your team sees
* ✅ And more as we add more rules to [conditions](/hubble/conditions/intro-to-conditions.md).

{% hint style="info" %}
This block lives **inside the Shopify Admin customer profile page**, so your team can access it instantly while reviewing a customer.
{% endhint %}

## Visual Example

Here’s how the count can differ:

<figure><img src="/files/404sNQN3c9pPyGVgHHeq" alt=""><figcaption></figcaption></figure>

> *In this example, Shopify shows only 1 order, but Hubble shows 2 (including a test order).*
>
> \
> \&#xNAN;*With the Customer Insights block, you get the full picture used by our targeting engine.*

## How to set it up

{% stepper %}
{% step %}

#### Go to any customer’s profile in the Shopify Admin

You'll see a section labeled **“App blocks”**.

<figure><img src="/files/6nBOoXFSwFBvoRfR6Xm5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Click on "+ App block" and select Hubble's "Customer insights"

Shopify will show a list of available app blocks.

<figure><img src="/files/s3as72gYI2laWJbkLA89" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### (Optional but recommended): Pin it

Click the **pin icon** to keep the block visible by default for all staff.

<figure><img src="/files/KtdqxFkfB5ivT49pcose" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### ✅ Done!

You should now see the full customer insights block every time you visit a customer’s profile:

<figure><img src="/files/i46b8RNXMyLlVQPXdEtc" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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.overse.app/hubble/analytics/customer-insights-admin-block.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.