Experience editor

The experience editor is where you build an experience — its cards and the flow that decides when it runs.

Layout

• Cards panel — the cards that make up the experience. Add, reorder and remove cards here.
• Canvas — a live preview of the selected card with its template.
• Inspector — settings for whatever you’ve selected (card, template, or a flow node).
• Flow view — the graph of start, conditions and actions.

Editing a card

1. Select a card to edit it.
2. Choose its template (the chrome). Start with Standard unless you need a widget bar or a centred/blank layout.
3. Set the card’s CTA and its link. The template’s outlet is where card content sits — its content is currently being reworked.
4. Optionally add card content beyond the outlet — a form, an upload, a confirmation or a redirect.

Editing the flow

The flow is a graph you edit visually:

• Start — how the experience is entered (a visitor action or an inbound webhook).
• Condition — gate the next step on a tag count, time-since, or an attribute value.
• Action — show a card, or fire an outbound webhook/integration event.

The flow graph is saved with the experience, so your logic versions alongside your content.

Field mapping lives here

When an inbound event drives the flow, you map incoming payload fields to visitor attributes on the Start node. Map to the same attribute names your conditions read. See tags & attributes.

Saving, previewing, deploying

• Save keeps your changes to the designed experience.
• Preview shows the card as a visitor would see it.
• Deploy publishes it to an account and mints the shortcode. See deploying cards.

Related

• The model: experiences & cards · flows.
• A full walkthrough: your first experience.