Event timeline analytics

Event timeline analytics: available fields, filters, associations, and API operations.

Path: event-timeline-analytics at organization level
Methods: GET collection/record only.

Fields: event-id, event-start-date, window-start, window-end, step, metric-version, generated-at, time-zone, points.
Filters: event_id, window_start, window_end, step.
step values: day, week, month. An unsupported value returns an empty collection.
Associations: none.

GET /api/core/organizations/30/event-timeline-analytics?event_id=319986&window_start=2026-09-01&window_end=2026-09-30&step=day

The default window is the event’s start through end date. Past events default to weekly points; other events default to daily points. A requested window is capped at two years. Invalid dates return 400.

Reporting verification: a source review identified a possible same-day undercount in the timeline projection, not yet verified against a live deployment. Reconcile a known sample with multiple records created on one day before using these values for totals or trend decisions. If they cannot be reconciled, omit the timeline chart and use event summaries or session/timeslot comparisons. See the reporting guidance.

Points are cumulative; do not sum them. A daily change requires a verified preceding point, and the first point may already include earlier activity. Preserve returned dates and verify the day boundary; the time-zone metadata alone does not establish how the series was grouped.

points is an array with this structure. Values below illustrate the response format and are not a verified event dataset:

[
  {
    "date": "2026-09-03",
    "relative-event-day": 0,
    "joined-registrants-cumulative-count": 850,
    "meeting-requests-cumulative-count": 120,
    "unconverted-open-chat-requests-cumulative-count": 15,
    "chat-messages-cumulative-count": 340,
    "total-engagements-cumulative-count": 475
  }
]