company logo

Help center

Go to Happenee
Privacy policyContact sales
All collectionsCommunication and invitationsIn-app and flowThe attendee's journey from the microsite to the attendee app

The attendee's journey from the microsite to the attendee app

How to lead the attendee from the e-mail to the microsite, into registration, and into the attendee app.

Happenee is a communication platform with two channels — the microsite (a public business card with a call-to-action to register) and the attendee app (the environment where the attendee lives during the event — Agenda, ticket, Networking, Notifications). The organizer's job is to lead the attendee from the e-mail to the microsite, from the microsite to registration, and from registration into the app. Once in the app, the attendee does not return to the microsite — everything they need is already there.

Getting started

  • Set the flow in your head: e-mail → microsite → registration → Confirmation e-mail → attendee app.

  • Write the e-mail short and punchy — not the full event content. The job of the e-mail is to get the attendee to the microsite.

  • Put the full information on the microsite, with a Register button (or Buy ticket).

  • In the Confirmation e-mail, do not forget the entry into the app — a link, a Magic Link, or a note about the PIN / QR code.

  • For medium and larger events, offer the app — do not force it.

Details

Two channels — why both

Happenee is an event operations system that offers two communication channels:

  • Event microsite — the public business card. Anyone with the link can find it. Information about the event: what, when, where, who is speaking, the agenda, the partners. The call-to-action is Registration or Buy ticket.

  • Attendee app — a private environment for registered attendees. Mobile iOS, mobile Android, web version. Here you find the QR ticket, My Agenda, Networking, Notifications, the Agenda with the option to save sessions to favorites, chat with others, attendees and exhibitors with click-throughs.

Both are filled from the same content and engagement features — the Agenda, Speakers, Sponsors, and Exhibitors appear on the microsite and in the app. You fill it in once.

The ideal attendee flow

  1. Invitation e-mail or campaign — short and punchy, with a Register button. Goal: click and move on.

  2. Microsite — the attendee sees the details, the agenda, the speakers, the venue. If it appeals to them, they click Register.

  3. Registration form — they fill in their data, plus any workshop / accommodation / additional choices.

  4. Confirmation e-mail — with a PDF ticket containing a QR code, an ICS file for the calendar, and a link into the app.

  5. Attendee app — the attendee gets in via a Magic Link, a PIN, or by scanning the event QR code. There they find the ticket, the agenda, My Agenda, notifications, and Networking.

  6. On event day — the organizer sends an e-mail campaign with the ticket (QR code) and pushes Notifications in the app. The attendee arrives, shows the QR (from the app or e-mail), is checked in via the service app, and a badge is printed.

  7. During the event — the app is the main channel. My Agenda, Notifications, Survey, voting, Networking.

From registration onward, do not pull the attendee back to the microsite. Everything they need is in the app.

How to get the attendee into the app

Three ways the attendee can reach the attendee app:

  • Magic Link — the Confirmation e-mail or Invitation e-mail contains a link that signs them in directly.

  • PIN — the attendee opens the app and enters the PIN they received by e-mail.

  • Event QR code — the attendee scans a QR code (for example, from a badge) and the event is added to the app.

All three methods use the same e-mail address — the one used for registration. If the attendee has a white label app from your customer, they only see events from that workspace. On the Happenee brand they may also see events from other customers under the same e-mail.

How to talk about the app with attendees

Organizers often ask how to convince attendees to use the app. Useful sentences:

  • "Your ticket is in the app — just show it at the entrance."

  • "In the app you will find the current agenda and notifications, in case anything changes."

  • "You do not want to install it? We have a web version at this address."

The organizer's posture should be: offer, do not force. Some people install the app, some use the web version, some only print the PDF ticket from the e-mail. All three paths work.

Typical mental blockers

Organizers often say things like:

  • "Our people are not going to download an app."

  • "For our event the app is pointless."

  • "We will put everything on the microsite, that is enough."

From a product point of view:

  • The mobile app is voluntary — those who want it have it; those who do not use the web version or stay on the e-mail.

  • The web app does not require installation — it runs in the browser. An attendee who does not want the app simply clicks the link and works with it in a mobile browser.

  • The app adds value: My Agenda (the sessions the attendee saved or registered for), Notifications with push, Networking (saving contacts, chat, scheduling meetings), the QR ticket, registration data at hand.

  • For the organizer, the app is a fast channel for changes — moving a session, shifting the start time, info about catering.

Event size and the role of the app

  • Small event (up to about 50 people) — microsite and a simple registration are enough. The app is not strictly necessary, but it is worth at least offering it. It is "free extra" — you fill in the content once and it is in both channels.

  • Medium event (50–300) — the app is useful for My Agenda, Notifications, and the QR ticket.

  • Larger event (300+) — the app is the key channel. Networking, engagement, the Online module, Notifications.

Even at small events the rule holds: "Whether they download it or not does not matter, but let them use it across the whole flow."

Keep the e-mail footer, the microsite, and the app consistent

If you have a white label setup (your own domain, logo, app under your own name), the microsite, e-mails, and app look like your brand. If you run on the Happenee brand, e-mails come from invitation.happenee.com, the microsite is on happenee.com, and the app uses the main Happenee brand. A consistent experience across channels helps the attendee recognize that it is still the same event.

Common pitfalls

The organizer crams the Invitation e-mail with all the event information so the attendee does not have to click — the e-mail is huge, unreadable, and the attendee never reaches the microsite

Keep the e-mail short. Its only job is to point to the microsite. Leave the agenda, speakers, and details there.

The organizer forgets the link into the attendee app in the Confirmation e-mail and the attendee does not know how to get in

The Confirmation e-mail should contain either text with links to the mobile app (App Store, Google Play) and the web app, or an HTML button Open in app. After clicking, the Magic Link signs the attendee in directly.

The organizer pulls the attendee back to the microsite after registration because there is more information there than in the app

The content on the microsite and in the app is filled from the same features. If you have filled in the agenda, it is in the app too. Instead of "look at the microsite" write "open it in the app".

The organizer blocks the app with the argument "Our people will not download it" and deprives attendees of My Agenda, Notifications, and Networking

Offer the app, do not push it. There is a mobile version and a web one. An attendee who does not want to install gets the web version with the same content (except for push notifications).

On event day the organizer sends an e-mail saying "Open the app and you will see your ticket" — but most attendees never opened the app

On event day, send an e-mail campaign with the PDF ticket attached (the QR code itself) and reference the app in the body. Whoever opens the app, great. Whoever does not has the ticket in the e-mail.

Related articles

  • Microsite vs attendee app: how to think about the attendee flow

  • How the Event microsite works

  • How the attendee app and its home screen work

  • How the Confirmation e-mail works

  • Using Notifications in the attendee app

  • Communication flow on the event day

  • What to do when an attendee cannot get into the app

Rate this article
😞
😐
😁