Engagement features
Push, in-app messages, journeys, A/B tests, surveys and Adaptive Variables, triggered by the same real-time data you analyze. The segment you found a minute ago is the audience you message now.
Capabilities
There is no export to a marketing suite and no overnight sync. Cohorts, triggers and content live next to the analytics that justify them.
iOS, Android and web push with automatic triggers on events, cohort entry or inactivity. Rich media, localization, delivery reports.
Show a message, an offer or a guide inside the product when a behavior happens, not a day later.
Multi-step flows across push, in-app and webhooks with waits, conditions and exits, driven by live events.
Change features, flows or copy for a segment without a release. Measure the effect on the same dashboards.
Ratings, NPS and surveys targeted by behavior, with responses attached to the profile.
Trigger internal workflows and systems from product behavior: notify a team, update a CRM, open a ticket.
In depth
The parts that matter when you evaluate this area seriously: what it does, how it behaves at the edges, and what your team controls.
Triggers
A user shows churn risk, a cohort membership changes, a feature is used for the tenth time. Each is an event Countly already has. Engagement features subscribe to those events directly, so the message goes out while it still matters.
Adaptive Variables
Adaptive Variables and A/B tests let you roll a feature out to internal users, then to 10%, then to everyone, and roll it back in a click if crash rates move. Every variant is measured on live data.
Feedback
Ratings widgets, NPS and surveys are shown to segments, not to everyone: users who finished onboarding, users whose crash-free rate dropped, users who used a feature ten times. Responses are attached to the profile and become segmentation properties, so satisfaction can be read against real behavior.
How it works
Everything below happens in one workspace, on one set of permissions, on one data model.
Spot the segment in Drill, Retention or a Cee finding.
Save it as a cohort. It updates in real time as behavior changes.
Attach a push, in-app message, journey, experiment or webhook.
Outcomes land in the same reports, so the loop closes without exports.
FAQ
Straight answers on how this part of Countly works in practice. For anything else, talk to us.
No. Push, in-app messages, journeys, experiments and surveys are part of the platform and share cohorts and reports with analytics.
Yes. Consent categories cover engagement as well, so a user who has not consented to messaging is never targeted, at the SDK level.
Yes. Webhooks and hooks fire on events, cohort changes or schedules and can call any internal endpoint with the event and profile payload.
Every campaign, journey and experiment is measured on the same live data as your analytics: conversions, retention and revenue by variant or audience.
