Skip to main content

Custom Tokens

The placeholders that pull reservation, guest and property data into a message, plus your own custom values and the limits on what they can hold.

11 articles
Custom tokensStore your own values against a property, rate plan, space type, or space, and pull them into any campaign.
Policy tokensThe token categories for the cancellation and no-show policies attached to a booking.
Reservation tokensThe token categories that carry the booking itself, from dates to the booking reference.
Property tokensThe token categories carrying each property's address, contact details, and branding.
User tokensThe token categories for the people on a reservation, including the booker and the primary guest.
Room and space tokensThe token categories for the room a guest is in and the type of space it belongs to.
Other tokensThe token categories covering integrations, consent, city tax, company bookings, and operators.
Custom token values are plain textWhy a link inside a custom token arrives as raw text, and how to add a clickable action instead.
Adding a "View in browser" link to campaign emailsGive guests a web version of your campaign email that looks exactly like the message they received, for when their email app renders it poorly.
Add a two-click unsubscribe linkThe #{{unsubscribe_link()}} token lets guests opt out straight from a message, without going through the Digital Reception consent page.
Why the Digital Reception token name differs from the form nameA form's token is generated from its first saved name and never changes, even if you rename the form later.