Push notifications for mobile apps.

Push notification software sends short messages to a customer's device through the platform's push service. In Gleap, push campaigns are written in the outreach editor with a title and message, targeted with the same audience rules as email, and delivered to iOS and Android apps and to browsers through Firebase Cloud Messaging.

A Firebase project and its service account key uploaded in Gleap's push settings, plus the Gleap SDK in your app. The SDK gives your app a push topic for each identified user, your app subscribes the device to it with Firebase, and the operating system or browser asks the user for notification permission. See the push setup documentation.

Yes, through Firebase Cloud Messaging. Add Firebase to your site; the JavaScript SDK reports the user's push topic and your server subscribes the browser to it. See the web push setup. Native iOS and Android apps, including React Native, Flutter, Capacitor and Cordova builds, use the same connection. While people are in the product, banners, info cards and in-app messages reach them in the widget.

Either once to a one-off audience, everyone who matches the rules right now, or dynamically, each time a person matches after an event or property trigger, with an optional delay and a frequency. News items can also send a push when they go live.

Yes. When a teammate or Kai Support replies to a conversation, the customer's device receives a notification such as New comment from Lukas, and tapping it opens the conversation in your app. This uses the same Firebase connection as campaigns.

Yes. Audience rules combine contact attributes, tags and events, and the audience preview shows how many people match. Audience membership does not replace device registration and permission, both of which are needed for delivery.

Yes. Title and message have a version per project language, with translation assistance in the editor. Keep the message short: most devices truncate after a few lines.

No. Delivery depends on Firebase, the device, connectivity and the user's notification settings. Use email or the in-app conversation as well when a message is critical.

Push reaches people who are away from the app, on the device. Email carries the longer message and the newsletter. In-app messages, banners and info cards reach people while they use the product. All share one outreach list and one customer record.

Yes. Through the Gleap MCP server, an agent drafts push notifications, targets them by trigger, events and contact attributes, previews the recipients and publishes once you approve. A one-off push needs the recipient count you approved and is never sent to every contact. If the event it needs is not tracked yet, the agent gets the tracking code for your app.

Push is one channel of the same conversation. A reply on the phone lands in the inbox, Kai Support answers what it can, and a reported problem becomes a ticket with the device and session data attached. See the platform and how Gleap closes the loop.

Push notifications are part of outbound messaging, included from Team ($149 per month, billed annually), with unlimited seats. See pricing for plan details.