Notifications is an engagement feature in the attendee app — a feed of messages the organizer schedules and the attendee sees in the app. Attendees can like and comment on them. Anyone with the mobile app installed receives them as push notifications. Notifications is the main channel for communication during the event (welcome, agenda changes, reminders, follow-up). It differs from E-mail campaigns in that Notifications go into the app, while a campaign goes into the e-mail inbox.
Turn on the engagement feature Notifications in the Engagement features category.
Prepare a plan of the key notifications in advance — a welcome notification, a reminder on the day of the event, notifications during the day (changes, refreshments, surveys), and a follow-up.
Decide whether to enable comments on each notification (yes for interactive news, no for system info).
For a notification to arrive as a push, the attendee must have the mobile app installed.
In the left event menu go to Engagement features → Notifications. The feature belongs to the Engagement features category and shows up only in the attendee app (not on the microsite).
In the source materials the feature also appears under the names News, News Feed, or Push notifications — the canonical product name is Notifications.
Click New notification and fill in:
Text of the notification.
Description / body of the notification.
Image (optional).
Sender — the name the attendee will see.
Button to redirect to a module (optional) — once tapped in the app, the attendee jumps to, for example, My Agenda, the Agenda, a specific exhibitor, and so on.
Targeting — all assigned, only Attending, only those who showed up on site, only the web app, only the mobile app, or a specific group.
Schedule — send now or on a specific date and time.
Allow comments — turn on or off.
In the app — the notification appears in the Notifications section as a feed. Newest at the top.
As a push notification — if the attendee has the mobile app installed and notifications enabled on the phone, a push arrives.
In the web app — without push notifications (browsers have limited support). The attendee sees the notification when they open the app.
The attendee can like and comment on the notification (if the organizer allowed comments).
Morning welcome on the day of the event — "Good morning, we're looking forward to seeing you, registration is open from 8:00."
Reminder on the day of the event — "We start in an hour, don't forget to have your QR ticket ready."
Agenda changes — "Pavel Novák's keynote moves from 14:00 to 14:30." Ideally with a button to the Agenda.
Refreshment info — "The coffee break is open in the main foyer."
Contest or activity — "Don't forget to fill in the survey and collect points for the Leaderboard."
Follow-up — "Thanks for coming. Here are the photos and the recording link."
Notification for a specific group — "VIP attendees: main rehearsal at 16:00 backstage."
Just like with E-mail campaigns, you can schedule Notifications for a specific date and time. For the day of the event, prepare a series of notifications in advance (welcome, agenda reminder, coffee break, feedback, closing). On the day itself you only react to changes; the routine runs on its own.
Notifications E-mail campaign Delivery Attendee app + push E-mail inbox Delivery requirement Attendee in the app (mobile / web) E-mail address Interactivity Likes, comments Only a button click Reaction speed Immediate (with push) Depends on when the attendee opens the e-mail Best for Info during the event, contests, agenda changes Invitations, pre-event reminders, follow-up, tickets Offline reading Yes, in the app Yes, in the client Format Short text, image, button to a module Full e-mail with attachments
Before the event, campaigns lead (they reach the attendee even if they have not opened the app yet). During the event, notifications lead (fast, in-app, with push). After the event, combine both.
Just like campaigns, Notifications can target by groups. If you have a Speakers group, send only them a notification about the main rehearsal. If you have a workshop group, send them a reminder an hour beforehand. The groups must exist beforehand and have contacts in them — see Targeting communication by groups and statuses.
Notifications is a strong channel (a push notification goes straight to the lock screen). Too many notifications and attendees end up with a "nervous" app and start to ignore it. For a one-day event, do not exceed roughly 5–8 notifications per day.
Notifications is a news / news feed that the organizer schedules. It is not the system notification "your session in My Agenda starts in 15 minutes" — the app handles that one on its own based on what the attendee has saved. They are two different kinds of notifications that complement each other.
In targeting, choose all assigned with Attending status or a combination of web + mobile. Targeting Web app only sends the message only to people in the browser.
Push notifications work reliably only in the mobile app (iOS / Android). The web app has limited support. If push reach matters to you, communicate this in the Confirmation e-mail and encourage installing the app.
For fast communication during the event, use Notifications. The push arrives instantly. E-mail is a slower channel.
Keep the frequency reasonable. Group information together ("Good morning. Registration from 8:00. The agenda starts at 9:00 in the main hall. The Wi-Fi password is…"). Notifications sent in bulk lose their value.
For notifications where you do not want a discussion, do not turn on comments. Typically with system info (refreshments, agenda changes) comments do not need to be on.
Notifications live in the app. Anyone without the app will not see the message. For them, use an E-mail campaign — or in the Confirmation e-mail encourage them to open the app.
