Slipping Away

See who is going quiet,
while you can still win them back

Slipping Away counts the users whose last activity is more than 7, 14, 30, 60 and 90 days old, as of right now. Find where the silence concentrates, open the people behind any count, and save them as a cohort that empties itself as they return.

In this demo car app, 9% of 236,600 vehicles have been quiet for more than 30 days, and the quiet ones have typically been away for 39 days.

Part of analytics

Silence,
read three ways

One stamp drives the page: the time of each profile’s last request, a session, an event or anything else the app sends. From it, three readings of the same audience.

  1. How many have gone quiet?

    Thresholds

    quiet for at least 7, 14, 30, 60 or 90 days

    Each row counts everyone quiet at least that long, so the 90-day row sits inside the 30-day one. Every count opens the profiles behind it.

  2. What does the whole audience look like?

    Recency

    bands that never overlap, from active this week to quiet for 90 days or more

    The same audience in one bar. A healthy one leans to the active side; a tall last band is loss that has built up.

  3. Is it getting worse?

    Risk index

    how long the quiet ones have typically been away

    One number to compare between visits. It is built from the midpoint of each band, so read it against itself, not as an exact duration.

From a count to a campaign

From a number
to the people behind it

Three questions, from noticing the silence to the people you can still win back, all on one page.

Read it right

The questions people ask
the first time they see it

The page is built to answer one question honestly: who is quiet right now, and for how long.

“The rows add up to more than all our users.”

Cumulative on purposeSomeone quiet for three months is in all five rows, because each row means “at least this long”. The recency bar shows the same audience without the overlap.

“So these users have churned?”

Not yetQuiet past a threshold is not gone. Some come back on their own, more come back when asked. The 90-day row is the closest the page comes to churn.

“Where is the date range?”

Always nowThe thresholds are measured from the moment you look, and a profile leaves the counts the moment it returns. For a trend, save a threshold as a cohort and watch its size.

“Thirty days is too long for our app.”

Your thresholdsThe five thresholds are server settings. Change them and the table, the bands, the cards and the risk index all follow.

Works with

Slipping Away, with the
rest of Countly

Every feature reads the same live data, so an answer in Slipping Away doesn’t stop there. These are the handoffs built in.

All features

Data ownership

A list of people to win back
stays on your servers

Who has stopped using your product, and since when, is as sensitive as anything you hold. It is worked out where the data already is.

Data privacy

One data set

The counts read the same profiles as Profiles, Cohorts and Drill, so the list you open is exactly the number you clicked.

Self-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.

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

How is this different from retention?

Retention groups people by when they started and asks whether each group came back, period by period. Slipping Away ignores when people started and asks who is quiet right now, and for how long. Retention judges onboarding and habit; Slipping Away picks who to win back today.

Does someone with several devices count more than once?

No. Counts are profiles, so a person with a phone, a tablet and a car head unit is one row, as long as the devices share a profile.

Try it

Every feature.
One data layer.