A stored answer goes into your copy as a token in double curly braces. You will rarely type one by hand (the builder inserts it for you and renders it as a pill), but knowing the shape helps when you are reading someone else's Experience.
The syntax
| What you write | What a visitor with the answer sees | What a visitor without it sees |
|---|---|---|
Hello, {{name}} | Hello, Sarah | Hello, |
Hello, {{name|Guest}} | Hello, Sarah | Hello, Guest |
Room {{room}} | Room 412 | Room |
Inserting one
- 1
Click into any text field in a block editor
Roughly fifty fields across the block library accept an answer, including headings, body text, button labels, promo boxes, accordion items and event descriptions.
- 2
Press the Answer button in the toolbar
The green braces icon. Its tooltip reads Insert an answer.
- 3
Find the answer
The picker groups them by reach: This Experience, This Project · name, Everywhere, and Other Experiences. Each row shows a badge, the label you gave it, and the raw token.
- 4
Type a fallback
The Fallback (if unset) field, with the placeholder e.g. Guest. Fill it in.
- 5
Press Insert an answer
It appears in your text as a pill reading name and fallback together. Click the pill later to edit the fallback or remove it.
If the picker is empty it says so: No answers collected yet. Add a Name Capture, Quick Choice or Custom Input block somewhere first.
Write the plain name, not the stored key
An answer set to This Experience is stored internally with a suffix, something like room_ab12cd. You do not write that. Write {{room}}: the renderer resolves the plain name for you, and the picker inserts the plain name automatically.
Where interpolation works
- Block copy
- Headings, body text, buttons, promo boxes, accordions, hours notes, event lists and sponsor lines all resolve answers before the page renders.
- Memory block prompts and greetings
- Quick Choice questions, Rating prompts, Custom Input labels, Quiz titles, Passport rewards, Welcome Back copy and the greeting shown after a capture block all resolve too. A Welcome Back block additionally gives you
{{visits}}, the visitor's total visit count. - Push notification copy
- Yes. NearField resolves answers on the server before sending, so a block labelled
{{name}} fed Hudsonpushes as Priya fed Hudson rather than losing the one word you cared about. A token with neither a value nor a fallback is dropped rather than pushed as noise.
Where it does not
- Email. Nothing NearField emails resolves answers. Write email copy that reads correctly with no personalisation in it.
- Read-aloud narration. The spoken version reads the raw field. NearField does detect when a visitor's own answers have personalised the page and skips the cached recording in that case, so nobody hears yesterday's audio over today's text, but the token itself is not spoken.
Answers that are lists
A Quick Choice that allows several selections stores a list. Dropped into a sentence it joins with commas, so Thanks for telling us: {{interests}} renders as Thanks for telling us: Reptiles, Birds. A selection that ends up empty falls back like any other unset answer.
Example
The Bellhaven Hotel: one greeting, written once
The check-in Marker carries an Email Capture block that also asks for a name. Both default to Everywhere.
Every room card on the property opens with a Heading reading Welcome back, {{name|to The Bellhaven}}. A guest who gave their name reads Welcome back, Marcus. A guest who did not reads Welcome back to The Bellhaven, which is a sentence someone wrote on purpose rather than a gap.
Can I use an answer collected on a different Experience?
Only if that answer's reach allows it. The picker groups by reach and shows you an Other Experiences section, but an answer set to This Experience will not resolve on a different page.
Can I put an answer inside a link?
You can put one in a button label. URLs do not resolve answers today.
What if I rename the answer after writing the copy?
The copy keeps the old name and stops resolving, which renders as your fallback. Search your Experiences for the old pill and reinsert it.
Does the visitor see the braces if something goes wrong?
No. An unresolved token renders as its fallback, or as nothing. Stray braces never reach the page.