Engagement Scheduler

Updated 2 months ago by Michael Alon

Engagement Scheduler

Every engagement has a scheduling step that helps you defined when and how often an engagement should be evaluated and triggered. In-app scheduling is a little different than Email scheduling due to the different nature of these engagement channels, for example Email can be a great way to reach out to users after they are no longer in your app and driven by a predefined schedule whereas in-app will always be triggered by users when using the app.

In-App Engagement Scheduler

Triggering in-app guides, announcements or surveys are defined by two main elements: Scheduler and Qualification Scope

Scheduler: date range for the engagement

  • From: a date range where the in-app engagement will be active 24/7
  • Advanced: Recurring is optional in case you would like to hide/show on different hours within the range

Qualification Scope: how often (thresholds) for when a user will see an engagement

  • Only Once: Choosing this scope means the user will see the engagement a single time across any number of visits under the specified date range
  • Once per visit: Choosing this scope means the user will be qualified once per visit, mostly used for 'continues critical announcements' or testing purposes.
If user is Inactive for 30 minutes, Gainsight PX automatically resets it to a New Visit/Session.
  • Every Time (Every Event): Choosing this scope means the user will be qualified on every event level, mostly used for 'Paywall or access control'.
For Every Time (Every Event) tracking usage: Gainsight PX tracks all events once per visit. For example, if the user completes NPS Survey multiple times, Gainsight PX considers and counts it only once.
  • Show Attempts: Choosing this scope means the user will see the engagement every hours/days/weeks/months and will be snoozed x times between these intervals.

Email Engagement Scheduler

Triggering emails are defined by two main elements: Scheduler and Qualification Scope. In case of outbound channels like Email, the actual qualification is happening before the email is being queued up. The system automatically runs the audience match a few hours before the scheduled time so the sending time is as accurate as possible.

Scheduler: date range for the engagement

  • At: specified date where the email engagement will be triggered and evaluated against the audience criteria
  • Advanced: Recurring is optional in case you would like to specify recurring engagement which also provides greater granularity

Qualification Scope: how often (threshold) for when a user see an engagement

  • Only Once: each user will be qualified a single time only regardless if the audience will match more than once.
  • Every Time: each user will be qualified against the audience rules every time the scheduler is set.
  • Once Every: each user will be re-qualified every hours/days/weeks/months interval period.
IMPORTANT: Email engagements cannot be triggered by events; these are only time-based. For example, PX cannot launch an email upon clicking any button and page visits. You can trigger the email only by using the Schedule and Qualification Scope.


How did we do?