Skip to content
2mee Docs

Tags & attributes

Flows make decisions using two kinds of data on a person: tags and attributes.

Tags

Section titled “Tags”

A tag is a behavioural label applied to a visitor for categorisation and analytics.

  • Set by the SDK in response to visitor actions — page views, CTA clicks, custom events — and added or removed by CTA actions.
  • Examples: has-viewed-pricing, kyc-started.
  • Stored and audited, so you can see when a tag was added or removed.

Conditions in a flow commonly test how many of a tag a visitor has, or how long since a tag was applied.

Idempotency tags

Section titled “Idempotency tags”

Some tags exist purely to stop work repeating. When an inbound event is processed, an entry tag such as webhook-{messageId} is recorded so re-delivering the same message can’t restart someone’s flow. When an action fires, a completion tag is recorded so the action can’t double-fire. You don’t manage these — they’re how the engine stays exactly-once. See retries & idempotency.

Attributes

Section titled “Attributes”

An attribute is a value carried on a visitor or participant — for example an email, a phone number, a plan name, or a basket value.

  • Attributes arrive from inbound events and are mapped onto the visitor/participant record (e.g. traits.phone → mobile). You configure that mapping when you set up an integration or a webhook.
  • Flow conditions can test an attribute’s value, so the data your systems send can steer what 2mee shows.

Where they come from

Section titled “Where they come from”
inbound event ─▶ map payload fields ─▶ write tags + attributes on the visitor
                                       │
                                       ▼
                          flow conditions test them ─▶ actions fire
Section titled “Related”
Was this page helpful? Tell us / report an issue ↗