CRM merge tags allow you to automatically pull information from your connected CRM into your GetAccept documents and templates. When a document is created from a CRM workflow or when CRM data exists on the deal, these tags populate instantly, ensuring your proposals and contracts stay accurate and consistent without manual editing.
CRM merge tags are essential for scaling automated document creation and maintaining alignment between your CRM and GetAccept.
1. What CRM Merge Tags Do
CRM merge tags act as placeholders linked to your CRM’s deal, company, or contact data.
When the document is generated, GetAccept fills each tag with live CRM information, such as:
Deal name or opportunity title
Company name and industry
Contact details
Deal value or amount
Close date or renewal date
CRM owner information
Product/line item lists
These tags ensure your content stays accurate, synchronized, and fully personalized at scale.
2. Types of CRM Merge Tags
CRM merge tags vary depending on the CRM you use, but they generally fall into the following categories:
Deal/Opportunity Fields
Deal name
Deal value
Close date
Stage
Owner
Currency
Custom fields
These are commonly used in proposals, quotes, and contract summaries.
Company/Account Fields
Company name
Industry
Address
Website
Employee count
Region
Helpful for personalizing introductions or pre-filled contract details.
Contact Fields
Primary contact name
Email
Phone number
Title
Department
Used in greetings, signature blocks, and recipient personalization.
Line Item Fields (Merge Blocks)
If your CRM supports product syncing (Salesforce, HubSpot, Dynamics, etc.), you can use line item merge blocks to:
Pull products into a pricing table
Display item descriptions, quantities, and prices
Automatically insert totals or discounts
Line item merge blocks are essential for building scalable pricing workflows.
3. How CRM Merge Tags Populate
CRM merge tags populate when:
A document is created directly from the CRM
A template with CRM tags is used in a CRM-triggered workflow
CRM fields are updated prior to document creation
A sender manually refreshes CRM data (if supported by the integration)
CRM tags do not retroactively update after a document has been created unless the document is regenerated or updated through a new version.
If CRM data is missing at creation time, the merge tag will remain blank.
4. When CRM Merge Tags are Available
CRM merge tags are available when:
Your CRM integration is active and connected
You create documents from the CRM or use CRM-linked templates
Your template contains merge tags mapped to CRM fields
The CRM object data exists at the time of document creation
Different CRMs support different sets of tags depending on permissions, field types, and the integration setup.
5. Best Practices for Using CRM Merge Tags
Assign template roles
Many CRM tags depend on correct role mapping (e.g., “Primary Contact”).
Use consistent naming in your templates
Avoid mixing CRM merge tags with manual text.
Validate CRM data before sending
If key fields are empty in the CRM, the merge tag will also be empty.
Use line item merge blocks for pricing
This keeps product data accurate and synced.
Avoid placing CRM tags inside images or complex formatting
CRM tags work best in text-based content.
6. Common Issues & Why They Happen
Tag not populating
Missing CRM data
Field not accessible due to permissions
Template role not assigned
Document not generated from CRM
Wrong values appearing
CRM record contains outdated information
Incorrect role mapping
Wrong CRM object linked
Line items not appearing
Products not added to the CRM deal
Template missing a line item merge block
Integration does not support item syncing
Each issue is typically resolved by reviewing CRM data or adjusting template configuration.
Summary
CRM merge tags allow documents to automatically populate with accurate CRM data, making it easier to build large-scale, personalized proposals and contracts. They support deal fields, contact details, company information, and line items — giving your templates dynamic power and ensuring consistency across platforms.