Concepts overview

This section explains the ideas the rest of the docs assume. Read it once and the portal, the API and the integrations all make more sense.

The shape of it

• Experiences & cards — what you build and deploy. The hierarchy is experience → card(s) → template.
• Flows — the graph that decides when an experience starts and advances, and what actions it fires.
• Visitors & participants — who 2mee shows things to: anonymous visitors and named participants.
• Tags & attributes — the behavioural labels and values that flows test.
• Goals — the outcome a flow aims for, and what happens when it’s reached.
• Glossary — authoritative one-line definitions for every term.

How a message reaches a person

Your data / a visitor action          2mee
   ─ inbound webhook / event ──▶   tag the visitor · evaluate the flow graph
                                   · start or advance the experience
                                   · show the card
   ◀── outbound webhook / event ─   report what happened to your systems

Inbound and outbound both go through the same engine. The Webhooks reference and Integrations sections cover the edges; this section covers the middle.

Naming

We use precise names on purpose. An experience is made of cards, and a card applies a template with an outlet. The glossary is the source of truth for terminology.