APP PUSH FREE
Free$0 · Free plan
Start with core App Push features and a shared queue.
MADE FOR YOUR USERS
Transactional push notifications for everyday moments
One relevant update. One clear destination.
Shipping
A parcel moves to its next stop
Connect transactional push notifications to a verified fulfillment event and current order view.
Reservations
A booking update is ready
Notify the booking owner about a confirmation or change without disclosing unnecessary details.
Account activity
Help users review a recent change
Show a neutral account activity alert and require authentication before displaying details.
Service status
An appointment moves forward
Use transactional push notifications to share a confirmed service or collection update.
CHOOSE WITH CONFIDENCE
Plan your transactional push notifications integration
Connect notification delivery to your application rules.
| Your requirement | How it is delivered | What to plan for |
|---|---|---|
| Permission & identity | Register subscribed recipients through the platform SDK. | Your app owns consent, preferences, and account-device mapping. |
| Sending | Use the supported console or server APIs. | Your backend controls business triggers, timing, and duplicate suppression. |
| Opening an update | Handle a notification click and its destination. | Validate payloads and account access before showing private content. |
| Delivery insight | Inspect available message records and engagement reports. | Accepted sends do not guarantee receipt; features depend on the plan and channel. |
FROM SETUP TO FIRST SEND
Get started with transactional push notifications
Configure the channel, connect a test recipient, and follow the complete integration guide.
BUDGET BEFORE YOU BUILD
Transactional push notifications Pricing & Trial
Start with App Push for transactional push notifications. Web Push has separate plans.
What are transactional push notifications?
They communicate an event tied to an existing account or user action, such as an order update or booking confirmation. The sending trigger should come from your authoritative backend.
How do transactional push notifications differ from marketing?
Transactional messages explain a relevant service event; marketing messages promote a return or offer. Keep audience eligibility, consent, frequency, and preference rules appropriate to each purpose.
Are transactional push notifications guaranteed delivery?
No. Permission, operating system policies, network state, and channel behavior affect delivery. Design any required fallback or escalation in your own application.
Can transactional push notifications include private details?
Keep lock-screen previews minimal. Route the user into an authenticated view for sensitive details, and verify that the current account can access the referenced record.
How do I prevent duplicate transactional push notifications?
Use idempotent event handling, recipient checks, and expiry rules in your backend. Push delivery records help investigate sends, while your system controls business-event duplication.
How do I send transactional push notifications after an order or booking?
Trigger the message from a confirmed backend event and address an authorized recipient. Include a clear destination and avoid exposing sensitive details on the lock screen.
How should transactional push notifications handle duplicates and expired events?
Give business events stable IDs and apply idempotency and expiry in your sender workflow. Define a fallback for critical updates because delivery depends on permission, channel and device state.