---
title: "Engagement: Journeys, push, in-app, surveys and experiments · Countly"
description: "Turn insight into action, without leaving Countly. Journeys, push, in-app messages, surveys and experiments, triggered by the behavior you analyze."
url: https://countly.com/platform/engagement
last_modified: 2026-11-04
---

Engagement features

# Turn live behavior into messages, experiments and workflows

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.

Trusted by

17,000+ apps in 126 countries keep their data at home.

Capabilities

## From insight to action, in the same system

There is no export to a marketing suite and no overnight sync. Cohorts, triggers and content live next to the analytics that justify them.

### Push notifications

iOS, Android and web push with automatic triggers on events, cohort entry or inactivity. Rich media, localization, delivery reports.

### In-app messages

Show a message, an offer or a guide inside the product when a behavior happens, not a day later.

### Journeys

Multi-step flows across push, in-app and webhooks with waits, conditions and exits, driven by live events.

### A/B testing and Adaptive Variables

Change features, flows or copy for a segment without a release. Measure the effect on the same dashboards.

### Surveys and feedback

Ratings, NPS and surveys targeted by behavior, with responses attached to the profile.

### Webhooks and hooks

Trigger internal workflows and systems from product behavior: notify a team, update a CRM, open a ticket.

In depth

## How it works, in detail

The parts that matter when you evaluate this area seriously: what it does, how it behaves at the edges, and what your team controls.

01 Triggers 02 Adaptive Variables 03 Feedback

### The signal and the action share one data layer

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.

- Triggers on events, cohort entry and exit, inactivity
- Audience is any cohort or drill segment
- Delivery and outcome measured on the same reports

### Change the product without a release

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.

- Progressive rollouts by segment or percentage
- Experiments with automatic significance
- Kill switch tied to crash and performance data

### Surveys and ratings tied to behavior

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.

- Target surveys by cohort, event or session count
- NPS and ratings with follow-up questions
- Responses stored on the profile, usable in Drill
- Localized, branded, rendered natively by the SDK
How it works

## Insight to action in four steps

Everything below happens in one workspace, on one set of permissions, on one data model.

- 01 Find Spot the segment in Drill, Retention or a Cee finding.
- 02 Target Save it as a cohort. It updates in real time as behavior changes.
- 03 Act Attach a push, in-app message, journey, experiment or webhook.
- 04 Measure Outcomes land in the same reports, so the loop closes without exports.
FAQ

## Questions teams ask us

Straight answers on how this part of Countly works in practice. For anything else, talk to us.

**Do we need a separate messaging tool?**

No. Push, in-app messages, journeys, experiments and surveys are part of the platform and share cohorts and reports with analytics.

**Can engagement respect consent?**

Yes. Consent categories cover engagement as well, so a user who has not consented to messaging is never targeted, at the SDK level.

**Can we trigger our own systems?**

Yes. Hooks fire on events, cohort changes, alerts or schedules, and send the payload to your systems over HTTP, by email or through your own code.

**How are results measured?**

Every campaign, journey and experiment is measured on the same live data as your analytics: conversions, retention and revenue by variant or audience.