Prepare and test a native push notification
Create a notification and confirm it on a real iOS or Android device.
Last updated 9 September 2026
On this page
Before you begin
UserGist push notifications are for native iOS and Android apps. Your app needs an SDK connection, the correct Apple or Firebase credentials, a registered device token, and the required user permission and consent. Saving credentials is not proof that a notification can reach a phone.
Build the notification
Open Push and create a new campaign.
Write a short title and body that explain why the notification matters now.
Configure the destination or action so the customer reaches the relevant place in your app.
Review the platform preview and any content variants.
Choose the audience and campaign timing, then keep it in draft while you test.
Test on a known device
Use a test recipient you control. Confirm that the phone has granted notification permission, that its token belongs to the intended app and environment, and that the saved credentials match. Send one test, inspect its delivery record, and confirm receipt on the physical device. A preview cannot validate Apple or Firebase delivery.
Launch deliberately
Review who will receive the campaign and when. Activation can queue notifications immediately for broadcast campaigns; scheduled or triggered campaigns follow their configuration. After launching, review results and delivery errors. Keep title, destination, and timing consistent so the notification does what customers expect.