Application Usage Report Exceeds the Defined Date Range

This article explains why the Application Usage Report may return entries that appear to be outside the selected date range.

• For example, a report generated for May 1 to May 31 might include an entry from April 30.

• Reports

The discrepancy occurs due to a difference in time zones. The API query for the report uses the user's local timezone (for example, UTC+2), while the event timestamps within the report are recorded in Coordinated Universal Time (UTC), also known as Zulu time. An event recorded late in the day in UTC (for example, 2025-04-30T22:23:21Z) may fall within the start of the next day when converted to the local timezone of the query (for example, 2025-05-01T00:23:21+02:00), causing it to be correctly included in the report.

This is functioning as designed. To confirm this behavior, analyze the API request and the timestamps involved.

1. Retrieve the API request generated by the report.
2. Decode the URL to view the filter parameters. A decoder tool can be used for this step. The raw URL may appear similar to this:
   /api/v1/analytics/reports/application-usage/exports?filter=eventTimestamp+ge+%222025-05-01T00%3A00%3A00%2B02%3A00%22+and+eventTimestamp+lt+%222025-06-01T00%3A00%3A00%2B02%3A00%22+and+appInstanceId+eq+%22<appInstanceId>%22
3. The decoded URL shows the exact timestamp filters, including the timezone offset:
   /api/v1/analytics/reports/application-usage/exports?filter=eventTimestamp ge "2025-05-01T00:00:00+02:00" and eventTimestamp lt "2025-06-01T00:00:00+02:00" and appInstanceId eq "<appInstanceId>"
4. Note the timezone supplied to the filter (for example, +02:00).
5. Compare this with the timestamp of an entry that appears to be outside the range (for example, 2025-04-30T22:23:21Z). The Z indicates the time is in Zulu (UTC).
6. Convert the Zulu timestamp to the filter's timezone to confirm it falls within the requested range. A time zone converter can assist with this conversion.
   • In this example, 2025-04-30T22:23:21Z is equivalent to 2025-05-01T00:23:21 in a +02:00 timezone.