Push goes out three ways: a campaign you send or schedule, a journey’s send step when a contact reaches it, or a transactional send from your app. Each one reaches the contact’s active devices in the push project you choose, and checks push consent just before it goes.
From a campaign
- In the campaign’s Details, under Channels, choose Push, or both Email and Push. Push goes to the active devices of contacts with push consent.
- Choose the audience.
- In the Push notification step, choose the app under Send through and write the notification. See Create a push notification.
- On the review step, Who receives it shows how many people each channel reaches.
- Choose Save and send… or Save and schedule… and confirm.
If no push app is ready, the channel says No push app is ready yet with a link to Set up push apps. A campaign with both email and push sends only when both channels are ready; it never goes out on one alone.
You can schedule push for one moment or for each contact’s local time, like email. See Schedule and send a campaign.
From a journey
Add an Email or push notification step, choose push as its channel, then choose the app and write the notification. Each contact who reaches the step gets it then, after the step checks their devices, push consent and topic. See Set up a send step.
- Topic: optionally pick one. Without a topic, it goes to everyone with push consent.
- If they can’t receive this, go to: a path for contacts with no active device, no push consent or outside the step’s topic. Point it at an email step to send push, else email. Without one, they skip this notification and carry on.
- If it can’t be sent, go to: a path for when the notification can’t be queued. A failed delivery comes later and doesn’t branch.
From your app (transactional)
Order updates, delivery alerts and sign-in prompts can be sent by your server through the API, one person at a time. There’s no transactional push template in the dashboard: your developer writes the notification in the request. See the developer guides to push and transactional messages.
Transactional push:
- still needs push consent, unlike transactional email;
- goes at high priority by default, which asks the push service to deliver it straight away (the device’s settings still decide how it’s shown);
- isn’t held by quiet hours or message limits;
- can fall back to email: your developer can send push first and the email only if the push can’t be sent, such as when the contact has no eligible device or the push fails.
Its Delivery report is on the Transactional page, with a Push tab.
Delivery timing
- Campaign and journey push goes at normal priority by default, so a phone may hold it for a little while to save battery. Transactional push goes at high priority by default.
- Quiet hours and message limits apply to campaign and journey push as to email. See quiet hours.
- Offline devices: Apple and Google keep trying a phone that’s switched off for the time set under Stop trying after, one day by default.
What a push doesn’t do
- It doesn’t pause with email. A marketing email pause for bounces or complaints doesn’t stop push.
- It isn’t counted against your email allowance. Push has its own monthly allowance on each plan. See Plans and billing.
- It isn’t silent. Kirora sends every push as a notification, not a background-only push. Whether it appears still depends on the device’s notification settings.