RudderStack Event Specification

Learn the fields and properties associated with the standard RudderStack API methods.

The RudderStack Event Spec outlines how to send event data to RudderStack’s APIs and the proper format to capture events using RudderStack’s SDKs.

The RudderStack Event Spec supports multiple API calls that make it easy to identify users and track their specific actions as events. Using the correct format to capture events ensures that RudderStack can automatically forward those events to any of our supported destinations.

Supported API calls

The RudderStack API spec supports the following calls, each gathering important data about the user:

API callDescription
IdentifyThe user’s identity
PageWeb page details of the user’s current page
ScreenApp screen details
TrackDetails of user actions (for example, Clicks, Sign ups, and Purchases)
GroupGroup or organization details
AliasMerge identities to a known user
MergePerform identity resolution by associating different identifiers to a given customer profile in the warehouse (Deprecated)
ResetResets the information related to the previously identified user
warning
Refer to the corresponding SDK documentation for the implementation specifics of the above calls.

Send sample events

Use RudderStack’s Event Playground app to send sample events to RudderStack and test the data flow without any instrumentation.

Select the relevant API method from the dropdown and click Send to see the API call in the Network tab of your browser’s developer tools.

To send test events to your account:

  1. Sign in to RudderStack dashboard. Note the data plane URLThe data plane URL is the location where events are routed and sent to the RudderStack backend for processing. You can find this URL in the home page of your RudderStack dashboard. at the top of the default Connections page.
  2. Set up a source and note its write keyThe write key (or source write key) is a unique identifier for your source. RudderStack uses this key to send events from a source to the specified destination. .
JavaScript source write key
  1. Click Use My Account in the Event Playground app and specify the write key and data plane URL.
  2. Click Save.
  3. Select the required API Method from the dropdown, edit the relevant fields or traits/properties, and click Send to my account.
  4. To verify the data flow, go to the Live Events viewer of your source.

How the API calls work

Here’s a quick overview of how the API calls work:

  1. A customer interacts with your website/app triggering an event.
  2. When an API is called, the event data is sent to the RudderStack backend.
  3. RudderStack transforms the event data into a destination-specific format.
  4. The transformed data is then sent to all requested destinations.

Event data format

The event data is collected in JSON and includes the Common Fields along with API-specific fields.

It is strongly recommended large integer values be passed as strings. This ensures that the values are correctly transmitted to all systems (including various downstream destinations) without any issues.

RudderStack follows the RFC 7159 standard which has an upper limit of 253 for integers. If the values passed exceed this number, you may lose precision. Furthermore, certain downstream destinations have their own limitations on parsing large integer values.

Industry Specs



Questions? Contact us by email or on Slack