In this demo car app, one message drawn on every platform it goes to. What you type on the preview is what people receive.
Push Notifications
Send the push your analytics
already knows how to aim
Push in Countly targets the same cohorts, profiles and places your reports use, fills in each person’s details on the way out, and measures what happened on the same data. One message for iOS, Android and the web, written on live previews.
Part of engagement
The right message,
at the moment it matters
Five ways a campaign goes out: once, on a schedule, on dates you list, when a profile does something, or when your own server says so. Each one can carry the person’s own details.
“Your weekly driving summary is ready, Ada.”
Recurring, every Monday at nine in each driver’s own time zone, with their name filled in and a fallback for anyone without one.
“We haven’t seen you in a while. Here is what changed in 6.2.”
Automated, when someone enters a lapsed cohort, and cancelled if they come back before it goes out.
“Thanks for the trip. Rate it in one tap?”
Automated on an event, with the event’s own properties available to the message.
“Your car is charged to 80%.”
API: your server triggers it the moment the charger reports, with the values in the call.
“Service centers close early on 24 December.”
One-time, to everyone near the locations you saved, at one moment for all.
“Your winter tire change is due next week.”
Multi-day, on the exact dates you list.
From audience to outcome
Aim it, check it,
then see what it did
Every campaign is one editor and one results page, with the reach counted before anything is sent.
Safe to send
Built for teams that answer
for what they send
A push reaches people’s lock screens. These are the guardrails between a draft and that moment.
- 01Optional
Approval
A project can require sign-off. Launch becomes Send for approval, and the campaign waits until someone with the right decides.
- 02Every campaign
Reach before launch
The estimate counts only profiles registered for push on the platforms you chose, so a zero shows a problem before anything goes out.
- 03Per campaign
Delivery deadline
A message whose time has passed is dropped, not delivered late. 24 hours by default, from one hour to a week.
- 04Optional
Local time
Nine in the morning in each recipient’s time zone, with a choice for anyone already past it: skip them or deliver the next day.
- 05Every campaign
Frozen once sending
Who it goes to and when cannot change after it starts. Duplicate it to send it differently.
- 06Every campaign
Undo
Deleting a campaign stops its deliveries, with a few seconds to take it back.
Works with
Push Notifications, with the
rest of Countly
Every feature reads the same live data, so an answer in Push Notifications doesn’t stop there. These are the handoffs built in.
All featuresData ownership
Aimed with your data,
on your servers
Targeting and personalization run where your analytics live, so the cohorts and properties behind a campaign never have to be copied into a separate messaging tool.
Data privacyOne less vendor
Push uses the same SDK, the same profiles and the same cohorts as your analytics. There are no audiences to sync.
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