Overview & Requirements for Session Check-In

Session check-in is a powerful feature in PheedLoop that helps event managers accurately track attendance for each session. This is especially useful for:

  • Continuing Education (CE) credit tracking — validating that attendees were present for the required duration.

    Access control — ensuring only eligible or pre-registered participants enter restricted sessions.

  • Event analytics — collecting attendance data to measure engagement and optimize future programming.

How Session Check-In Works

There are two primary ways to check attendees into a session:

  1. Staff or volunteer scans attendee badges using the PheedLoop Go! App or PheedLoop OnSite.
  2. Attendees check themselves in through the Self Check-In feature in the PheedLoop Go! Event App.

Both methods instantly update the Event Dashboard with attendance records.

System Requirements

Before you can use session check-in, your organization must meet the following requirements:

You must use PheedLoop’s OnStie Services in order to scan the QR code unique to attendee badges. Alternatively, you may use the e-badge feature in PheedLoop Go! To have attendees display their QR code. Please note, this option requires Enable App E-Badge to be enabled in the Event Dashboard, under Experiences > Mobile App > Settings.

In addition, you must have both the Mobile Event App & Virtual Event Portal Module and On-Site Check-In Power-Up assigned to your event.

When to Use Session Check-In

We find session check-in to be popular in a number of use cases, notably for tracking continuing education credits. These use cases include:

  • Tracking attendance for compliance or accreditation
  • Limiting access to VIP or paid add-on sessions
  • Measuring session popularity in real time
  • Streamlining entrance flow for high-demand presentations

With these requirements in place, you’re ready to explore specific check-in methods.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us