Dynamic Monetization Enhancements in 2024.12

The following enhancement for Dynamic Monetization was added in the 2024.12 release.

Elastic Access Timezone-Tolerant Enforcement of Start and End Dates

Because Elastic Access operates in the UTC timezone, client software running elsewhere may not be able to use a full 24 hours in the start day of a line item, or in the expiration day.

For example, end customers using client software in Adelaide will be ten and a half hours ahead of Elastic Access. If there is a new line item with a start date of 2025-01-08, the customer will have to wait nearly half a day until 2024-01-08 arrives in UTC and the line item allows tokens to be consumed.

A similar impact is experienced by customers in western locations (e.g. San Diego, California), losing eight hours of their day when the line item expires.

Timezone tolerance assumes all customers are in the east-most location for the start date of a line item, and west-most location for the expiration date. It therefore grants an extra half a day of usage at the beginning and end of a line item's duration to ensure customers' productivity is not interrupted.

Timezone tolerance is controlled using the timezone.tolerant value of the /configuration API. By default, timezone tolerance is disabled. For more information, see the topic Configuration Values in Dynamic Monetization in the Dynamic Monetization User Guide.