> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/using-euno/usage-optimization/omni-usage-data.md).

# Omni Usage Data

Euno observes impression records for Omni workbooks and dashboards based on usage data pushed from your Omni instance.

## Impression Records

An impression record is generated each time a user views an Omni workbook or dashboard. These impressions are collected via the [Omni Usage integration](/sources/business-intelligence/omni-integration/omni-usage-setup.md), which receives usage data from your Omni instance (or an external export) and associates it with the relevant Omni resources in Euno.

{% hint style="info" %}
To observe usage data, you must set up both the [Omni integration](/sources/business-intelligence/omni-integration.md) (to discover workbooks and dashboards) and the [Omni Usage integration](/sources/business-intelligence/omni-integration/omni-usage-setup.md) (to receive and aggregate usage events).
{% endhint %}

## Properties

| Property                                                                                                                    | Value                                                                                                                                           | Applicable to                     |
| --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- |
| <p><code>total\_impressions\_14d</code><br><code>total\_impressions\_30d</code><br><code>total\_impressions\_60d</code></p> | The number of impressions the resource had within the last 14/30/60 days.                                                                       | `omni_workbook`, `omni_dashboard` |
| `used`                                                                                                                      | A list of user-usage entries with per-user counts and timestamps. Supports a user-level breakdown in the resource side pane and Euno Assistant. | `omni_workbook`, `omni_dashboard` |

## Usage relationships

Workbooks and dashboards with usage data also expose:

| Source type(s)                    | Relationship | Target type(s) | Notes                                               |
| --------------------------------- | ------------ | -------------- | --------------------------------------------------- |
| `omni_workbook`, `omni_dashboard` | is used by   | `user`         | Per-user impression counts from the `used` property |

## Dashboard vs. Workbook Usage

When a user views an Omni **dashboard**, the usage is counted for both:

* The dashboard itself
* The parent workbook that contains the dashboard

This double-counting reflects that dashboard views contribute to both the dashboard's popularity and the workbook's overall usage.

## Related

* [Omni Usage Setup](/sources/business-intelligence/omni-integration/omni-usage-setup.md) – Configure the push integration to send usage data to Euno.
* [Omni integration](/sources/business-intelligence/omni-integration.md) – Set up the Omni integration to discover workbooks and dashboards.


---

# 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.euno.ai/using-euno/usage-optimization/omni-usage-data.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.