Create scheduled tasks

Last updated 10/03/2026

Entry: Go to Engage > Operation Tasks > Create task > Select the Channel Type > Webhook / Push Notification > Select a channel to open the operation task editing page.

Note: Client-side Reach channels don't support creating scheduled tasks yet.

1. Push timing

Multiple push timing types are supported. You can choose scheduled, manual, or behavior-triggered push timing as needed, and configure more push settings for each push timing type, such as approval timeout handling and task entry limits.

1.1 Scheduled - One-time

• Scheduled - One-time

For tasks that run once and push at a fixed time, such as reminding users at 12:00 noon to log in and claim stamina.

You can configure approval timeout handling, which takes effect when approval isn't completed before the push time

• End automatically on timeout: If the task isn't approved before the push time, the operation task ends automatically
• Push immediately after approval: The task can still be approved within 48 hours after the push time, and it's pushed immediately once approved

If you push based on the user time zone and choose to end automatically on timeout, we recommend that you submit the task at least 24 hours in advance. Otherwise, the operation task ends automatically.

1.2 Scheduled - Recurring

• Scheduled - Recurring

For tasks that run repeatedly and send at one or more specified times within a specified period, such as reminding users at 7:00 PM every Friday, Saturday, and Sunday of each calendar week during an anniversary event month to log in and join the event.

• You can set the task to repeat daily, weekly, or monthly

• You can set task entry limits to reduce ineffective reach (task entry limits cap the maximum number of pushes each user can receive from this task within a period of time). You can choose:

  • The maximum number of pushes a user can receive within a single task schedule
  • The maximum number of pushes a user can receive within X days (a sliding window; for example, only once within 7 days means only once within the last 7*24 hours)
  • The maximum number of pushes a user can receive within each X days, weeks, or months (a rolling window; for example, once per week means only once within each calendar week)

warning

If your product is released globally, you can choose to base the push time on the user time zone when you configure it. Pushes are then sent at the corresponding time in each user's time zone, based on the user's time zone property. (To push based on the user time zone, turn on multiple time zones for the project and configure the user time zone property in Project Management - Project Time Zone.)

1.3 Manual push

For push tasks that run manually. After approval, you can choose the push time freely, for example, to quickly push related content at the moment the final result of an offline tournament is decided.

2. Audience

Rich audience selection features are supported. You can use a custom audience to select users by user properties or tags and by user behavior events, or directly select an existing cohort. You can also estimate the audience size to assess how many users the operation task may reach.

2.1 Select the audience

• Custom Audience:

Combine filters on user properties or tags with filters on user behavior events using "AND" or "OR" logic, and then exclude existing cohorts.

• User Conditions (user properties, user cohorts, or tags): Combine multiple properties, cohorts, or tags with And or Or logic
• User Behaviors (User behavior event or sequence): Combine multiple behaviors with And or Or logic
• Exclude: Exclude users with certain properties, or multiple existing cohorts, from the audience

• Existing Cohort:

  • You can directly use the selectable existing cohorts of the project
  • About "selectable": For projects with multiple time zones turned on, the cohorts selectable in an operation task are those whose time zone is the same as the task time zone (ID cohorts and result cohorts have no time zone restriction and can all be used). For more information about task time zones, see Operation task time zones

2.2 Estimate audience size

After you set the audience conditions, you can click Estimate to estimate the number of target users and assess how many users the operation task may reach.

To keep the estimate as close to the actual value as possible, the estimate counts target users who meet the audience conditions and whose push ID for the selected channel is not empty (that is, users who can actually receive the push).

3. Push configuration

3.1 Turn on A/B testing

In push configuration, you can turn A/B tests on or off, turn delivery caps on or off, and set the operation task whitelist. For more information about A/B tests, see A/B testing

3.2 Delivery caps

When multiple operation tasks use the same channel type (channel), you can limit the maximum number of pushes a single user receives from the same type of channel within a period of time, to avoid disturbing users too often.

3.3 Whitelist

Whitelisted users receive every push of an operation task. As an operator, you can add your own account to the whitelist to monitor every push of the task. For more information about whitelists, see Whitelist management

4. Push content

Based on the selected channel, you can fill in suitable message content according to your operation strategy and insert user properties to personalize the copy. You can also run a send test right away to preview and confirm the push effect, and turn on delivery caps or set a task whitelist as needed.

4.1 Multi-language support

If your product is released globally, you can configure multiple language versions of the push content. When pushing, the language version is matched based on each user's language property. (To use multi-language features, configure the User Language Property in Settings - Localization Settings.)

In addition, to make configuration more efficient, when you add languages, the content entered for the default language is automatically synced to the content of the other languages.

4.2 Personalized content

You can insert user properties into the message content as needed to personalize the push. For example, if you insert the user nickname property into the message content, the message that each user receives will include their nickname.

4.3 Send test

Before you submit the task for approval, you can use Send Test to preview the push content of the operation task and make sure it's correct.

• Send tests can verify the push content and channel custom parameters
• If you insert user properties into the push content, the Default Value of each user property is used as the send test content
• Channel custom parameters use their Default Value as the push content. If there's no default value, you can enter the content you want to test

5. Goal settings

A conversion is counted when a reached user completes the specified event behavior. Conversions are used to evaluate the effect of the operation task.

You can set one main goal and two secondary goals at the same time.

6. Metric settings

You can set metrics for performance after any reach node to help evaluate the operation effect.

For details, see Task performance analysis