Push, in-app messages and journeys, sent from your own servers.
Reach users inside the app with the data you already hold, without copying it into another vendor's cloud. Works alongside the engagement platform you already use.
No activation in 3 days
1 day, then send at 9:00
A 45 · B 45 · control 10
Your card is ready
Activate card banner
No message
A wins · +12.3 pts vs control
Friday 24 October
19:00
The Coast S2 is out
All 8 episodes, now streaming.
Home
Continue watching
NEW SEASON
Pick up The Coast
Season 2, episode 1 · 48 min
Watch nowNot nowHow it works.
- 1
Pick an audience
Build it from events, properties, the link a user came from, or an uploaded list.
- 2
Design the message or journey
Push, in-app, surveys, or a multi-step journey with waits, branches and a control group.
- 3
Measure the outcome
Opens are a start. Goals measure what users actually did, against the control group.
What engagement does for you.
Journeys that react.
Start on a trigger, wait, branch on what each user does, and stop when they reach the goal.
Trigger
Trial started
Wait
2 days
Push
Try your first workout
Goal
workout_started
Push from your servers.
Scheduled or instant, in each user's local time, with a deep link to any screen and delivery reporting.
Push
Your card is ready
Activate it in one tap.
9:00 local time
8,240 users
9:00
Your card is ready
Activate it in one tap.
Prove what works.
Variants and a control group on every campaign, measured on the outcome you care about, not on opens.
Experiment · card activation
Winner found+12.3 pts vs control · 95% confidence · A sent to the rest
Every feature.
Included on every grovs plan, cloud or self-hosted.
| Channels | Orchestration | Measurement | Audiences |
|---|---|---|---|
| Push notificationsiOS and Android, from your servers. | JourneysTriggers, waits and branches. | ExperimentsVariants plus a control group. | SegmentsBuilt from your grovs data. |
| In-app messagesBanners, modals and full screens. | Local-time deliverySend at 9:00 wherever each user is. | GoalsPurchases, bookings or any event. | Individual usersMessage one user from your backend. |
| Your own HTMLDesign in-app messages your way. | Frequency limitsNo user sees too much. | Winner selectionSend the best variant to everyone. | Uploaded listsTarget a list of IDs. |
| Surveys and ratingsQuestions inside the app. | Deep link to any screenEvery message opens the right place. | Delivery reportingSent, delivered, opened, converted. | APITrigger messages from your systems. |
Channels
- Push notificationsiOS and Android, from your servers.
- In-app messagesBanners, modals and full screens.
- Your own HTMLDesign in-app messages your way.
- Surveys and ratingsQuestions inside the app.
Orchestration
- JourneysTriggers, waits and branches.
- Local-time deliverySend at 9:00 wherever each user is.
- Frequency limitsNo user sees too much.
- Deep link to any screenEvery message opens the right place.
Measurement
- ExperimentsVariants plus a control group.
- GoalsPurchases, bookings or any event.
- Winner selectionSend the best variant to everyone.
- Delivery reportingSent, delivered, opened, converted.
Audiences
- SegmentsBuilt from your grovs data.
- Individual usersMessage one user from your backend.
- Uploaded listsTarget a list of IDs.
- APITrigger messages from your systems.
Questions about a feature?
Talk to an engineer who builds it, or read how it works in the docs.
Runs on your servers.
Engagement is part of the grovs deployment in your cloud or data center. Or start on grovs Cloud and move later.
Stays in your cloud
Campaigns, audiences, journeys and results, all in your own data stores.
What leaves
Push payloads go to Apple (APNs) and Google (FCM) for delivery. That's how every push on a phone works.
One SDK, five products.
Each product is one step of the same journey: bring users in, understand them, keep them, monetize and own the data.
Questions, answered.
Something else? Talk to an engineer.
Do we have to replace Braze, Salesforce or Adobe?
No. Many teams keep their engagement platform for email and use grovs for push, in-app and journeys where the data has to stay inside. Both can run side by side.
How are push notifications delivered?
From your grovs deployment through Apple Push Notification service and Firebase Cloud Messaging, which is how every push reaches a phone. Campaigns, audiences and results stay on your servers.
Can messages use sensitive data?
The data never leaves your infrastructure, so your own rules decide what a message can use. Push text is visible on the lock screen, so keep it generic and put details behind the tap.
How do experiments and control groups work?
Split an audience into variants and a control group that gets nothing. grovs compares each variant against the control on the goal you set, like a purchase or a booking, and can send the winner to everyone else.
Can in-app messages use our own design?
Yes. Use the built-in banner, modal and full-screen formats, or your own HTML, with frequency limits so users aren't shown the same message too often.
Do you send SMS or email?
No. grovs links work inside the SMS and email you send with your existing tools, and their clicks show up in your journeys.
Your first link, live this afternoon.
Install the SDK, connect your domain and send a link that opens the right screen. Start free on grovs Cloud, or run the same stack in your own.
Compare plans$0up to 10K monthly users
- Sign up and add the SDK
- Your first link live the same day
- Flat yearly price as you grow
Flat licencea year, in your cloud, no metering
- AWS, Azure, GCP or your data center
- Deployment help from our engineers
- Your SSO, your database, your rules