What is a push notification?

A push notification reaches an attendee whether or not they have the app open. That reach is the whole value, and it is finite: permission can be revoked once, silently, and never comes back.

In practice at an event

Three to five a day is the working budget at a full-programme conference. Nothing before 7:30 in the morning, because attendees are in different hotels and some arrived from a different time zone. Nothing after the last programmed item, because an evening interruption is paid for the next day.

Write them the night before and schedule them. A notification composed live is where a typo reaches four hundred phones.

Front-load the information: “Keynote moved to Windsor Suite, starts 09:15” rather than “Important update”. Lock screens truncate, and the first four words carry the message.

What to look for

The single most important behaviour is deep-linking: does tapping it open the exact session, announcement or thread it refers to, or the app’s home screen? A notification that makes the attendee do the work twice is how permission gets spent.

Then check segmentation. A room change matters to the people who saved that session and is noise to everyone else. And check delivery reporting, because sent is not delivered and the gap is diagnosable on day one.

How event67 handles it

Announcements and messages deep-link to the exact post or thread rather than to the home screen. Notifications can publish now or be scheduled to push at a set time, so the predictable sends are written in advance. Delivery is tracked, which is what turns a first-morning gap between sent and delivered into a fixable problem rather than a mystery.