Glossary term

Ingestion Timestamp

An ingestion timestamp records when a system accepted an incoming event into its processing pipeline. Comparing ingestion time with event time measures delivery delay and separates transport problems from business inactivity when affiliate dashboards appear to be missing recent deposits or conversions.

Practical example

Illustrative example: An event generated at 14:00 and ingested at 14:03 has a three-minute ingestion delay.

Scaleo application: integration pattern

For a Scaleo integration, treat ingestion 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 ingestion timestamp?

A fast ingestion time does not prove that validation, commission calculation, or reporting has finished successfully.

What is a practical example of ingestion timestamp?

An event generated at 14:00 and ingested at 14:03 has a three-minute ingestion delay.

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.

Applying this in an affiliate program? See affiliate tracking platform options.

See this metric live in your own program: explore iGamingXpert browse the full glossary