Audiences from behaviour
“Added to cart, didn’t buy, came from spring-sale.” Built in seconds, with the size shown live.
Campaigns
Pick an audience from real behaviour, send a push with a deep link inside, and see who bought afterwards.
Why Lotse campaigns
“Added to cart, didn’t buy, came from spring-sale.” Built in seconds, with the size shown live.
A deep link in every message, straight back to the cart.
Sent, opened and your goal event — per campaign.
How a campaign runs
Inside the app too
Cards and banners shown on the right screen, counted for who saw and tapped them.

Compared
Push alone is everywhere. Lotse targets by origin campaign, behaviour and feedback — from one segment.
| Lotse | OneSignal | Firebase | |
|---|---|---|---|
| Push | yes | yes | yes |
| Attribution | yes | no | limited |
| One segment across all of it | yes | no | no |
| EU data residency | yes | difficult | difficult |
| Native to Serverpod | yes | no | no |
In each single discipline the specialist goes deeper. The value of Lotse is in the transitions.
For developers
// A push tapped while the app was closed, and pushes tapped while it runs.
final push = await Lotse.instance.initialPush;
Lotse.instance.pushOpened.listen((push) => router.go(push.targetPath ?? '/'));
Yes. Send now or pick a time.
Yes, over APNs. TestFlight and App Store builds need a production APNs key.
Not yet. Lotse sends push and in-app messages.
Campaigns
Build an audience, write one message, read the result.