Playbook entry and goal conditions: use cases


Overview

While journy.io's Playbooks have been created with simplicity in mind, there are still quite powerful Playbook (entry/goal) conditions that can be set.

Here are some most common use cases.

Event-, screen- and page-based conditions

journy.io supports Playbook entry and goal conditions to include event, screen or page tracking information. So conditions can be build for specific events, screens or pages:

  • when they occurred [in given period of time]

  • when they occurred at least x times [in given period of time]

  • when they occurred at most x times [in given period of time]

  • when they specifically did not occur [in given period of time]

image-20240417-093406.png

Running time-window conditions

Lets dive into the '[in given period of time]' part of conditions.

journy.io supports a wide range of running time-windows, relative to current date-time ('now'). The time-window can hold fix-days length as well as fix-references.

In following example, let's say that today is May 13th 2023:

Time condition

Begin & end date

Desciption

Today

May 13th 2023, from 0:00:00.0000 till 23:59:59.9999

Today

Yesterday

May 12th 2023, from 0:00:00.0000 till 23:59:59.9999

Yesterday

Last 30 days

April 14th → May 13th 2023

Last 30 days, until today

Last Month

April 1st → April 30th 2023

The first and last day of the month, previous to this month, relative to today.

This Month

May 1st → May 31st 2023

The first and last day of the month, relative to today.

There are similar conditions for:

  • last 7 days, this week, last week

  • last 90 days, this quarter, last quarter

  • this year, last year

ANY event, screen and page condition

journy.io does not have the concept of directly selecting 'any' event, screen, page in the respective event, screen or page condition. Instead, there's a single date-time property 'Last activity at' that is being updated each time an event, screen or page tracking is performed.

As such, if you want to know if someone wasn't active for the last 7 days, your condition would look like:

image-20240417-093446.png

Time-related conditions

journy.io supports creating time-based conditions with rules that can be compared before, during or after, both past and future date-time references.

Before, during and after future references

Imagine that you want to take action when a renewal is up for, lets say in the next 7 days. This is how you would construct the condition:

 

Before, during and after past references

Imagine that you want to take action 3 months after registration. This is how you would construct the condition:

Multi-account-multi-user B2B Playbook conditions

journy.io supports accounts with different users, and users being part of different accounts, in a so-called multi-accounts-multi-user B2B environment.

Account-based user conditions

When creating user playbooks, journy.io allows you to set related account conditions.

Simply add a condition, and choose 'Accounts'

You now have the choice to set any possible account condition, and indicate whether you want these conditions to be met by:

  • No account

  • At least one account

  • All accounts

User-based account conditions

When creating account playbooks, journy.io allows you to set related user conditions.

Simply add a condition, and choose 'Users'

You now have the choice to set any possible user condition, and indicate whether you want these conditions to be met by:

  • No user

  • At least one user

  • All users


Tip: Need help with your Playbooks?

Reach out to our support team

https://releasemanagement.atlassian.net/servicedesk/customer/portal/14

or book time to make it together