Visitors & participants
2mee distinguishes the anonymous people on your site from the named contacts you enrol in an experience.
Visitor
Section titled “Visitor”A visitor is an end-user browsing a website where the 2mee snippet is installed.
- Tracked by a device fingerprint / UUID stored in a first-party cookie.
- Carries tags (behavioural labels) and attributes.
- Anonymous — visitors never have accounts and aren’t identified by default.
Participant
Section titled “Participant”A participant is a named contact enrolled in an experience — typically with a name and email.
- Created when an experience is triggered for a specific person — for example, by a webhook from your CRM.
- May be associated with a stage of a wider customer journey.
- Gets a participant shortcode — a personal link (e.g.
s.2mee.com/p98765) with session and expiry handling.
Linking identity
Section titled “Linking identity”A visitor starts anonymous. When an inbound event carries a client user id — your own id for the person — 2mee links it to a visitor:
- If that id is already linked to a visitor, the event attaches to that visitor.
- If it isn’t linked yet, the work is held against the id until a visitor links, rather than guessing.
Integrations can carry several ids at once. A visitor can hold, for example, a Segment
userId, a Segment anonymousId, and ids from other connected systems — each stored as a
{provider, namespace, externalId} link. Outbound events read the right id back so the
event lands on the matching person in the destination system. See
Connect Segment for a worked example.
Users (for contrast)
Section titled “Users (for contrast)”A user is a human with a 2mee portal login — one of your team managing experiences on behalf of your account. Users are not visitors or participants; they’re the people who build and operate 2mee.
Privacy note
Section titled “Privacy note”Raw inbound payloads, delivery logs and identity links can contain personal data. 2mee retains them with time-to-live expiry and supports data-subject erasure across these stores. If you have specific data-residency or retention requirements, raise them with your 2mee contact.