Event Timestamp - iGamingXpert

An event timestamp records when a business action actually occurred, rather than when a tracking platform received the message. It determines the event's reporting period and helps align deposits, bets, and commission rules across systems that receive data at different speeds.

Practical example

Illustrative example: A deposit occurs at 23:58 UTC but arrives at 00:04; its event date remains the previous day.

Scaleo application: integration pattern

For a Scaleo integration, treat event timestamp as a requirement at the operator-to-tracker or reporting boundary. Agree which system owns the behavior and test it against the current endpoint contract; the workflow described here does not assert a dedicated native Scaleo feature.

Frequently asked questions

What should you check before using event timestamp?

Record the timezone and clock source so that a late delivery does not silently change the business date.

What is a practical example of event timestamp?

A deposit occurs at 23:58 UTC but arrives at 00:04; its event date remains the previous day.

Scaleo integration reference. Verify the endpoint contract and configured features for your implementation.

Apply the term in context

For the broader operator context, read what is iGaming. Review payment processors for online casinos when tracing the player funding journey. To compare the commission assumptions in a worked scenario, calculate RevShare profitability.