Engagement

See how your audience took part. When guests sign in and use interactive modules — voting, bidding, checking in, answering a survey — EventSync records each interaction, attributed to the guest, and shows it back to you in the Dashboard's Engagement page: per-guest timelines, live totals, funnels and cohorts, and one-click exports for the client report.

How it fits together

• Guests sign in on a device (optional — modules work without it). A signed-in guest's interactions are attributed to them.
• Modules record interactions. Every built-in module — auctions, polling, Q&A, raise-your-hand, leaderboard, guest list, feedback, word cloud, happy-face, photo booth, the cue-stack viewer — reports what happened, typed and attributed, as it happens. Custom modules can too (see Custom modules).
• The Engagement page assembles it all, live, into a view you can read during the show and export afterwards.

Guest identity & consent

Guests sign in from an interactive module using whichever method suits your event — scanning a QR from their invite, entering a code, or picking their name from your guest list. Once signed in, that device's interactions are tied to the guest until they sign out or hand over to someone else.

You can ask guests to consent to their engagement being used for analytics. Their choice is honoured: a guest who declines is still served by every module exactly as normal — their operational data (for example, that they checked in) still works — but they're excluded from the marketing-style analytics and exports. Consent is per event, and you decide whether declined guests appear when you deliberately choose to include them.

The Engagement page

Open Engagement in the Dashboard for the active event. It has two views, switched at the top.

Guests

A live, searchable list of everyone who took part, with a summary header — total guests, how they signed in, and a card per module showing interactions and unique guests. Expand any guest to see:

• Their sessions — when and how they signed in, on which device.
• Their interaction timeline — every action in order, with the detail that matters (which item they bid on and how much, which option they voted for, their survey answers), not just a count.

Export to CSV flattens the guest list — one row per guest with per-module counts — for the post-event report.

Analytics

The Analytics view turns the raw interactions into charts, built from whatever your modules recorded — no set-up required. It offers:

• Breakdowns — pick an interaction (say, drinks ordered, or bids placed), group it by a category (drink, or item) or by a guest attribute, choose a measure (a count, or the sum/average of a number like amount), and read it as a bar chart with a time-series and filter chips. Most-popular-drink, total raised per item, votes per option — all fall straight out.
• Funnels — pick an ordered set of steps (for example: signed in → voted → entered the prize draw) and see how many guests reached each step, with conversion and drop-off.
• Cohorts — break any breakdown down by a guest attribute (table, seat, category, how they signed in) to compare groups.
• Saved views — save a breakdown or funnel you've built and reload it with one tap, so the charts you'll want at the client debrief are ready.
• CSV export of any breakdown, filtered exactly as on screen.

Which modules feed it

Every built-in interactive module reports engagement automatically — there's nothing to switch on. Examples of what each records:

Custom modules

Modules you build yourself can record engagement too. A custom module declares the interactions it wants to track and calls a single function when they happen; EventSync validates and attributes each one and it appears in the Engagement page alongside the built-ins. Developers should read Recording engagement — track() in the Module SDK.