Skip to content
English
Submit a request
  • There are no suggestions because the search field is empty.

Analytics API: dateEnd Parameter for Aggregated Page Analytics

Enabling accurate date-range filtering in the Tiled aggregated page analytics endpoint

1. Purpose & Scope

This article documents the addition of the dateEnd parameter to the Tiled aggregated page analytics API endpoint, released in v60.0.0. This parameter enables consumers of the analytics API to define a precise date range for analytics queries, ensuring that returned data is accurately bounded.

Scope: Developers and data teams consuming the Tiled Analytics API directly. Customers using third-party BI tools or data pipelines connected to the Tiled API.

2. Control Objective

The control objective is to ensure that analytics data returned by the API accurately represents the time period specified by the caller, eliminating data completeness and accuracy issues caused by unbounded or ambiguous query windows. This supports the integrity of engagement reports used for business decisions and audit evidence.

3. Parameter Reference

Endpoint

GET /analytics/pages/aggregated

New Parameter

dateEnd

Type

String — ISO 8601 date format (YYYY-MM-DD)

Required

No — optional parameter. If omitted, behavior defaults to the previous unbounded-end behavior.

Effect

Filters the returned aggregated page analytics to include only sessions and events that occurred on or before the specified date.

Pair With

dateStart — use both parameters to define a closed date range for accurate period-bound reporting.

4. Example API Request

GET /analytics/pages/aggregated?dateStart=2026-04-01&dateEnd=2026-04-30

This request returns aggregated page analytics for the month of April 2026 only. Without dateEnd, the query would return data from dateStart through the current date at time of request, producing non-reproducible results between runs.

5. Impact on Audit Reporting

Prior to v60.0.0, analytics API queries lacked a reliable end-date boundary, meaning that a report generated on May 1 and the same report generated on May 15 would return different totals for the same 'April' query. This introduced data integrity concerns for:

  •   Period-close engagement reports.
  •   Audit evidence exports tied to specific SOC 2 review windows.
  •   Automated BI dashboards with scheduled refresh cycles.

With dateEnd, all of the above scenarios produce deterministic, reproducible results, satisfying accuracy and completeness requirements for audit evidence.

6. API Documentation Reference

Updated Swagger / public API documentation reflecting the dateEnd parameter has been published as part of v60.0.0 (TD-6625). Refer to the Tiled Developer Portal for the full endpoint specification.

8. Change History

v1.0 — May 5, 2026

Initial article. Parameter shipped in Tiled v60.0.0 (TD-6616). API docs updated via TD-6625.