About customer accounts
Let participants and loyalty members sign in to OmniLab experiences with their own account for a personalised experience.
Let your customers sign in to OmniLab experiences with an account you already manage, so OmniLab recognises returning participants and personalises what they see. This page is for your IT or identity team.
Customer accounts — sometimes called CIAM (Customer Identity and Access Management) — connect your end-users' existing accounts to OmniLab. This lets OmniLab recognise a returning participant, personalise what they see, and connect their activity back to your systems.
This is different from SSO for your internal team. CIAM is about your customers or participants, not your employees.
What the participant experiences
The participant leaves OmniLab, signs in with the account they already have with you, and comes straight back to where they were. Done well, it feels like one continuous experience rather than a detour.
The participant opens the experience
They are anonymous at this point.
They choose Sign up or Log in
OmniLab remembers the page they were on.
OmniLab sends them to your identity system
Your own sign-in screen, your own branding.
They sign in with the account they already have
Password, one-time code, social login — whatever you support.
Your system confirms who they are to OmniLab
OmniLab returns them to the page they left
Now recognised, with their history and entitlements available.
They continue the experience as a known participant
The participant returns to the exact page they left, not to the campaign home page.
The participant opens the experience
They are anonymous at this point.
They choose Sign up or Log in
OmniLab remembers the page they were on.
OmniLab sends them to your identity system
Your own sign-in screen, your own branding.
They sign in with the account they already have
Password, one-time code, social login — whatever you support.
Your system confirms who they are to OmniLab
OmniLab returns them to the page they left
Now recognised, with their history and entitlements available.
They continue the experience as a known participant
Steps 3 to 5 happen on your side. OmniLab hands the participant over and waits for them to come back.
What this enables
- OmniLab can identify a participant across multiple sessions and campaigns.
- Reward history, registration data, and personalised content can be tied to a known account.
- Participants do not need to re-enter their details every time.
How it works
Your development team connects your customer identity system to OmniLab. When a participant launches an OmniLab experience, your system passes their identity to OmniLab in a secure way, so OmniLab knows who they are before they interact.
This is a developer integration
Setting up customer accounts requires your development team to connect your identity system to OmniLab. Contact your OmniLab Customer Success Manager to discuss the right approach for your setup.
Where this shows up
The most common use is a kiosk or self-service terminal in-store: a loyalty member scans their card, and the identifier on that card is passed into the OmniLab experience so they play as a recognised member rather than filling in a form. See Kiosk URLs.
If your customer identity system is not connected, an experience that expects a known member cannot fall back to an anonymous session — the visitor is blocked. Confirm the connection is live before you test any card-based journey.
Getting started
- Describe your use case to your Customer Success Manager: which participant data OmniLab should know, which campaigns will use it, and which systems currently hold that data.
- Your Customer Success Manager will confirm the supported integration approach and involve the right technical contacts.
- Your development team implements the connection using the guidance provided.