Integrations and API
Send server-side events
Record trusted product and transaction activity through the Events API.
Last updated August 20, 2026
Before you start
- An API key
- A stable event name and trusted identity context
How to do it
- 1
Use the Events API for backend-confirmed product or transaction activity.
- 2
Include the event time, stable identity, and only the properties needed for analysis.
- 3
Send externalSessionId for an app visit. More than 30 minutes without activity starts another visit. Delayed events use the time they happened.
- 4
Omit externalSessionId for background actions. The event stays visible without a visit and the response contains sessionId: null. Visit counts may fall because background events no longer create visits.
- 5
Retry an action with the same eventId, site, and event name. An explicit dedupeKey takes precedence and must remain unchanged. Check the saved event in Realtime.
What to check
- The event appears once with the expected timestamp
- It links to the correct canonical visitor
- App visit events share one visit. Background actions remain visible without adding visits or active visitors.