Usage events are the units in which product usage is measured
eventType
is the top-level category for the event, and describes at a high level what happened. Only events of the same type can be aggregated together via usage metrics. Think of event types
as mutually incompatible categories that should not be mixed in aggregations. If you have slightly different events that you might want to combine in the same metric, give them the same event type,
and rely on event properties to distinguish them.
customerAlias
identifies the customer that the event belongs to. It can be either:
eventTimestamp
determines the billing period in which this usage will be charged.
customerEventId
is a unique identifier for the event that you can optionally set, and is otherwise auto-generated by Sequence.
If multiple events with the same customer event ID are received, only the last one will contribute to usage metric calculations.
eventProperties
are arbitrary key-value pairs providing additional metadata for the event.customerEventId
.
The original event will still exist in Sequence, but future metric calculations will only take the
last received event into account.
customerEventId
and update its customer alias to VOID
. Alternatively, you can also adjust the timestamp to fall outside any billing periods or change the amount
to zero (in the case of a transaction event).