ENA Feedback

Sessions & QR Activation

Understand how a QR code scan creates a session and how to manage active survey deployments.

Last updated on

What is a session?

When a visitor scans a survey QR code, Enafeedback creates a session record. The session tracks the entire interaction from first scan to final submission.

Visitor scans QR → Session created (status: started)
Visitor answers questions → Session updated (status: in_progress)
Visitor submits → Session closed (status: completed)

If a visitor abandons the form without submitting, the session remains as in_progress and eventually expires.

Session data

Each session records:

FieldDescription
Survey versionThe exact version of the survey shown
LocationWhich location the poster was deployed to
Started atTimestamp of the first scan
Completed atTimestamp of final submission
DurationTime from start to completion
AnswersAll question–answer pairs
DeviceBrowser and OS (from user agent)
LanguageThe language the form was shown in

Sessions do not record the visitor's identity, IP address, or device fingerprint by default.

Deploying a survey to a location

Before a QR poster can show a survey, the survey must be deployed:

  1. Navigate to Survey Management and open your survey.
  2. Click Deploy.
  3. Select one or more locations.
  4. Choose the poster template to use.
  5. Click Confirm deployment.

The system generates a unique QR code for each location–survey pairing and links it to the poster.

Activating and deactivating

A deployed survey can be paused without removing the deployment. When paused, the QR code redirects visitors to a "Currently unavailable" message instead of the form.

  • Activate — Start accepting responses.
  • Pause — Temporarily stop accepting responses (e.g., during an event).
  • Remove deployment — Unlink the survey from a location entirely.

Incomplete sessions

Incomplete sessions (started but not submitted) are visible in Survey → Sessions → Incomplete tab. This view helps you understand where visitors drop off.

Common drop-off causes:

  • Survey is too long
  • A required question is confusing
  • Network connectivity issue at the location

Session expiry

Sessions that remain in_progress for more than 4 hours are automatically marked as expired. Expired sessions are excluded from completion-rate calculations.

Re-scanning

If the same device scans the same poster within a configurable cooldown window (default: 30 minutes), the existing session is resumed rather than creating a new one. This prevents accidental duplicate submissions when visitors refresh the page.

Viewing sessions

Go to Survey → [Survey name] → Sessions to see all sessions for a specific survey. Filters available:

  • Date range
  • Location
  • Status (completed, in progress, expired)
  • Language