Statuses, results, and troubleshooting

The history shows the app's last 20 campaigns.

Status	Meaning
Queued	The job is waiting for a background worker
Sending	Recipients have been selected and messages are being sent to FCM
Sent	Processing is complete; at least one message was accepted by FCM, or there were no matching tokens
Failed	The job failed or FCM rejected all sent messages

After a technical failure, the job may be retried up to three times. If some messages are accepted and others rejected, the status is “Sent”. Invalid tokens are disabled and excluded from future campaigns.

Metrics

• Sent — number of tokens for which FCM returned a successful response.
• Opened — number of unique installations that sent a push_open event for this campaign.
• CTR — opened / sent × 100%.

Successful sending to FCM does not confirm that the notification was displayed or read.

If a notification does not arrive

Problem	What to check
Stays “Queued” for a long time	Wait a few minutes. If the status does not change, send support the app name, title, and send time
“Failed” status	Push is enabled, FCM credentials are active, and the Firebase project ID is correct; support checks server settings
“Sent”, but the count is zero	The selected segment has no active tokens
A device did not receive a push notification	OS permission, internet connection, Focus/Do Not Disturb, current app and token, and segment membership
The inactive segment does not work	The app must report the last activity time
The image does not appear	Public HTTPS URL, direct image response, file size; on iOS, rich push support in the build
The deep link does not open	The path exists, is accessible to the user, and is handled by the mobile build
CTR does not increase	The app sends push_open with the correct visitor_key and meta.send_hash

When contacting support, include the app, title, approximate time, segment, status, metrics, platform, and app version. Do not post a push token in a public channel.