The RudderStack Event Spec helps you plan your event data and provides various options for tracking your events across all the RudderStack SDKs and APIs.
Supported API calls
The RudderStack API Spec supports the following calls, each answering a pertinent question about the user:
| API call | Description |
|---|---|
| Identify | Captures the visiting user's details. |
| Page | Captures the details related to the web page that the user is currently on. |
| Screen | Captures the details related to the app screen that the user is currently viewing. |
| Track | Captures information related to the user's actions. |
| Group | Captures details about the group or organization that the user is a part of. |
| Alias | Lets you merge different identities of a known user. |
| Merge | Lets you perform identity resolution by associating different identifiers to a given customer profile in the warehouse. |
| Reset | Resets the information related to the previously identified user. |
How the API calls work
Here's a quick overview of how the API calls mentioned above work:
- When the user makes the API calls, the event data is sent to the RudderStack backend.
- RudderStack transforms this event data into a destination-specific format.
- The transformed data is then forwarded to the required destination.
Event data format
The event data collected by RudderStack has a JSON structure, which has the Common fields and an API-specific payload.
RudderStack follows the RFC 7159 standard which has an upper limit of 2 53 for integers. If the values you pass in your events exceed this number, they may lose precision. Furthermore, certain downstream destinations might have their own limitations on parsing such integer values.
Contact us
For more information on the topics covered on this page, email us or start a conversation in our Slack community.