> 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/faq.md).

# Data Analytics FAQ

Frequently asked questions about funnels, retention, and event aggregation.

These are frequently asked questions about checking funnels, retention, and events in Hackle Data Analytics.

#### How is the data in the funnel graph aggregated?

The funnel graph aggregates by Unique ID. It does not simply add up the daily figures.

Each unique user who triggered the event during the period is counted only once. Even if the same user triggers the event on multiple days, they count as one user.

***

#### Can I change the name of a registered event?

Event names cannot be changed. Collect the event under a new name and turn the existing event Off.

***

#### How are active users counted in an event's calculation method?

Active users include all users who triggered Any Event.

For example, if you set the calculation method for `Purchase Complete` to the average count per active user, the total number of occurrences of that event is divided by the total number of users based on Any Event.

***

#### The chart data for the same period changed from yesterday.

Events that occurred in the past can be delivered late. Hackle reflects data from up to 7 days earlier in the results.

{% hint style="warning" %}
If the app is offline or is not terminated in the background, event delivery can be delayed.\
Past events delivered late are still reflected as valid data for up to 7 days.
{% endhint %}

***

#### Why do the conversion rates differ between the Funnel chart and the User Path chart?

User Path only counts conversions within the same session. Funnel counts conversions within the query period, regardless of session.

Funnel results also differ by aggregation type. Any Order Funnel, Closed Funnel, and Direct Order Funnel each use different criteria.

***

#### How is a new visit event measured?

The point at which the first event is collected for a Hackle ID is counted as a new visit.

***

#### Why is Day 0 retention in the Retention chart lower than 100%?

This is expected when the Start Event and the Metric Event are different.

If the two events are the same, Day 0 retention is 100%.\
If the two events differ, the percentage of users who triggered the Start Event and also triggered the Metric Event is calculated.

***

#### How is the total number of users in the Retention chart calculated?

It is the actual occurrence rate relative to the number of unique users in the cohorts that can produce retention for that period unit.

For example, recently acquired cohorts that cannot produce Week 2 retention are excluded from the denominator.

***

#### What is 'Other Events' in User Path?

It is the sum of events not included in the top events in Previous Flow Analysis.

For example, suppose 1,000 events occurred at step 3. If the top events account for 800, the remaining 200 are shown as 'Other Events'.

***

#### Why does 'No Data' appear in User Path?

It means there is no data at that step in Previous Flow Analysis.

For example, you can select `session_start` as the final event and query up to four previous steps. If there are no events at the fourth previous step, 'No Data' is shown.


---

# 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/faq.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.