> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-wait-for-event.md).

# Activity: Wait for Event

**Wait for Event** is an activity in Campaign > Flow that waits for one event of the player. When the event happens, the player continues on one branch; when the waiting time runs out first (timeout), the player continues on another.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fk0NdCRibGnKCbIyKYXI0%2Fwfe-canvas-ba717a4b-9956fd.png?alt=media" alt="Wait for Event on the canvas"><figcaption><p>The branches of Wait for Event. The menu that opens when you click the activity calls them 1 — Happen and 2 — Timeout; on the canvas the first one is shown as 3 — When happened</p></figcaption></figure></div>

In the activity, choose the **Event to wait**. Below it you can add conditions on the data of that event, for example a minimum deposit amount. Then, in **Delay options**, choose how long to wait: **Time to wait** (a length of time) or **Delay till** (a point in the calendar).

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FwRXJytjQ8XdgsqoY3NOC%2Fwfe-form-b22737df-6bb1ca.png?alt=media" alt="Wait for Event settings"><figcaption><p>1 — the event to wait for; 2 — conditions on the event data; 3 — how long to wait</p></figcaption></figure></div>

#### **Delay Options**

**Time to wait** — set **Maximum time to wait** in seconds, minutes, hours or days, from 5 seconds up to 30 days.

**Delay till** — the **Wait till** field offers eight options: **Exact date**, **Day(s) of week**, **Specific day(s) of month** and **Specific days**, each in UTC or in the user timezone. For an exact date you pick a **Date**; for the others you set a **Schedule**.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2F7wv7iOtY7dvJOWiKjzL7%2Fwfe-wait-till-7cfa2299-d014d3.png?alt=media" alt="Wait till options"><figcaption><p>1 — the options of Wait till</p></figcaption></figure></div>

For example, an Operator can create a campaign that triggers when a player makes a deposit above an exact amount, then add specific 'Wait for Event' to happen, and delay the execution until a particular date (or day of the week) in the delay settings.

### Outgoing connections

The Wait for Event step has two outgoing connections:

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2F9P8uJjZfv9dO4Z3zYxZS%2Fb55d364b9a-wait-for-event-a3900a5d-a7a4a9.png?alt=media" alt="Outgoing connections"><figcaption><p>Outgoing connections of Wait for Event in a flow. The numbers match the table below.</p></figcaption></figure></div>

| # | Connection                             | When the player goes this way                                                                                                                                                             |
| - | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | **When happened (Happen in the list)** | The player did the event, and it matched the conditions, before the waiting time ran out. The player goes on at once.                                                                     |
| 2 | **Timeout**                            | The waiting time (**Maximum time to wait** or the **Delay till** moment) ran out first. With no Timeout connection, the step just ends there and the player goes no further on this path. |

### Campaign Duration and Timing Considerations

* **Campaign Duration Setting**: Ensure the overall **Campaign Duration** in the campaign settings is longer than the waiting time configured in your **Wait for Event** activity. If the campaign duration expires while a user is waiting, the campaign terminates for that user immediately and they will not reach the **Timeout** branch.
* **Real-Time Evaluation Only**: **Wait for Event** only listens for events that occur *after* the user enters the wait activity. Past events that took place before the user reached this step are not evaluated.

### Time zones

When you use **Delay till** with a user timezone option, the wait ends at that time in the player's own time zone (taken from their last session) instead of UTC.

#### **Use Case Scenario**

The **“Wait for Event”** activity can be used in various situations.

For example, in a Promo Code campaign, after a user is shown the popup, the **“Wait for Event”** step can be added that triggers only after a specific action - such as **“Core: Client Action.”**

In this case, the client action would be the user entering the promo code (e.g., **WIN100**).

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FGFUvR6v4VnpL4nfYMoCE%2Fc5e209c5a4-wfe-11-5d01f250-c5c384.png?alt=media" alt=""><figcaption><p>Example: a promo code journey. Wait for Event comes after the popup</p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fe0KEuAhWtRMjRMRDUJz9%2F7f6e5fe3d8-wfe-12-2b7045d8-b46013.png?alt=media" alt=""><figcaption><p>Wait for Event waits for Core: client action with the promo code</p></figcaption></figure></div>

You can configure conditions on the event payload (such as promo code, transaction amount, or custom parameters) directly inside the **Wait for Event** activity, below **Event to wait**, without needing an additional check activity.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FTh5UC8eMdq81ZJ7WCBhz%2F1d7e3ad6e7-wfe-13-952e7123-ee5691.png?alt=media" alt=""><figcaption><p>The same check done in a separate Multiple check activity, after Wait for Event</p></figcaption></figure></div>

### Frequently Asked Questions

**Q: Does Wait for Event trigger on events that happened before the user reached this step?**

No. The activity only listens for events that occur while the user is actively waiting at the node.

**Q: What happens if a user produces the awaited event, but it does not match the condition rule?**

The user remains in the wait step. They will only advance down the **When happened** branch when a matching event occurs, or move to **Timeout** if the deadline passes first.

**Q: Why did users get stopped instead of progressing to the Timeout branch?**

Check your campaign's overall **Campaign Duration** setting. If the campaign duration is shorter than the activity's wait time, the campaign terminates the user before the activity timeout can execute.

**Q: Can a single Wait for Event activity wait for multiple different event types?**

No. Each Wait for Event activity waits for one event type. To wait for several events, use one Wait for Event activity per event, or separate campaigns.

### Related Documentation

For more information on flow activities and condition building, see [Activities of Flows](/welcome/products/crm-automation/activities-of-flows.md) and [Query Builder](/welcome/products/crm-automation/segmentation/query-builder.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-wait-for-event.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.