Lookback doesn’t have a dedicated “screener ID” field, but you can use custom identifiers to track participants in your research workflows - especially when integrating Lookback with external recruitment or screening systems.
The simplest way to do this is by asking your participant to enter a unique identifier in place of (or alongside) their name when they onboard for the session.
How it works
When a participant starts a session, they are prompted, to enter:
their name, and
their email address (depending on your setup)
Instead of (or in addition to) a real name (and/or email), you can ask them to enter a unique user or tracking ID (e.g., a screener ID, panel ID, tracking code).
Once entered:
that ID will appear in session metadata in the Lookback player, and
it will also show up in a column in the session feed CSV export.
This makes it easy to align Lookback sessions with your external data systems (e.g., CRM IDs, panel screener IDs, participant lists, or recruitment spreadsheets).
When to use custom identifiers
Use this approach when you want to:
link Lookback sessions to external recruitment or panel data
track how a participant was qualified or screened
match sessions with CRM or research database records
ensure consistency across tools during synthesis
This is especially helpful when working with external recruitment providers, screener systems, or participant panels where a consistent external ID is part of your workflow.
Best practices
Communicate the instruction before the session (e.g., in your participant invite email template).
Use clear, short alphanumeric identifiers (e.g., “P12345”, “AB-6789”).
Store your participant ID mapping spreadsheet securely and reference it when analyzing or exporting data.