---
title: "Get Engagement Summary"
method: GET
path: "/analytics/engagement-summary"
tags: ["analytics"]
---

# Get Engagement Summary

`GET /analytics/engagement-summary`

Per-category engagement rollup powering the dashboard summary cards.

Returns one row per category in ``EVENT_CATEGORY_MAP`` plus a top-events
breakdown and a 7/14/30-day sparkline (daily counts) for each. Counts are
sourced from ``user_activity_sessions.activities_performed`` (the same
JSONB dict that retention/activation endpoints already use), so any event
a feature emits via ``trackFeatureUse(...)`` shows up automatically.

The categories are coarse on purpose — fine-grained per-event detail is
on the Activity Monitoring page. The point of this endpoint is the
"is this whole feature area being used" headline number.

## Query parameters

- `days` integer

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-09-02** `45cbba31aa7d` — 1 info
  - added the new optional `query` request parameter `segment`

[Change history](https://skmtc.dev/fluentea/apis/aurqa-language-learning-platform-refactored/changes/analytics/engagement-summary/get.md)

---

[API](https://skmtc.dev/fluentea/apis/aurqa-language-learning-platform-refactored.md) · [All operations](https://skmtc.dev/fluentea/apis/aurqa-language-learning-platform-refactored/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/fluentea/aurqa-language-learning-platform-refactored/revisions/78f314acd8bf/schema)