> For the complete documentation index, see [llms.txt](https://docs.enable3.io/enable3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enable3.io/enable3/system-events.md).

# System Events

### Overview

**System Events** are predefined user actions tracked by default to help you build flexible and engaging mission flows, without API integration.\
They **lower the barrier** to launching retention-focused missions, especially for **non-technical teams or no-code clients.**

System Events help you shape meaningful user behaviors from Day 1:

* **Referral** → encourage acquisition through peer invites and community growth
* **Widget Open** → launch missions to boost return visits and habit formation
* **Hold to Earn** → reinforce core staking actions by rewarding both volume and frequency

***

### Setup and Use

#### Installing System-Based Events

When the Event-Based Missions feature is installed, 3 System Events are automatically added to the Events tab:

1. Hold to Earn
2. Referral
3. Widget Open

{% hint style="success" %}
System Events are created automatically, but [depend](#feature-dependencies) on the related feature being installed and active.
{% endhint %}

<figure><img src="/files/6ALZLKB54WcKMMx27g1g" alt=""><figcaption><p>System Events (Events tab)</p></figcaption></figure>

#### Using System Events in Missions

After installation, System Events become selectable in the mission builder under the **“Choose Event”** field.

<figure><img src="/files/QFcquSRHF9YBLjJM9vQ8" alt="" width="332"><figcaption><p>Selecting Systems Events (Missions creation page)</p></figcaption></figure>

You can build missions around these events using either:

* **Count of Events** (number of times the event occurred)
* **Amount of Events** (total value associated, available for Hold to Earn only)

<details>

<summary>Feature dependencies</summary>

* **Hold-to-Earn** and **Referral** events are tied to their respective features.
* These System Events:
  * Will be available only if the related feature is installed.
  * Will be removed from the Events list if the feature is uninstalled.
  * Will also disappear from the mission builder and become unavailable for new missions.

{% hint style="warning" %}
If there is an **active mission** using Referral or Hold to Earn events, and the related feature is later uninstalled, the mission will **remain visible on the widget** but cannot be reused or edited with that event type.
{% endhint %}

</details>

<details>

<summary>Events behavior &#x26; rules</summary>

* System Events **appear at the top** of the Events list.
* They are **Active by default** after installation.
* **Editable & Translatable** — You can customize names and labels.
* **Status toggle is enabled** — You can deactivate them.
* **Deletion is disabled** — You cannot remove System Events.

</details>

***

### System Event-based Missions examples&#x20;

> :link: **Referral** System Even&#x74;**:**&#x20;
>
> Mission **—** *"Invite 5 friends"*
>
> * Encourages viral sharing and network growth
> * **Condition:** Count of Events = 5

> :star: **Widget Open** System Even&#x74;**:**
>
> Mision **—** "*Visit the widget for 5 days in a row"*
>
> * Builds a usage habit and increases daily engagement
> * **Condition:** Count of Events = 5
> * **Enable** “Count once per day”

> :coin: **Hold to Earn** System Event:\
> Mission — "*Make 5 Stakes"*&#x20;
>
> * Reinforces regular interaction with the staking feature
> * **Condition:** Count of Events = 5

> :coin: **Hold to Earn** System Event:
>
> Mission — *"Stake 10,000 tokens" —* Drives higher value activity and deeper commitment
>
> * **Condition:** Amount of Events = 10,000