Three steps to get going, then a careful path for every message: the right people, at the right hour, with proof of what it changed.
Create an app and upload the Firebase service account and APNs key you already have. Perchpush checks the Firebase key with Google and stores every key encrypted.
A few lines in Flutter, React Native, iOS or the web. Identify signed-in users and track the events you care about. The guided setup waits for your first device.
Send a campaign or start a journey. Delivery, opens and conversions roll in live, with the raw answer from each provider for every attempt.
The same five stages run for a one-off campaign, a journey step or an API call from your server.
Everyone, segments, a list of user ids, devices or filters. Describe it in plain words and the AI writes the filter.
Opted-out people, turned-off topics, frequency caps and the hold-out group are removed. None of them count as sends.
Now, at a set time, at the same local time everywhere, or at each device’s best hour. Quiet hours hold marketing messages.
Messages go to Firebase, Apple, the browser, your mail server or your SMS gateway. Each reply is logged and dead tokens are removed.
The device confirms receipt, taps and goal events are counted, and signed webhooks tell your server what happened.
Instead of sending to everyone at once, each device gets the message in the hour it usually engages. No guessing and no manual time zones.
Included in the Growth and Business plans. Compare plans.
Every push carries a small marker. The SDK reports a receipt when it arrives, so “received” is shown apart from “accepted by Google or Apple”.
Pick a goal event and a window, such as a purchase within 24 hours. A conversion is that device firing the event in time.
Hold back 1 to 50% of the audience. They are never sent to and never charged, and the campaign page shows the lift against them.
Try versions on a slice of the audience, and the winner goes to everyone else.
Purchases tracked from the SDK or your server are credited to the last campaign opened within 24 hours.
When a provider reports a dead token, Perchpush records an uninstall and removes the device.
Every hour Perchpush looks at the last 90 days of opens and app sessions for each device, with an open counting three times as much as a session, and picks the hour it engages most. New devices fall back to your app’s best hour. A send spreads over 24 hours.
Most of the work is uploading the Firebase and APNs keys you already have and adding a few lines of SDK code. The guided setup in the dashboard waits for your first device and lets you send yourself a test.
No. Messages marked transactional, such as order updates or sign-in codes, go straight away and skip marketing frequency caps.
Create an app, connect Firebase and send a test to your own phone in a few minutes.
Perchpush
