Admin Guide

Journeys

A journey is an automated chain of pushes: users from the selected segments enter it and go through steps — pushes, waits, conditions and branches — at their own pace.

How journeys work

Every 15 seconds Notirix enrolls the app's users who match the entrance segments and moves enrolled users through the steps. Each user has their own position in the journey: one may be waiting for a day while another is already getting the second push.

ℹ️

Every journey push uses one message from your plan quota, just like a campaign. When the quota is used up, the push is skipped and the user moves on.

Steps

StepWhat it does

EntranceAudience (include and exclude segments), only new users, schedule, re-entry and frequency cap settings.

Push notificationSends a push from a message template to the user's web and mobile subscriptions. Personal variables from tags work as in campaigns.

WaitPauses for a set number of minutes, hours, days or weeks.

Wait untilWaits for a date, a tag value or entry into a segment, with an optional timeout.

Time windowHolds the next step until an allowed window opens: days of the week, hours and a time zone.

Yes / No branchSplits by a condition: the last push was clicked, the user has a tag or tag value, the user is in a segment.

A/B splitSends users down branches by percentage.

Tag userSets or updates a user tag.

WebhookCalls an external URL. Errors are logged and the journey goes on.

ExitEnds the journey for the user.

Entry and exit

A user enters when they match at least one include segment and none of the exclude segments. With re-entry on, they can enter again a set time after finishing or leaving the journey.

A journey ends at the Exit step. Exit rules can also take users out early:

Frequency cap

The frequency cap keeps one user from getting too many journey pushes: no more than K pushes in N minutes, hours or days per user, shared by all journeys of the app. It is off by default — while it is off, journeys work exactly as before.

Turn it on in Admin → Settings → Configuration → Frequency cap: set the maximum number of pushes (1 to 50) and the period (1 minute to 30 days).

What counts

Counted

Every message a journey creates for the user, even if it was not delivered. Pushes of all journeys count, including journeys that do not respect the cap.

Not counted, never blocked

Campaigns and direct (transactional) messages sent from the admin panel, the REST API or the Bitrix module.

The window slides: before each push Notirix counts the user's journey pushes over the last period. A push blocked by the cap does not use your plan quota.

💡

Example: the cap is 2 pushes in 24 hours. Pushes went out at 10:00 and 15:00. A third push due at 18:00 hits the cap; a slot frees up at 10:00 the next day.

Journey settings

In each journey: Settings → Frequency tab. The tab is inactive while the cap is off for the app.

OptionBehaviour

Respect the app capOn by default. When off, the journey sends pushes without the check, but its pushes still count toward the cap of other journeys.

Skip the pushThe push is not sent and the user moves on to the next step right away.

Defer the pushThe user waits on the step until a slot frees up and then gets the push. Set the longest wait in hours (1 to 168, counted from arrival at the step); if no slot frees up in time, the push is skipped.

Exit the journeyThe user leaves the journey early with the reason Frequency cap. Early-exit tags are applied as for other early exits.

ℹ️

Journeys respect the cap and skip the push by default, including journeys created before the cap was turned on.

Analytics

Journey analytics show skipped pushes for every push step: how many were skipped because of the frequency cap and how many because of the plan quota. Exits caused by the cap appear in exit reasons as Frequency cap. Deferred pushes that were sent later are not counted as skipped.

⚠️

After a skipped push the user has no last message, so a following Yes / No branch on Message was clicked answers No.