You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/docs/api.mdx
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -316,7 +316,7 @@ Track custom events programmatically using the basket endpoint.
316
316
317
317
**Required Fields:**
318
318
-`type`: Must be "custom"
319
-
-`eventId`: Unique identifier for the event (max 512 characters)
319
+
-`eventId`: Unique identifier for the event (max 512 characters) - used for deduplication (auto-generated if empty)
320
320
-`name`: Event name (1-128 characters)
321
321
322
322
**Optional Fields:**
@@ -329,6 +329,10 @@ Track custom events programmatically using the basket endpoint.
329
329
**Simple tracking**: For basic event tracking, you only need `type`, `eventId`, and `name`. The `anonymousId` and `sessionId` are useful for user journey tracking but not required for simple conversion or action tracking.
330
330
</Callout>
331
331
332
+
<Callouttype="info">
333
+
**Event ID Generation**: The `eventId` is a custom string you provide for deduplication. It can be any unique identifier (UUID, timestamp-based, etc.). If you send the same `eventId` twice, the second event will be ignored. This prevents duplicate events from network retries or accidental double-sends.
0 commit comments