Overview of Merge Fields & Custom Variables
Vendi Today gives you several ways to make your emails, texts, forms, and workflows dynamic instead of writing the same static content over and over. Here's a plain overview of each, so you know which one to reach for.
Merge fields
Merge fields are placeholders that pull real data from a contact's record and drop it into your message automatically. They look like {{contact.first_name}} or {{contact.email}}. When the message sends, the placeholder is swapped for that specific contact's actual value.
- Standard fields — built-in fields like name, email, or phone. You can't rename or remove these.
- Custom fields — fields you've created yourself to track things specific to your business, like a membership tier or a preferred appointment day.
Custom values
Custom values are reusable pieces of static content you set once — your business address, a support phone number, a policy link — and reference anywhere with a {{custom_values.your_value}} tag. Unlike merge fields, they're the same for every contact; update the value once and every message or page referencing it updates automatically.
Custom objects
For data that doesn't fit neatly into a contact or opportunity record — like properties, vehicles, or event bookings — custom objects let you build your own structured record type with its own fields and its own relationships to contacts and opportunities.
A few things to know
- Merge field tags are case-sensitive:
{{contact.first_name}}works,{{Contact.First_Name}}doesn't. - If a merge field has no data to pull, it shows up blank by default — but you can set fallback text so it never looks broken (see the fallback values guide).
Quick reference
| Use this when you want to... | Use |
|---|---|
| Insert a contact's own data (name, email, custom field value) | Merge field |
| Insert the same static content everywhere | Custom value |
| Track a whole new type of record (property, vehicle, booking) | Custom object |
Was this article helpful?
