What is a deep link?

A deep link points inside an app. Tapping it lands the attendee on the session that moved, the announcement that was posted, or the thread that was replied to — not on a home screen from which they have to navigate.

In practice at an event

Every notification an event app sends should be a deep link. “Keynote moved to the Windsor Suite” that opens a home screen has made the attendee do the work twice: read the message, then find the session. Two or three of those and notifications become something to dismiss rather than read.

Deep links matter beyond notifications too. A link in an email, a QR code on signage, a link shared between attendees — each should land on the thing it names. The failure is silent, which is why it is worth testing rather than asking about.

What to look for

Test this in a demo rather than asking about it. Have the vendor change a session’s room and send a notification about it while you watch, then tap the notification on a phone. Where you land is the answer.

Check the edge case too: a deep link to something that has since been deleted should degrade gracefully rather than showing an error screen. Schedule changes create these.

How event67 handles it

Announcements and messages deep-link to the exact post or thread they refer to. Because the same mechanism carries schedule changes, an attendee who saved a session that moves receives a notification that opens that session directly. This is one of the specific behaviours worth verifying in any product you are evaluating, ours included.