The panel properties tabs
What each of the seven tabs on a screen does — the question, the layout, the wording, the page settings, the colours, the images and the tracking.
Open a panel step and you get Panel Properties, with seven tabs. This is what each one is for.
#Interaction — the question
The tab you will use most. It defines what this screen asks.
| Field | What it does |
|---|---|
| Question / Description | The wording the visitor reads above the input. |
| Identifier (Variable Name) | The name the answer is stored under. Short and uppercase — NAME, EMAIL, BUDGET. |
| Input Type | What kind of answer: text, email, buttons, a date, an upload. See Question and input types. |
| Next/OK Button Label | The wording on the continue button. Defaults to OK. |
| Validation Method | What counts as an acceptable answer. |
| Add to Dataset | Optionally file this answer into one of your data tables. |
The tab reminds you how to reuse the answer later: an identifier of NAME
becomes $NAME.
Leave the question and input type empty and the screen simply shows content with a continue button — which is what you want for a welcome or thank-you screen.
#Validation methods
| Method | What it accepts |
|---|---|
| No Validation | Anything. |
| Default Validation | Whatever suits the input type — a real email address for an email field, and so on. |
| Mask Pattern | A shape you define. Use 9 for a digit, A for a letter, * for any character. 99999 is a five-digit code. |
| Min/Max Range | A value or length between two bounds. On a multiple-select list this is instead how many options may be ticked. |
| Must Be From List | One valid answer per line; anything else is rejected. |
| External Webhook | Another system decides. Tayon calls it and accepts or rejects based on the reply. |
You can write your own Validation Error Message so a rejected answer says something helpful rather than something generic.
#Template — the layout
Pick the visual layout for this screen from the available templates. The template decides which content slots, colour slots and image slots exist — which is why the Content, Colors and Images tabs tell you to select a template first until you have chosen one.
#Content — the wording
The text that fills the template you picked: the title, the subtitle, the body text, and any slot the template defines. Some slots count characters against a limit as you type.
Depending on the template, this is also where you put a video URL (YouTube, Vimeo and other embed links are supported), a booking link, a button URL, or raw HTML.
You can use variables here. Thanks $NAME on a screen after the name question
prints the name back.
#Settings — the page
Two things, and neither is obvious from the tab name:
- Page Name — an optional name that lets this screen be linked to directly, so you can send someone straight to the middle of the flow rather than the beginning.
- Show Footer — whether the site’s footer appears on this screen. Turning it off is normal on a full-bleed opening screen.
It also shows this step’s published identifier, or not published yet if the step has never been through a publish.
#Colors — this screen only
Overrides the site-wide colours for this screen. Backgrounds, title, subtitle, body text, buttons — whichever slots the template offers.
Use it sparingly. A closing screen with an inverted background reads as deliberate; five screens that each look slightly different read as broken. Set the defaults site-wide under Settings → Branding and override here only where you mean it.
#Images — this screen only
Select or replace the images this template uses. You pick from your image gallery or upload a new one — PNG, JPG or GIF up to 10 MB.
#Tracking — the analytics
Fire an analytics event when a visitor reaches this screen.
| Field | Use |
|---|---|
| Meta Pixel Event | A standard event name — Lead, CompleteRegistration, Contact, ViewContent, AddToCart, Purchase. |
| Google Tag Trigger | An event name sent to Google Tag Manager. |
| Custom Panel Script | JavaScript that runs when this screen is shown. |
The Pixel and Tag IDs themselves are set once for the whole site under Settings → Tracking. These per-screen fields only say which event to fire where.
#Saving
Save in the properties stores the step. You still need Save Flow and then Publish before a visitor sees any of it.
Updated: