Merge tags allow you to automatically personalize documents and templates with dynamic information. When a document is created or sent, merge tags are replaced with real data—such as recipient details, sender information, company data, or CRM values. This ensures every document is tailored without requiring manual editing.
Merge tags work across the Editor, Templates, and Messages, and are essential for creating scalable, personalized document flows.
1. What Merge Tags Do
Merge tags act as placeholders that GetAccept replaces with actual values.
Examples:
{{recipient.firstName}}→ John{{sender.title}}→ Account Executive{{company.name}}→ ACME Inc.{{deal.value}}→ €12,500
This keeps content accurate, personalized, and consistent.
2. Types of Merge Tags
Merge tags are grouped by the type of data they pull from.
Recipient Tags
Insert data related to the individual receiving the document:
Name
Email
Phone number
Company name
Useful for greetings, personalization, and contract fields.
Sender Tags
Pull information about the user sending the document:
Name
Title
Contact information
Company details
Helpful for signature blocks, sign-offs, and branding.
Company & Entity Tags
Insert details from your GetAccept entity settings:
Logo
Address
Organization name
Default company information
Used for headers, footers, and branding consistency.
Document Tags
Pull data specific to the document:
Document name
Document value
Expiration date
Custom data fields
Ensures key details stay consistent throughout the document.
CRM Merge Tags (optional)
Available when your CRM is connected (Salesforce, HubSpot, Dynamics, Pipedrive, etc.)
Use these for:
Deal value
Close date
Company industry
Line items (via merge blocks)
Owner information
CRM tags allow high levels of automation when documents are created from CRM workflows.
3. Where Merge Tags Can Be Used
Merge tags work in most content areas, including:
Editor text elements
Templates (Editor or PDF with field mapping)
Document messages
Email templates
Communication templates
Content Library snippets
If a field supports text, it typically supports merge tags.
4. How Merge Tags Update
Merge tags populate at the moment the document is created or updated.
They update when:
You create a document from a template
You assign recipients to template roles
You change CRM data before generating the document
You edit document details (e.g., updating value or company name)
If required data is missing (like recipient phone number), the merge tag appears empty until the information is provided.
5. Merge Tag Best Practices
To ensure tags behave correctly:
Always assign template roles, so tags know which recipient to reference
Keep CRM fields clean and consistent
Use fallback values when needed (e.g., “Hi {{recipient.firstName | default:'there'}}”)
Avoid placing merge tags inside pricing tables
Keep merge tags inside text elements—not images or embedded media
These practices prevent formatting issues and missing values.
6. Common Issues & Why They Happen
Tag not populating → Missing recipient or CRM data
Wrong value inserted → Wrong role assigned
Tag stays blank → Field type unsupported or not mapped
Formatting looks strange → Tag placed in a styled area incorrectly
Each issue is typically fixed by updating the source data or adjusting template roles.
Summary
Merge tags automatically personalize your documents with real data—saving time while improving accuracy. They can pull information from recipients, senders, your organization, the document itself, or your CRM. Using merge tags effectively creates scalable, consistent, and dynamic document workflows.