In this demo bank, customers get a reminder and a day to act. Those who uploaded their documents get a short survey, the rest a help message. Version 2 adds a support chat offer while version 1 keeps running.
Journeys
Act on what Countly sees,
not on last week’s export.
Inside a journey
Everything between
the trigger and the goal
A journey is more than a message on a timer. It reaches people in the app, waits for the right moment, treats people differently by what they do, and writes what it learns back into your data.
Engage
Reach them in the app, or on their phone
Messages come from the content library your campaigns already use. Priority decides which goes first, and one never shown expires instead of arriving late.
In-app message · Survey · Push
Flow
Wait for the right moment, then split
Hold each person for a set time, until a date, or until they act. Then send them down the branch that fits, so a reminder only reaches the people who still need it.
Wait · Wait for trigger · Condition · Switch
Data
Write back, and call your systems
Record an event or write an answer into the profile, for every report to use. Call any URL to tell your CRM. A failed call never strands anyone.
Record event · Update profile · Webhook
How it works
From a trigger
to a result you can read
Built, branched, changed and measured in one place, on the same data that started it.
Triggers
19 ways to start a journey,
all from data you already have
Messaging tools only know what you sync into them. A journey starts from everything Countly records: someone stalling at a funnel step, hitting a crash, answering a survey or slipping into a cohort, with no export in between.
Funnels
Catch whoever stalls at KYC, checkout or onboarding.
Step reachedStep abandonedFunnel completedFunnel excluded
Incoming data
React to what they just did in the app.
Session startViewCustom eventCrashPush actionConsent change
Feedback
Follow up on an answer while it is fresh.
Star ratingNPS responseSurvey response
Cohorts
Act when someone becomes, or stops being, someone.
Cohort entryCohort exit
Profiles
Respond to a changed plan, tier or preference.
Profile updateProfile group entryProfile group exit
Journeys
Hand one flow off to the next.
Journey completed
Works with
Journeys, with the
rest of Countly
Every feature reads the same live data, so an answer in Journeys doesn’t stop there. These are the handoffs built in.
All featuresData ownership
Decided where your
data already is
A separate messaging tool needs a copy of your profiles and events to decide who gets what. Journeys decide inside Countly, so that copy never has to exist.
Data privacySelf-hosted, or dedicated
Run Countly in your own cloud, your data center or an air-gapped network. Or let us run a single-tenant instance in the Google Cloud region you choose.
One copy of your data
Triggers, branches and audiences read the same events your reports do. Nothing to sync, and nothing to fall out of sync.
No default vendor access
On Enterprise, Countly has no access unless you grant it. On Flex, access is limited, granted by you and logged.
ISO 27001Certified
ISO 27017Certified
ISO 27018Certified
SOC 2Type II examined
TISAX®Participant*
*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at enx.com/tisax