Events with the same transactionId are only processed once. If you send the same event twice, Fynn returns the existing event instead of creating a duplicate.
Use deterministic transaction IDs, e.g.: ${customerId}-${timestamp}-${eventName} or UUIDs.
Properties for Nutzungsmetriks
The properties object should contain all fields your Nutzungsmetriks need:
Nutzungsmetrik
Aggregation
Required Property
Token Usage
Sum
tokens_used
API Calls
Count
- (counts events)
Storage
Latest
storage_gb
Active Users
Unique Count
user_id
Grouping Properties
If your Nutzungsmetrik uses groupBy, include those fields:
{ "properties": { "tokens_used": 350, "model": "gpt-4", // groupBy field "region": "eu-west-1" // another groupBy field }}
Filter Properties
If your Nutzungsmetrik has filters, include the filtered fields: