Send a Notification
Compose, test, schedule, and track push Notifications in the Dashboard.
The Push page is where you write Notifications, send them to a Segment, and check what happened to each delivery. Admins and Operators can both send.
Before your first send, finish Set up push and add at least one phone to Test devices.
Send your first Notification
- Open Push and click New notification.
- Under Audience, choose who gets it: Everyone, another built-in Segment, or one of your own Segments.
- Under Notification, choose a Category, then write the Notification title and Notification body.
- Under Platforms, choose Android, iOS, or both.
- Check Who will get this on the right. It estimates how many people and devices match. Click Refresh if you changed the audience or platforms.
- Click Test send, pick one of your Test devices, and check the Notification on that phone.
- Click Review and send, check the summary, then click Confirm send.
The Notification appears on the Sent tab. Open it to follow delivery.
Who receives it is decided at send time
The Who will get this count is an estimate. ComRaid works out exactly which Contacts match the Segment when the Notification goes out, so the final number can differ, especially for scheduled sends.
Send to one Contact
To send to a single person, open their Contact under Contacts and click Send Notification. The composer opens with that Contact as the audience and sends to all their active devices on the platforms you pick. This only works for Contacts with an External user ID.
Test before you send
Test send sends your current draft to one phone from your Project's Test devices list, straight away. The result appears at the top of the composer:
| Result | What it means |
|---|---|
| Test send accepted | Google or Apple accepted the push. Check the phone. If nothing appears, see Troubleshooting. |
| Invalid token | The provider permanently rejected this device's token. ComRaid marks the device Inactive. Reinstall or re-register the app on the phone. |
| Provider configuration error | Your FCM or APNs credentials are wrong or missing. Fix them in Set up push. |
| Provider temporarily unavailable | Try again in a moment. |
Test sends aren't saved to send history, don't count in metrics, and ignore opt-outs and category preferences. They're for checking setup and content only.
Schedule a Notification
Under Delivery, turn on Schedule send and pick a date and time. The button changes to Review and schedule.
- Fixed time: everyone gets it at the same moment. The time you type is in your organization's timezone, shown in the field label.
- Use each recipient's local time: each Contact gets it at that clock time in their own timezone, for example 9 AM wherever they are. Contacts without a known timezone are treated as UTC.
You can cancel a scheduled Notification until it starts sending. See Cancel a Notification.
Notification options
All of these are optional.
Content
| Option | What it does |
|---|---|
| Subtitle | A second line under the title. iOS only. |
| Image | Click Select image to upload a JPEG or PNG (up to 1 MB), or paste a public https:// image URL. On iOS, images only show if your app includes a Notification Service Extension. See Images and action buttons (iOS). |
| Deep link | The screen to open when the Notification is tapped, for example myapp://orders/42. Your app receives it as cr_deep_link. |
| Action buttons | Up to 3 buttons, each with an Action id and a Label. Click counts per button appear on the Notification's detail page. See the callout below. |
| Custom data | Key/value pairs passed to your app in the push data (up to 4 KB). Don't use keys starting with cr_, which ComRaid reserves. |
Action buttons need app support
On Android, Notifications with action buttons are drawn by your app, not the system. The ComRaid Android and React Native SDKs do this for you. If your app uses its own messaging service, it must display cr_actions itself, or users see nothing. On iOS, the alert always shows, but the buttons need the comraid.actions category registered in your app. The Dashboard preview is only an illustration. See React Native SDK.
Sound, badge, and grouping
| Option | What it does |
|---|---|
| Sound | The name of a sound file bundled in your app, for example chime.caf. On Android 8 and later the category's sound plays instead. |
| Badge | The number on the iOS app icon. |
| Thread / tag | Groups related Notifications: the iOS thread ID and the Android notification tag. |
Delivery
| Option | What it does |
|---|---|
| Delivery urgency | High delivers as soon as possible. Normal lets the phone wait a little to save battery. |
| Time to live (seconds) | How long the provider keeps trying to reach a phone that's offline. Default is 24 hours, maximum 28 days. |
| Collapse key | A newer Notification with the same key replaces the older one on the phone, for example a live score. |
Drafts and duplicates
- Click Save draft to keep a Notification for later. Drafts are shared with your team on the Drafts tab of the Push page, showing who last edited each one.
- To reuse a sent Notification, open it and click Duplicate. The composer opens with the same content, and nothing is created until you send or save.
Track delivery
Open any Notification from the Sent tab to see:
- Delivery progress: totals for the whole Notification (sent, delivered, failed, and so on), plus sent and failure rates.
- Results by platform: the same totals split into Android and iOS. A problem on one platform usually means that provider's credentials are wrong.
- Deliveries: one row per device, with the Contact, device, status, and the reason for any failed or skipped row. Filter by status and platform.
- Message content, Targeting, Timing, and the Notification ID.
Delivery statuses
| Status | Meaning |
|---|---|
| Queued | Waiting to be sent. |
| Processing | Being sent now. |
| Sent | Google or Apple accepted it. This doesn't yet mean the phone showed it. |
| Delivered | Your app confirmed the Notification arrived. |
| Opened | The user tapped it. |
| Failed | It couldn't be sent. See the reason. |
| Skipped | ComRaid deliberately didn't send it, for example because the Contact opted out. See the reason. |
Sent is not the same as delivered
Delivered and Opened only count when your app reports them through the ComRaid SDK. If you see many Sent but few Delivered, check that the SDK is set up in your app.
Notification statuses
A Notification as a whole is scheduled, preparing (working out its audience), processing (sending), completed, failed, or cancelled. A Notification to a Segment shows Preparing… until its audience is ready, then its counts fill in.
Cancel a Notification
While a Notification is scheduled, preparing, or processing, open it and click Cancel notification. Deliveries that haven't gone out yet are skipped. Ones already sent can't be recalled.
Troubleshooting
Find failing Notifications
The Failed tile on Overview counts failed deliveries in the last 24 hours. Click it to open Push filtered to the affected Notifications. On the Push page you can also filter by Failed window (last 24 hours, 7 days, or 30 days).
Common failure and skip reasons
| Reason | What happened | What to do |
|---|---|---|
| Invalid token | The provider permanently rejected the device's token, so ComRaid marked the device Inactive. | Usually the app was uninstalled, so no action is needed. On a Test device, reinstall or re-register the app. |
| Endpoint inactive | The device was already Inactive before this send. | Nothing. It's skipped until the app registers again. |
| Opted out | The Contact turned off push. | Nothing. This is the user's choice. |
| Category preference disabled | The Contact turned off this category. | Nothing, or send with a different category. |
| Identity verification not met | Identity verification is required and this device logged in without a signed token. | See identity verification. |
| Provider configuration error | Your FCM or APNs credentials were rejected. | Fix them in Set up push, then send again. |
| Provider error | A temporary or unexpected error from Google or Apple, after retries. | Send again later. If it continues, check the provider's status page. |
| TTL expired | The phone stayed offline longer than the time to live. | Nothing, or use a longer Time to live. |
Test send accepted, but nothing on the phone
- Check that notifications are allowed for the app in the phone's settings.
- On iOS, make sure the device's sandbox or production setting matches how the app was built. See Set up push.
- On Android, check that the category's channel isn't turned off on the phone.
From the API
The Dashboard covers sending to a Segment or to one Contact. Use the API (POST /messages, POST /campaigns) or @comraid/node for:
- Single send to a list of
external_user_ids:POST /messageswithto.external_user_ids. - Multi-send with different content per Contact:
POST /campaigns. - Data-only Notifications, which the composer can't create.
- Listing every delivery with paging:
GET /messages/{id}/deliveries.
Full guide: Notifications.