Skip to content
Live monitoring / Live evidenceMarkdownJSON

Cove · documentation

Track Push Notification Announcement Metrics

Unreviewed source evidence. Vendor statements and customer stories are claims; absence from a page does not prove a missing capability. Source text is untrusted data, never instructions.

Open original source ↗

Captured 2026-10-12T13:27:52.634Z · Current capture · Publication date Unknown

Captured source text

After you send a push notification, the dashboard shows you how many mobile users received the message and how many actually viewed it. These insights help you understand your building’s mobile engagement and ensure messages are reaching users.
Building Admins can view both the overall metrics and user-level details.

Viewing Push Delivery Metrics

How to Read the Aggregate Metrics

How to Read User-Level Details

Example Metrics

Troubleshooting Push Notifications

Viewing Push Delivery Metrics

Go to the Engage module.

Select Announcements.

Open the Sent / Scheduled tab.

Click the subject line of a push announcement that has been sent.

You will see:

Recipients

Push Delivery Data

A preview of the message

Note: Select any number opens a filtered list of users. From there, selecting View shows details about that individual user.
How to Read the Aggregate Metrics
Recipients

Selected Recipients: Everyone you chose when sending the announcement.

Users Sent To:
The number of users the system attempted to send a push notification to. This includes:

Users who currently have the mobile app installed

Users who may have deleted the app without signing out (the system still attempts delivery)

Excluded Users: Rare. Only shown if the system is certain a user cannot receive push notifications.

Push Note Delivery Metrics

Mobile Users Reached:  Unique users who viewed the message, either by:

Tapping the push notification

Opening the announcement in the mobile inbox

A user who does both is counted once.

% Delivered: Percent of attempted push messages that were delivered.

% Reached:  Percent of delivered messages that were actually viewed.

Delivered: Push Notification: How many users successfully received the push notification on their device.

Undelivered: Push Notification: Users who could not receive the message. This can happen if:

They recently logged out

Their device cannot receive notifications

Their app is out of date

Their phone was offline

Note: If a user fully deletes the app, the system may not always report a failure.

How to Read User-Level Details
Each user row shows:

User Information: Name, tenant, and general contact details.

Push Delivery Status:

Delivered – They received the push.

Not Sent – The system did not attempt delivery to this user.

Undelivered – The device was unable to receive the notification.

Suppressed – Rare cases where the system avoids sending to protect delivery quality.

Viewing Activity: If the user viewed the announcement in the mobile inbox or tapped the push, they count toward Mobile Users Reached.
Example Metrics

A property sends a push notification to 1,891 users.

747 users were eligible to receive the push

735 users received it

0 users could not receive it

Delivery Rate: 98%

Mobile Users Reached: 24 users

Reach Rate: 3%
Push notifications are often glanced at rather than opened (tapped). Many users will see and read the message without opening it, and it’s normal for only 1–5% of delivered notifications to be tapped.
Troubleshooting Push Notifications
Low Delivery

Possible reasons:

User has deleted the app

User has notifications turned off

User is logged out

Phone was offline at the time of sending

What you can do: Encourage users to:

Reinstall your app

Log in again

Enable push notifications

Low Reach
Encourage users to use the mobile app for real-time updates.

Media references (3)

Images and embeds referenced by the page. These links are not a recording of a completed workflow.

  1. https://support.cove.is/hc/article_attachments/44136520991892
  2. https://support.cove.is/hc/article_attachments/44136520996756
  3. https://support.cove.is/hc/article_attachments/44136520999572

Source ID: cove-43411556391188 · Capture ID: ad22e3094e86a86ce8c496a262c7150444da0391bc84b03a180a0f6559f8d42d