In-App & Push Notifications
Email is not the only way Eventonomy reaches people. From 1.3.0 there are two more delivery channels for members: an in-app notification feed - the bell, with an unread count - and native push to the phones members have signed in on. Both sit alongside email rather than replacing it, and both are driven by the notifications Eventonomy already sends, so there is no second set of messages to configure.
What You Will Learn
- How the three channels relate to each other
- Which notifications reach the bell and push, and which deliberately do not
- Who receives them, and who keeps getting only email
- What is Free and what needs Eventonomy Pro
The Three Channels
Every notification Eventonomy produces is handed to all delivery channels at once, and each channel takes the ones it can actually reach:
| Channel | Reaches | Free or Pro |
|---|---|---|
| Anyone with an email address - members and guests | Free | |
| In-app feed (bell) | Logged-in members only | Free |
| Push | Members who have signed in on a phone and registered it | Registering the device is Free; sending the push is Pro |
| SMS | Attendees who gave a phone number | Pro - see Reminders & SMS |
Because they share one dispatch, an in-app entry is generally created for the same moment that sends the member an email, and the bell entry reuses the email's own subject wording so the two never drift apart.
What Reaches the Bell and Push
A notification lands in the feed (and, with Pro, in a push) when the recipient is a logged-in member. That covers:
| Notification | Trigger |
|---|---|
| RSVP confirmation | The member submits an RSVP |
| Waitlist promotion | A spot opens and the member is promoted to Going |
| Order confirmation | The member's order completes |
| Event reminder | Before the event starts, on your reminder schedule |
| Event cancelled | The event is cancelled |
| Event updated | The event details change |
| Event rescheduled | The event's date or time moves |
| Approval result | An admin approves or rejects the member's own event |
| Organizer message (blast) | An organizer emails their attendees |
| New event from someone you follow (Pro) | An organizer or space the member follows publishes an event |
| Payout receipt (Pro) | You record a payout to that organizer |
Two notifications deliberately never reach the bell or push:
- The guest magic-link email. It goes to a guest who has no account, so there is no feed to write to and no device to push to. Guests keep receiving email and their magic management link exactly as before.
- The "new event submitted" admin notice. It is addressed to your site admin address rather than to a specific member account, so it stays email-only.
More broadly: guests are never in the feed. Anyone who RSVPs without an account is reached by email only, on every notification type.
Push Notifications
Push has two halves that sit on different sides of the Free/Pro line.
Registering a device is Free. When a member signs in on the app, their device is stored against their account. Signing out or uninstalling removes it. A member can have several devices registered at once and a push goes to all of them.
Sending the push is Pro. With Pro active, push is added as a delivery channel on the same dispatch that already sends your email, so every notification type in the table above arrives as a native push too - with no per-notification setup on your side. Without Pro, devices are still registered but nothing is ever pushed to them.
A member with no registered device simply falls back to email, which is the normal case for anyone who has not installed the app.
You control whether the app registers devices at all with Enable push notifications on the Mobile App settings tab - see Mobile App Settings.
The Feed Itself
The feed is per member and is created automatically when you update. There is nothing to configure and no settings screen for it.
Each entry carries a title, a short summary trimmed from the matching email, and - where the notification is about an event - a reference to that event so the app can open it directly. Members can mark a single entry read or mark everything read, and the unread count follows.
How This Interacts With Unsubscribes
Unsubscribe and suppression are an email mechanism: they filter who receives mail. A member who has unsubscribed from notification-class email still sees entries in their in-app feed, and still receives push if you run Pro. Treat the bell as the member's own record of what happened on your site rather than as a mailing list. See Unsubscribe & Suppression.
Related
- Emails - the email channel and the full list of emails Eventonomy sends.
- Reminders & SMS - reminder timing and the Pro SMS channel.
- Mobile App Settings - the settings that enable the app and push registration.
- Mobile App - what the companion app is and what members get from it.