# Set your key events

Source: https://kirora.io/docs/guides/goals/key-events

Tell Kirora which of your events mean a sign-up, a transaction, a cancellation or a refund, so goals and Kiro AI can read them.

Key events are the events that matter most to your business, such as a transaction or a sign-up. Common goals, customer groups, value totals and Kiro AI's tasks read them, so set them once in **Settings › Workspace › Key events**.

## The key events

- **Transaction and activity**: what counts as a transaction (an order, a subscription payment, a deposit or a repayment), the property that holds its amount, and what shows a customer is still active.
- **Sign-up and onboarding**: **Sign-up**, **Verified** and **Trial started**.
- **Subscriptions**: **Became paying**, **Cancelled** and **Payment failed**.
- **Checkout and refunds**: **Checkout started** and **Refund**.

For each, enter the event your app sends, or choose **We don't track this**. Events reach Kirora through the API, the SDKs or a connected integration such as your payment provider.

## Why they matter

- **Common goals** are measured from them, so most need nothing more than choosing which ones count. A goal whose event has never arrived shows **Needs data** and names what to send.
- **Revenue goals** are offered only when your transaction event carries an amount.
- **Kiro AI's tasks** about purchases read the transaction event and amount. When a task needs an event you don't send yet, it says which one. See [Kiro AI tasks](https://kirora.io/docs/guides/kiro-ai/kiro-tasks).

> **Tip:** Event names must match exactly what your app sends, including case. Check the names your developer uses before you fill these in.

## Next steps

- [Create a goal](https://kirora.io/docs/guides/goals/create-a-goal)
- [Track events from your app](https://kirora.io/docs/api/events)