Journeys
Journeys follow what readers do and respond step by step: an email two days after signing up, an offer a week after cancelling, a newsletter box when a regular reader scrolls halfway down an article.

Send emails, wait, update profiles, add tags, put notifications in the reader’s bell and tell your other systems.
Show an experience when a visitor scrolls, stays, is about to leave or reads their third article of the week.
Split readers at random between two emails or two experiences, and see the results on each path.
Background journeys start when a reader signs up, subscribes, cancels, opens an email or does anything your site tracks, or on a weekly schedule for a segment.
On-page journeys work for every visitor, anonymous or logged in. Check the page, the visitor’s reading history, their subscription and their segments, then show the experience that fits.
Add steps and splits in a visual builder that checks your journey before it goes live. Each step shows how many readers reached it, and emails show opens and clicks.

Orchestration decides which experience a reader sees on a page. Journeys add time and steps: they react to what a reader does, wait, check, and continue, by email and on the page.
Any of your email templates. Readers who have not agreed to marketing email, or who unsubscribed, are skipped.
Yes. A webhook step sends the reader to any endpoint you set up under Connect, with its authentication.
Yes. They can use the page, the device and the visitor’s reading history for everyone, and profile details for readers who are logged in.
Create an account and add the tag, or ask us to walk you through it.
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.