EventProperties
A flexible key-value map for custom event properties.Properties
Dynamic properties that can be attached to any event. Keys are strings, and values can be strings, numbers, booleans, null, or undefined.
AnalyticsEvent
The core event structure used internally by the SDK.Properties
Unique identifier for this event.
Unix timestamp (in milliseconds) when the event occurred.
Type of event. Possible values:
track, page, identify, alias, heatmap, session, error, subscription, payment.Name of the event (e.g., “Button Clicked”, “Form Submitted”).
Custom properties associated with the event.
The identified user ID if available.
Anonymous identifier for the user, generated automatically if no userId is set.
Unique identifier for the current session.
Contextual information about the event:
page(PageProperties): Page-related informationuserAgent(string): Browser user agent stringtimezone(string): User’s timezonelocale(string): User’s localescreen(object): Screen dimensions (width, height)library(object): SDK information (name, version)performance(PerformanceData): Performance metricsheatmap(HeatmapData): Heatmap interaction datasession(SessionData): Session informationerror(ErrorData): Error details
BackendEvent
Backend-compatible event structure for API submission.Properties
Unique identifier for the event.
Type/name of the event being tracked.
The user’s ID if they are identified.
Current session identifier.
ISO 8601 formatted timestamp string.
Custom properties for the event.
Browser user agent string (auto-extracted by backend).
User’s IP address (auto-extracted by backend).
PageProperties
Properties specific to page view events.Properties
Page title from the document.
Full URL of the page.
URL path (without domain).
Referrer URL that led to this page.
Query string parameters.
UserProperties
Properties for identifying users.Properties
User’s subscription information.
Additional custom user properties.
PaymentEventProperties
Extended properties for payment-related events.Properties
Payment amount in cents.
Currency code (e.g., “usd”, “eur”).
Status of the payment. Possible values:
succeeded, failed, pending, refunded.Reason for payment failure, if applicable.
Associated invoice identifier.
Payment processor charge identifier.
ConversionEvent
Event data for A/B test conversions.Properties
ID of the experiment this conversion is associated with.
Name of the conversion event.
Numeric value associated with the conversion (e.g., revenue).
Additional properties for the conversion event.