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

# Data Analytics Introduction

Learn how to analyze customer behavior and business metrics in real time.

Hackle Data Analytics is a platform for understanding customer behavior and business performance.

{% hint style="success" %}
Run A/B Tests, Feature Flags, and Data Analytics on a single set of event data.

Consolidate Web and App behavior logs and analyze them in real time without sampling.
{% endhint %}

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-8feb81d29373ba6b855bdbdadd5f3643d47f981c%2Fc9a0785-Frame_180422_14d99559d4dce471.png?alt=media)

### What can you analyze?

Set a time range and conditions to answer questions like these.

* Which channels, operating systems, and regions do users come from?
* How are sign-up, search, and purchase conversion rates changing?
* Are revenue, average order value, and subscriber count moving toward your targets?

{% hint style="info" %}
You can configure analysis conditions using time ranges, events, and user properties without writing SQL.
{% endhint %}

### Who it is for

{% hint style="info" %}
**Product teams** review the customer journey and feature performance.

**Marketing teams** compare acquisition channels and campaign performance.

**Data teams** reduce repetitive analysis and focus on advanced work.

**Leadership teams** check key KPIs and business trends quickly.
{% endhint %}

### Get started

<table data-view="cards"><thead><tr><th>Guide</th><th data-hidden data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td><i class="fa-chart-line">:chart-line:</i><br><strong>Chart Types</strong><br>Choose Insight, Retention, Funnel, or User Path Analysis.</td><td><a href="/en/data/chart-types.md">Chart Types</a></td></tr><tr><td><i class="fa-lightbulb">:lightbulb:</i><br><strong>Data Analytics Tips</strong><br>See how to use each analysis type, with examples.</td><td><a href="/en/data/analysis-tips.md">Data Analytics Tips</a></td></tr><tr><td><i class="fa-file-lines">:file-lines:</i><br><strong>Data Report</strong><br>Organize analysis results and share them with your team.</td><td><a href="/en/data/data-report.md">Data Report</a></td></tr></tbody></table>

### Why Hackle Data Analytics

{% hint style="success" %}
Analyze Web and App data together. Review the full dataset in real time.

The same events power experiments and Feature Flags. Events are never billed twice.
{% endhint %}

<details>

<summary>Compare with other analytics tools</summary>

**Google Analytics** works well for web traffic analysis. Hackle analyzes Web and App user behavior together.

**Amplitude and Mixpanel** provide product analytics. Hackle runs data analytics, experiments, and Feature Flags on one platform.

</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://docs.hackle.io/en/data/data-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.