The microsite and the attendee app are the two main channels through which an attendee interacts with your event. The microsite is a public web page with information about the event — accessible to anyone who has the link. The attendee app is the environment for registered attendees, available as a web version and a mobile app. Happenee is designed so that an attendee moves naturally from the microsite through registration into the app — and each channel plays its own role. Understanding this flow helps you set up communication that guides the attendee instead of pushing them.
Decide whether the event will use the microsite alone or the microsite together with the attendee app. The choice depends more on the event's size and complexity than on its type.
Understand the underlying logic: the microsite is for informing and registering, the attendee app is for living through the event itself.
You set content up once in Happenee — whether each content feature appears on the microsite, in the attendee app, or in both is controlled separately for each feature.
The microsite is the public web page for your event. It has its own URL and is accessible to anyone who reaches it through a link in the Invitation e-mail, a campaign, or social media. The microsite plays two main roles:
Information showcase — it presents the event, the agenda, the speakers, the venue, sponsors, FAQ, and anything else an attendee needs to know before deciding whether to attend.
Entry point into registration — from here the attendee continues into the Registration form or to ticket purchase.
The attendee app exists in two forms:
Web app — runs in the browser, nothing to install.
Mobile app — a native app for iOS and Android. For most enterprise customers — typically banks, insurance companies, IT firms, and healthcare organizations — the app is branded (white label), so attendees download the organization's own app under its name and icon.
The attendee app is the environment for registered attendees. They find the detailed Agenda, My Agenda with their registered sessions, Networking, Notifications, Polls, Questions from the audience, the QR ticket for entry, and other engagement features that are not available on the microsite or appear there in a simplified form.
In Happenee the channels are designed to chain into a single flow:
The attendee receives a short Invitation e-mail with a call to action.
The e-mail leads them to the microsite, where they find the basic information and either register or buy a ticket.
After registering, they receive a Confirmation e-mail with a QR ticket and links to download the mobile app or open the web app.
Further communication — updates, agenda details, networking, the day of the event itself — then runs primarily inside the attendee app.
A well-built Invitation e-mail is short and to the point. Its only job is to get the attendee onto the microsite — not to deliver every detail at once.
For smaller or one-off events, where the attendee just downloads a ticket and shows up, the microsite alone can be sufficient. Typical examples are gala evenings, single-occasion company events, and small gatherings of a few dozen people. The attendee app does not add enough value in those cases to outweigh the friction of installing it.
As soon as an event has an agenda, workshops, networking, polls, or a need to push announcements during the day, the attendee app starts to make sense. A useful rule of thumb: the bigger and longer the event, the bigger the payoff from the attendee app. Conferences, expos, multi-day gatherings, events with workshops — all of these are cases where the attendee app leads to real time savings and a better experience.
The attendee app is not mandatory for attendees. Some prefer the web version, others install the mobile one. As the organizer, you simply offer it in the Confirmation e-mail.
For some external client events, the organizer has their own marketing website and the Happenee microsite serves only as a registration layer — the attendee arrives from the company website, fills in their e-mail, registers, and goes back. In this mode, the microsite shows minimal content (often just the Registration form) and the event information lives on the main company website.
This approach has a downside: you lose the ability to show speakers, the agenda, and other information directly inside Happenee. The content has to be maintained twice — once on the company website and once in Happenee for the attendee app — or kept in sync through an API. The ideal state is to use the microsite as the full home for the event. The alternative mode is still valid if the organization's brand requires that all content sit on the company website.
The microsite is meant to inform and bring the attendee into registration. The attendee app is meant to guide the attendee through the event itself. When both roles are pushed onto the microsite, you lose engagement and overload the page.
Offer the attendee app as a service — both the web version and the mobile one. Let the attendee pick whichever works for them.
Stick to the logic: the microsite before registration, the attendee app after registration. The Confirmation e-mail clearly leads into the attendee app, and further communication then runs mainly through the app (Notifications, push notifications).
Decide by size and complexity, not by type. A large company conference needs the attendee app; a small client workshop may not.
