Using Merge Fields

Merge fields are placeholders you put in your documents that automatically replace themselves with real data — your client's name, the event date, your pricing, and more. They let you write a template once and have it personalize itself for every client.

How They Work

A merge field looks like this: {{client_name}}. When your client views the document, Gilded swaps it out for the actual client name from the event record. In the builder, you see the raw placeholder. In the preview and in the client-facing view, you see the resolved value.

If a merge field cannot be resolved (for example, you have not entered the venue name yet), it renders as blank — your client never sees the raw {{venue_name}} tag.

Inserting Merge Fields

In the document builder, you can type merge fields directly into the rich text editor using the double curly brace syntax. You can also use the merge field panel to browse available fields and insert them with a click.

Full Field List

Client Fields

• {{client_name}} — Primary client's full name
• {{client_email}} — Primary client's email address
• {{partner_name}} — Partner's full name (if provided)

Event Fields

• {{event_date}} — Event date, formatted
• {{venue_name}} — Venue name
• {{venue_address}} — Full venue address
• {{guest_count}} — Expected guest count

Pricing Fields

• {{total_price}} — Total contract value
• {{deposit_amount}} — Deposit amount due
• {{balance_amount}} — Remaining balance after deposit

Business Fields

• {{planner_name}} — Your name (from your profile)
• {{business_name}} — Your business name
• {{business_email}} — Your business email
• {{business_phone}} — Your business phone number

Where to Use Them

Merge fields work in any section of any document type — proposals, contracts, and combined documents. They also work inside templates, which is where they are most useful. Write your template with merge fields throughout, and every document you create from that template gets personalized automatically.

Common places to use them:

• Opening paragraph: "Dear {{client_name}}, thank you for considering {{business_name}} for your wedding on {{event_date}}."
• Payment terms: "A deposit of {{deposit_amount}} is due upon signing. The remaining balance of {{balance_amount}} is due 30 days before the event."
• Signature block context: Pricing summaries and party names

Tips

• Fill in your event details first. The more data you have on the event record, the more fields resolve correctly when you preview or send.
• Preview before sending. The document preview shows you exactly what your client will see, with all merge fields resolved. Catch any blank spots before the document goes out.
• Pricing fields update automatically. If you change the contract value or deposit amount on the event, those merge fields reflect the new numbers the next time the document is viewed.