Written by mikepalma Merge Tags are used to ensure that the contract fields are pulling the correct information from the CRM when prefilling information like first_name, last_name, address, etc or when inputting custom coding. What the merge tags will be will depend on the e-sign tool you are using, below are the guides that will tell you the merge tags of the common e-sign tools.
Formstack Sign
Formstack Sign offers the following text tags “types”:
- sig – to require a signature (Example: [sig|req|signer1])
- check – for creating a checkbox (Example: [check|req|signer1])
- initial – for requiring a signer’s initials (Example: [initial|req|signer1])
- date – will auto-populate the date when passed through Formstack Sign (Example: [date|req|signer1])
- text – will provide a short answer text box in place of the text tag (Example: [text|req|signer1])
- fullname- will populate the full printed name of the signer (Example: [fullname|req|signer1])
The second part signifies whether the text tag field is required or not
- req – a required field (Example: [sig|noreq|signer1])
- noreq – a field that is not required (Example: [initial|req|signer1])
The third part signifies which signer will need to interact with that text tag field. You can assign multiple signers to the same document.
- Signer 1 (Example: [sig|req|signer1])
- Signer 2 (Example: [sig|req|signer2])
- Signer 3 (Example: [sig|req|signer2])
https://support.webmerge.me/hc/en-us/articles/360029855351-Formstack-Sign
Adobe Sign
| {{Sig_es_:signer1:signature}} | A signature field assigned to the recipient identified as signer1. |
| {{Int_es_:signer1:initials}} | An initials field assigned to the recipient identified as signer1. |
| {{SigB_es_:signer1:signatureblock}} | A signature block assigned to the recipient identified as signer1. |
| {{OSig_es_:signer1:optsignature}} | An optional signature field assigned to the recipient identified as signer1. |
| {{OInt_es_:signer1:optinitials}} | An optional initials field assigned to the recipient identified as signer1. |
| {{SigStamp_es_:signer1:stampimage(25)}} | A stamp field that can be used as a signature option. Stamps are not required unless there are no other signature fields for the signer. |
| {{Cmpy_es_:signer1:company}} | A field for the recipient identified as signer1 to enter his or her company name. |
| {{N_es_:signer2:fullname}} | A read-only field for the recipient identified as signer2 to enter his or her full name. |
| {{Dte_es_:signer1:date}} | A read-only field containing the date of signature. |
| {{Em_es_:signer1:email}} | A read-only field containing the signer’s email address. |
| {{*Ttl_es_:sender:title}} | A mandatory field for the sender to enter his or her title. |
| {{price_es_:prefill}} | A field the sender fills in before sending the document. |
| {{address_es_:signer1}} | An optional field for the recipient identified as signer1 to enter his or her address. |
| {{*city_es_:signer1}} | A mandatory field for the recipient identified as signer1 to enter his or her city. |
| {{!price}} | A read-only field. Signers cannot change the value of this |
| {{[]}} | A checkbox. |
| {{[x]}} | A checkbox, checked by default. |
| {(Red)Color}} | A radio button that has the value of Red when selected. |
| {{Image1_es_:signer1:inlineimage(4)}} | An inline image field with a height of 4 lines |
| {{*Mobile_es_:signer1:phone}} | A mandatory phone field allowing US phone number format. |
| {{d_es_:signer1:num(>0,<60)}} | An optional number field allowing values between 0 and 60. |
| {{field_es_:showif(price>60)}} | A field that shows if the “price” has a value greater than 60. |
| {{TV_es_:calc([SubTotal]+[Tax])}} | A field whose value is automatically calculated as the sum of the “SubTotal” and “Tax” fields. |
https://support.webmerge.me/hc/en-us/articles/206527106-Adobe-Sign-formerly-EchoSign-
DocuSign
| Description | Short Tag | Long Tag (Turn on under More Options) |
| Signature | \s1\ | \signature1\ |
| Initial | \i1\ | \initial1\ |
| Date | \d1\ | \date1\ |
| Name | \n1\ | \name1\ |
| Title | \t1\ | \title1\ |
| Attachment | \attachment1\ \attachment1_2\ \attachment1_3\ \attachment1_req\ \attachment1_2_req\ \attachment1_3_req\ | \attachment1\ \attachment1_2\ \attachment1_3\ \attachment1_req\ \attachment1_2_req\ \attachment1_3_req\ |
| Text Box | \tbx_1_text\ \tbx_1_2_text\ \tbx_1_3_text\ \tbx_1_text_req\ \tbx_1_2_text_req\ \tbx_1_3_text_req\ | \tbx_1_text\ \tbx_1_2_text\ \tbx_1_3_text\ \tbx_1_text_req\ \tbx_1_2_text_req\ \tbx_1_3_text_req\ |
| Checkbox | \cb_1_yes\ \cb_1_2_yes\ \cb_1_3_yes\ | \cb_1_yes\ \cb_1_2_yes\ \cb_1_3_yes\ |
| Radio Button | \rb_1_1a\ \rb_1_1b\ \rb_1_1c\ \rb_1_1d\ \rb_1_1e\ | \rb_1_1a\ \rb_1_1b\ \rb_1_1c\ \rb_1_1d\ \rb_1_1e\ |
| Radio Button (required) | \rb_1_1_req\ \rb_1_2_req\ \rb_1_3_req\ | \rb_1_1_req\ \rb_1_2_req\ \rb_1_3_req\ |
Eversign
Eversign allows you to embed signature tags in your document so that they know where to place signatures, initials, dates, etc in your document during signing. Below are a few examples.
- Signer 1 Signature – [sig|req|signer1]
- Signer 1 Date – [date|req|signer1]
- Signer 1 Text (optional) – [text|noreq|signer1]
- Signer 2 Signature – [sig|req|signer2]
- Signer 2 Initials – [init|req|signer2]
https://support.webmerge.me/hc/en-us/articles/360014420472-eversign
HelloSign
HelloSign has “Text Tags” that you can use to indicate the spot in the document that you want to place the signature (more info). These text tags are just text and they look like: [sig|req|signer1]
https://support.webmerge.me/hc/en-us/articles/207666676-HelloSign
OneSpan Signature
This signature tag is: {{esl:signer1:signature}}
https://support.webmerge.me/hc/en-us/articles/115001852486-OneSpan-Sign-formerly-eSignLive-
RightSignature
RightSignature uses “Text Tags” to allow you to automatically embed the signatures in specific spots within your document. Below is an example Text Tag for the signature of the 1st signer:
[ s:a:r ]
In the above text tag, the “s” stands for signature, the “a” represents the 1st signer (use b for 2nd, c for 3rd, etc), and the “r” is for required (use “o” for optional). The more space you use between the [ ] brackets, the larger the signature will be on the document. For more information, check out https://www.globiflow.com/help/using-rightsignature-text-tags.php
https://support.webmerge.me/hc/en-us/articles/206527036-RightSignature
Signable
Signable Tags are ways of allowing you to add text tags to your document before uploading it to Signable. It will then automatically grab these tags and replace them with the relevant field (signature, date, text or checkbox). For example:
{signature:signer1:Please+Sign+Here}
In your documents, since these tags look like a merge field, you need to use {literal} … {/literal} tags around the Signable tags so our system ignores them, like this:
{literal}{signature:signer1:Please+Sign+Here}{/literal}
Here are the other Signable tags you can use:
{signature:signer1:Please+Sign+Here}
{text:signer1:Your+Name}
{date:signer1:Date+Here}
{check:signer1:Please+Tick}
{upload:signer1:Please+Upload+Files}
For more information, visit the Signable Tags help page.
https://support.webmerge.me/hc/en-us/articles/115005251846-Signable
SignNow
SignNow also has the ability to embed fields and place signature box in specific locations using Field Tags. This is simply text that is in your documents that is detected by SignNow and turned into a field.
For example: {{t:s;r:y;o:”Signer”;}} (documentation below)
If you are using the online document builder or any of the office documents, you will need to wrap the field tags in {literal}{/literal} tags so that the brackets do not interfere with Formstack Documents merge field tags. Any code inside the literal tags is ignored by Formstack Documents.
For example: {literal} {{t:s;r:y;o:”Signer”;}} {/literal}
Here is the full documentation from SignNow, which can also be found at https://help.signnow.com/v1.0/reference
The order in adding the test tags is:
| KEY | What does it mean? | Accepted format & values | When fields need this KEY? |
| t | TYPE of the field | s (for signature)i (for initials)t (for text)d (for dropdown) | For every field |
| r | REQUIRED | y (for required)n (for optional) | For every field |
| o | ROLE | “<role name>” | For every field |
| l | LABEL | “<label of this field>” | Only for Text and Drop down fields |
| dd | DROPDOWN | “option1, option2, option2, ….” | Only for Drop down fields |
| f | FILE | “<filename>.pdf” | File attachment |
The full set looks like the following:
{{t:[s/i/t/d];r:[y/n];o:”text”;l:”text”;dd:”text,text,text”;”f:text.pdf”;}}
- To create a field of TYPE signature, with required REQUIREMENT, and ROLE ‘Signer’
{{t:s;r:y;o:”Signer”;}} - To create a Field of TYPE Text, with optional REQUIREMENT, with ROLE ‘Signer’, and with LABEL “notes”:
{{t:t;r:n;o:”Signer”;l:”notes”;}} - To create a Field of TYPE Initial, with optional REQUIREMENT, and ROLE ‘Signer’:
{{t:i;r:n;o:”Signer”;}} - To create a Field of Type Drop down, with required REQUIREMENT, with ROLE ‘Employee’, with LABEL ‘Date’, and with DROPDOWNS ‘2012,2013,2014’:
{{t:d;r:y;o:”Employee”;l:”Date”;dd:”2012,2013,2014″;}}
https://support.webmerge.me/hc/en-us/articles/206527096-SignNow