Unique customer ID. This can be

• The Antavo customer ID
• An external ID (requires configuration): {external_field:external_id_value}

Unique transaction ID

"The events history can be filtered by submitted event actions using operators. Refer to API events and internal events lists.
This filter query can be used in conjunction with the operators listed here. The filter should be submitted as a parameter in the following format: field.operator(optional)=value.

Filtering of events containing a transaction_id is also possible. This requires the action query to contain all related events and for an additional query using properties.transaction_id.
Example:
action.in=checkout,checkout_accept&properties.transaction_id.in=c078c162-88af-4369-89a4-408958a8cb75.
These combined filters can also use filtering operators.
The transaction_id field in any custom event must be set as filterable."

The events history can be filtered by a specific date. Specific start and/or end dates can be stated by using multiple operators. E.g.,

date.gt=2020-01-01&date.lt=2022-02-01

UTC timezone should be considered when sending the request.