For every post made in Hero that users may be notified about (Community Feed Posts and posts made to student pages), you are able to analyse who has been sent a notification, how this was sent and who has read the post in Hero.
- a push notification is clicked to take the user to the post in the app.
- the link in the email notification is clicked to take the user to the post in a web browser.
- a notification is clicked in the notification bell list to take the user to the post.
- "mark all as read" is clicked in the notification Bell.
- posts are viewed in the "My Feed" page (accessed via the "View All" button from the notification bell).
ACCESSING POST ANALYSIS INFORMATION
1. Navigate to the post
2. Click on the three dots menu for this post
3. Click Analyse Engagement
The Engagement Analysis page is split into the following four sections:
1. Graphs

- the proportion of notifications for this post that have been read/unread. Large proportions of unread posts indicate poor engagement.
Orange: the post has not been read. (see above for when a post is marked as read)
Green: the email has been opened, but the link to the post has not been clicked (note that short posts with no attachments are displayed in full in the email, so the user may not need to view the post in the app)
Blue: the user has read the post in the app, or clicked the link in the email to take them to the post.
- how the notifications were sent. This will give an indication of how many are using the mobile app.
Blue: an email notification has been sent
Orange: a push notification has been sent to the Hero app
- whether the notification was sent to a staff member or caregiver.

- Name
- Email Address
- The type of notification that was sent (Email or Push Notification through the Hero App)
- The date the notification was sent
- The date the post was read in Hero by the recipient OR the date the email was opened
Note: For posts made to student pages, staff members are the only type of user that are notified when a post is saved as a draft. The Engagement Analysis will include internal recipients only for posts that have not been published, or that have been made on a page not open to be viewed by parents.
- Name
- Email Address
- All students associated with this caregiver (ie, not just associated students in the targetted groups)
- The type of notification that was sent (Email or Push Notification through the Hero App)
- The date the notification was sent
- The date the post was read in Hero by the recipient OR the date the email was opened
4. Non-Recipients
These are the contacts that would have received a notification based on the student or group selected but did not.
For Non-Recipients you can see:
- Name
- Email Address
- The students associated with this caregiver to which this post is relevant
- The reason that no notification was sent to this caregiver
The most common reasons a notification has not been sent are:
- Contact has NO EMAIL ADDRESS - contacts must have an email address entered in order to receive notifications. For instructions on how to add an email address for this contact see Updating Contact Information
- Contact has ACCESS DISABLED - this contact has the slider "Is allowed access to the Hero app for <student>" switched to off. For instructions for editing this setting see Maintaining Student / Contact Relationships
- If the reason is Rejected by email service this may indicate an invalid address, a full recipient inbox or that emails from the school have been marked as spam.
- If the reason is UNKNOWN it is likely to be for one of the following reasons:
- the contact has chosen to turn off notifications from Hero in their profile information.
- the contact has been updated with an email address and/or access to Hero for this student since the post was published. They are still a non-recipient as the notification is not sent again.
- one or more groups have been added to the post after publishing. The parents of the students in these groups are able to view the notice, but do not receive a notification.
Comments
0 comments
Article is closed for comments.