# Churn-Related Reports ## Churn and Engagement - [POST /v3/reporting/engagement/churnAndEngagement/{product_id}](https://rui-api.redocly.app/v3_api_redocly/churn-related-reports/paths/~1v3~1reporting~1engagement~1churnandengagement~1%7Bproduct_id%7D/post.md): This report provides insight on the lifetime of lost users. It is meant to report what happened during the whole lifetime of these installations rather than what happened during a defined date range. This report shows how new installations during the specified date range were engaged or lost during their lifetime. This report does not only show users who were reported lost, but instead, all users who installed during the specified date range are included. By viewing this report, one can then see how many users were still active/engaged after x days/weeks/months. ## Churn Days Histogram - [POST /v3/reporting/churn/histogram/days/{product_id}](https://rui-api.redocly.app/v3_api_redocly/churn-related-reports/paths/~1v3~1reporting~1churn~1histogram~1days~1%7Bproduct_id%7D/post.md): This report provides insight on the lifetime of lost users. It is meant to report what happened during the whole lifetime of these installations rather than what happened during a defined date range. This report consists of a histogram that shows the number of days clients were active within their lifetime. ## Churn Runtime Histogram - [POST /v3/reporting/churn/histogram/runtime/{product_id}](https://rui-api.redocly.app/v3_api_redocly/churn-related-reports/paths/~1v3~1reporting~1churn~1histogram~1runtime~1%7Bproduct_id%7D/post.md): This report provides insight on the lifetime of lost users. It is meant to report what happened during the whole lifetime of these installations rather than what happened during a defined date range. This report consists of a histogram that shows the total amount of time in hours users spent interacting with your application. ## Churn Sessions Histogram - [POST /v3/reporting/churn/histogram/sessions/{product_id}](https://rui-api.redocly.app/v3_api_redocly/churn-related-reports/paths/~1v3~1reporting~1churn~1histogram~1sessions~1%7Bproduct_id%7D/post.md): This report provides insight on the lifetime of lost users. It is meant to report what happened during the whole lifetime of these installations rather than what happened during a defined date range. This report consists of a histogram that shows the number of times users launched your application. ## Churn User Activity Data Table - [POST /v3/reporting/eventTracking/churn/lifetime/dataTable/{product_id}](https://rui-api.redocly.app/v3_api_redocly/churn-related-reports/paths/~1v3~1reporting~1eventtracking~1churn~1lifetime~1datatable~1%7Bproduct_id%7D/post.md): The aim of this report is to show how events occurred throughout the churned clients' lifetime before they were lost. The data is presented as a paged table which shows a list of all events and how many times each occurred. This report contains data about each tracked event, how many times it occurred, how many times each user performed each event on average, etc. The events can be presented either as a flat view or categorized hierarchically based on event category and name. Data for each event can then be segmented by any property. ## Churn User Activity Histogram - [POST /v3/reporting/eventTracking/churn/lifetime/histogram/{product_id}](https://rui-api.redocly.app/v3_api_redocly/churn-related-reports/paths/~1v3~1reporting~1eventtracking~1churn~1lifetime~1histogram~1%7Bproduct_id%7D/post.md): The aim of this report is to show how events occurred throughout the churned clients' lifetime before they were lost. The data is presented as a histogram showing only a subset of events as specified. The histogram shows how much churned clients performed an event throughout their lifetime or their average daily/weekly/monthly usage. The report consists of histogram-style data for each different event or event combination that has been requested. The results consist of 4 histograms based on different values: event counts, average event count per day, average event count per week, and average event count per month.