MarketSharp and PandaDoc Supported Merge Fields
This document outlines the supported merge fields in MarketSharp that can be used in PandaDoc templates. Merge fields allow you to dynamically populate PandaDoc documents with data from MarketSharp.
How to Write Merge Fields
- Merge Fields column represent the fields to use in PandaDoc templates, mapped to MarketSharp properties.
Merge fields must follow the syntax:[EntityType].[PropertyName] - EntityType: The type of data being referenced (e.g.,
Appointment,Company). - PropertyName: The specific field name for the data.
For example, to reference the primary salesperson of an appointment, the merge field would be:Appointment.Salesperson1
Merge fields are case-sensitive, and the exact entity and property names must be used as listed in the tables and sections below.
Supported Merge Fields by Entity Type
1. Company
Merge fields for company-level data are written as:Company.[PropertyName]
| PropertyName | Returns |
|---|---|
| AddressLine1 | The primary address of the company. |
| AddressLine2 | The secondary address line of the company. |
| BulkRatePermitNumber | The bulk rate permit number for the company. |
| BusinessReplyPermitNumber | The business reply permit number for the company. |
| City | The city where the company is located. |
| ContactName | The primary contact name at the company. |
| ContactTitle | The title of the primary contact at the company. |
| Country | The country where the company is located. |
| The company's email address. | |
| Fax | The company's fax number. |
| FirstClassPermitNumber | First class permit for the company |
| IncrementMailerNumber | Increment mailer number for the company |
| Name | The name of the company. |
| PermitCity | City where the company has their permit |
| PermitZip | Zip where the company has their permit |
| Phone | The company's primary phone number. |
| ReplyZip | Reply zip for the company |
| ReplyZipPlus4 | Replay zip plus 4 for the company |
| State | The state where the company is located. |
| Timezone | Timezone the company resides in |
| Website | The company's website URL. |
| Zip | The company's ZIP code. |
2. Contact
Merge fields for contacts are written as:Contact.[PropertyName]
| PropertyName | Returns |
|---|---|
| AddressLine1 | The first line of the contact's address. |
| AddressLine2 | The second line of the contact's address. |
| BusinessName | The business name of the contact. |
| City | The city where the contact is located. |
| ContactType | The type of contact (e.g., customer, prospect). |
| County | The county where the contact is located. |
| Email1 | The primary email address of the contact. |
| Email2 | The secondary email address of the contact. |
| Email3 | The tertiary email address of the contact. |
| FirstName | The first name of the contact. |
| LastName | The last name of the contact. |
| PrimaryPhone | The contact's primary phone number. |
| State | The state where the contact is located. |
| Title | The title of the contact (e.g., Mr., Mrs., Dr.). |
| Zip | The ZIP code of the contact's address. |
3. Quote
Merge fields for quotes are written as:Quote.[PropertyName]
| PropertyName | Returns |
|---|---|
| Date | The date when the quote was created. |
| Name | The name of the quote. |
| Notes | Notes associated with the quote. |
| TaxAmount | The total tax amount for the quote. |
| TaxRate | The tax rate applied to the quote. |
4. Appointment
Merge fields for appointments are written as:Appointment.[PropertyName]
| PropertyName | Returns |
|---|---|
| Date | The scheduled date and time of the appointment. |
| DateIssued | The date the appointment was issued. |
| Description | The description or details of the calendar event. |
| Notes | Additional notes related to the appointment. |
| Result | The result or outcome of the appointment. |
| ResultReason | The reason for the appointment's result. |
| Salesperson1 | The name of the first salesperson assigned to the appointment. |
| Salesperson1Bio | The bio of the first salesperson. |
| Salesperson1Email | The email address of the first salesperson. |
| Salesperson1Phone | The phone number of the first salesperson. |
| Salesperson1Title | The title of the first salesperson (e.g., Mr., Mrs.). |
| Salesperson2 | The name of the second salesperson assigned to the appointment. |
| Salesperson2Bio | The bio of the second salesperson. |
| Salesperson2Email | The email address of the second salesperson. |
| Salesperson2Phone | The phone number of the second salesperson. |
| Salesperson2Title | The title of the second salesperson (e.g., Mr., Mrs.). |
| SetBy | The name of the person who set the appointment. |
| SetByBio | The bio of the person who set the appointment. |
| SetByEmail | The email address of the person who set the appointment. |
| SetByPhone | The phone number of the person who set the appointment. |
| SetByTitle | The title of the person who set the appointment. |
| SetDate | The date the appointment was set. |
| Subject | The subject or title of the calendar event. |
| Type | The type of the appointment (e.g., meeting, call). |
5. Inquiry
Merge fields for inquiries are written as:Inquiry.[PropertyName]
| PropertyName | Returns |
|---|---|
| AddressJobSiteName | The name of the job site for the inquiry. |
| AddressLine1 | The first line of the address for the inquiry. |
| AddressLine2 | The second line of the address for the inquiry. |
| Canvasser | The name of the canvasser who recorded the inquiry. |
| City | The city where the inquiry was made. |
| Date | The date and time when the inquiry was made. |
| Directions | Any special directions for the inquiry. |
| Division | The division associated with the inquiry. |
| Notes | Notes or additional information about the inquiry. |
| Promoter | The name of the promoter associated with the inquiry. |
| State | The state where the inquiry was made. |
| Status | The current status of the inquiry. |
| PrimaryLeadSource | The primary lead source for the inquiry. |
| SecondaryLeadSource | The secondary lead source for the inquiry. |
| TakenBy | The name of the person who took the inquiry. |
| Telemarketer | The name of the telemarketer associated with the inquiry. |
| Zip | The zip code where the inquiry was made. |
6. Custom Fields
Usage Scope
Custom Fields are based on a per-company basis, meaning each company in MarketSharp can define its own unique set of fields. These fields are supported in PandaDoc and allow dynamic integration of company-specific data.
How Custom Fields Work
Custom Fields must be written exactly as they appear in MarketSharp. The field names are case-sensitive and should include their associated entity prefix when applicable.
Custom Field Merge Field Syntax
CustomField.[PropertyName]
For example:
- If a company has a custom field for the color of a house, the merge field would be written as:
CustomField.Color of Home
7. Pricing Tables
Pricing Table Availability
The pricing table cannot be directly added to a document or template.
How to Use a Pricing Table
- To include a pricing table, users must copy an existing template that already contains one.
Limitations
- Items from the content library cannot be added to a document or template using the Embedded Editor.
8. Image Blocks
Limitations
Some image blocks are by default utilizing merge field functionality. (e.g., Company.Logo or Appointment.Salesperson1Picture) They cannot be added directly to templates
- The image name is not exposed in the Embedded Editor to change.
- Because of this, image blocks linked to merge fields must be copied from an existing template, similar to pricing tables.
Getting Merge Fields Set Up in PandaDoc
There are a few ways to get merge fields ready and integrated into your PandaDoc templates. Merge fields allow you to dynamically populate documents with data from MarketSharp. Below are the methods you can use to include these merge fields.
1. Adding Variables in the Template/Document
The most straightforward way to add merge fields to a PandaDoc template is by directly inserting them as variables in the document. These variables follow the same syntax: EntityType.PropertyName
For example:
- [Company.Phone]: This will insert the phone number of the company.
- [Appointment.Salesperson1]: This will insert the name of the first salesperson for the appointment.
To use this method, simply type the merge field where you want it to appear in the document, ensuring it follows the correct format. - Simply start by typing the open bracket character - [
2. Using the Fields in PandaDoc
Another way to add merge fields is by using the "Fields" in PandaDoc. Supported fields are Text Fields, Checkbox and Date fields. Here is how you can set up a field for a merge
For example:
Inquiry.Canvasser: This will insert the name of the canvasser associated with the inquiry.
This method allows you to add merge fields more easily by filling out the Merge Field text box in PandaDoc's field properties.
Here's an Example with Sales Rep 1
- In your PandaDoc document, click/drag to add a field.
- Click on the field and choose the Properties icon .
- In the Merge Field text box, enter the merge field in the same format as the variables (e.g.,
EntityType.PropertyName). - This is how it will appear in the Template prior to document generation. Once the document is generated, the field will be filled with the data in the Salesperson1 field from MarketSharp.
3. Checkbox Fields for Custom Fields
PandaDoc also supports merging data into checkbox fields, particularly for Custom Fields. You can provide a checkbox with a merge field name because these fields have a text box for merge fields.
To map a checkbox to a custom field in MarketSharp:
- In your PandaDoc document, click/drag to add a field.
- Click on the field and choose the Properties icon .
- Set the merge field name for the checkbox to correspond to the custom field in MarketSharp.
For example:
- CustomField.Check Box: This will map the checkbox to a custom field in MarketSharp. If the custom field is checked in MarketSharp, the checkbox will be checked in PandaDoc.
This allows you to dynamically control checkboxes based on the data from MarketSharp.