# Activity: Wait for Event

'Wait for Event' is an activity available in Campaign > Flow that allows an operator to execute an action after a specific event or redirect the user if the time for completion passes (timeout).<br>

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-ad6dccc9427b388bc481de93fe542ffd49078f0d%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

Operators can define for how long to wait, either using relative time or a specific date/time, in the delay settings.<br>

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-c24ff916fc227a67a6cdc0e7a03f522b3d934772%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Delay Options**

Time to wait - can be set to a maximum time in seconds, minutes, hours, or days.\\

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-4b0c6094912899efa46a9fc8faf9c3dd4adb8269%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

Delay till - can be one of the following options:<br>

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-0f0501a9921bfd5c8adb4d41997e8efd898f65ce%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

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.

#### **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**).

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-4012dff76b760d027c4402a2daf916dd049d5ada%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-d6de0d68784fc6e3d8b4b57a49d26e737b80f841%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

Then, Operator should use the same Event within “Check user profile” or “Multiple check” activity and the relevant payload:<br>

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-8a352dafc48dce659bf2fa1c66e5264fc907e35d%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

<br>
