Skip to content

Runtime Points Coordination

When the Event is running, Points are accruing live. This article covers what happens during the Event and how organizers can coordinate around Points in real time.

The Mobile App is where Points are earned and displayed; the Web App's Track surface is where organizers monitor totals.

During the Event

Once Points are enabled and configured, most accrual is automatic:

  • Participants log into the Mobile App → Points awarded
  • Participants upload a profile photo → Points awarded
  • Participants post in the Event Feed or a Room → Points awarded
  • Participants scan a custom QR code → Points awarded

The organizer typically does not need to take action for each award.

Where custom QR codes go

The organizer-driven part of Points is placement. Custom QR codes need to be visible at the right places. Practical considerations:

  • Print at a readable size — too small and phones won't decode reliably; aim for at least 2 inches square
  • Place at eye level — table tents, lanyard-height signs, posters
  • Lighting matters — dim rooms reduce scan reliability; consider printing on light backgrounds
  • Distribute thoughtfully — one QR at every booth encourages exploration; clustering codes in one area concentrates traffic there

Some organizers print Point QR codes onto session decks so a participant who attends a talk can scan from their seat. Others place them at session entrances or sponsor booths.

Online vs offline scanning

Points-related scanning behavior:

Mode Behavior
Online Scan registers and Points award within seconds
Offline Behavior depends on configuration; Points may be deferred until reconnection

Points scanning generally benefits from connectivity. For Events at venues with poor connectivity, place QR codes in areas where participants are likely to have signal.

For the broader scanning model, see QR Codes & Scanning in Eventene.

Monitoring Point activity

Organizers can watch Points accrue through the Web App:

  • Open the Event
  • Go to Track
  • Review Point totals per participant — filter, sort, or export as needed

This is useful for:

  • Identifying disengaged participants — those with zero Points after several hours may not have installed the app or may need a nudge
  • Spotting leaderboard contenders — for end-of-Event recognition
  • Validating QR placement — confirming that a specific QR is being scanned (if it is not, the placement may need to change)

Common runtime issues

Issue What to check
Participants scanning but not earning Points Confirm they were online; confirm the QR is a Points-bearing QR (not a Lead capture QR or a participant's badge); ask them to reopen the Mobile App
A QR does not scan at all Try better lighting; confirm the print is clean; confirm the participant has granted camera permission to the Mobile App
One participant has dramatically more Points than expected They may have repeated a Point-earning action that was not intended to be repeatable; review the configuration
Points not appearing in Track Sync delay; refresh the page; verify the Event has Points enabled at the Event level

Operational staffing considerations

For Events running an active Points program:

  • Designate one person to watch Track for the first hour or two — catches misconfiguration early
  • Have a backup plan for QRs that don't scan well (a stack of printed replacements; a phone with the Mobile App open for confirming scans)
  • Brief Event Staff on how Points work so they can answer participant questions
  • Coordinate with the Messaging Center — a pinned post in the Event Feed reminding participants how Points work is a useful nudge

End-of-Event coordination

When the Event closes:

  • Final totals appear in Track
  • Export Point data if you plan to recognize participants
  • Announce winners or top participants through the Event Feed, email, or a closing session
  • Reflect on what worked — which actions earned the most engagement, which QRs scanned the most, what to keep or change next time

Each Event's Point system is independent. What worked or didn't informs the next Event's setup.

See Also