# Learn events spec



The _Krenalis Event Specs_ explains what to send when you track events. SDKs handle delivery, but this spec keeps names, fields, and types consistent across web, mobile, and backend so your data stays clean and comparable. Read it to keep your events consistent, debug faster, and let downstream tools work without extra fixes. The rules apply no matter how you send data—via SDKs, backend services, batch jobs, or direct API calls—because the schema is the same in every case.

Calls are requests to the standard event methods:

* [**Page**](https://www.krenalis.com/docs/collect-events/spec/spec/page.md)\
  Answers: *Which web page did they view?*\
  Use when: a web route or URL loads or changes on the client.

* [**Screen**](https://www.krenalis.com/docs/collect-events/spec/spec/screen.md)\
  Answers: *Which app screen did they view?*\
  Use when: a native view opens on iOS, Android, desktop, or TV apps.

* [**Track**](https://www.krenalis.com/docs/collect-events/spec/spec/track.md)\
  Answers: *What did the user do?*\
  Use when: meaningful business pipelines. Examples: "Product Viewed", "Checkout Started", "Order Completed".

* [**Identify**](https://www.krenalis.com/docs/collect-events/spec/spec/identify.md)\
  Answers: *Who is the user?*\
  Use when: login, signup, profile updates, plan changes, consent updates.

* [**Group**](https://www.krenalis.com/docs/collect-events/spec/spec/group.md)\
  Answers: *Which account or organization is the user part of?*\
  Use when: the user is linked to a company, workspace, or team, or their roles within the group change.

## Event schema

The [event schema](https://www.krenalis.com/docs/collect-events/spec/spec/schema.md) defines the structure of an event, similar to how the profile schema (Customer Model Schema) defines the structure of a user.
Unlike the profile schema, which can be customized for each organization, the event schema is predefined. See more about the [event schema](https://www.krenalis.com/docs/collect-events/spec/spec/schema.md).