Supported Merge Tags

Here are the supported merge/text tags per delivery platform

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

https://helpx.adobe.com/sign/using/text-tag.html

https://support.webmerge.me/hc/en-us/articles/206527106-Adobe-Sign-formerly-EchoSign-

DocuSign

https://support.webmerge.me/hc/en-us/articles/206527116-DocuSign

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. Click here for full documentation.

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 looks like: {{esl:signer1:signature}}   

https://support.webmerge.me/hc/en-us/articles/115001852486-OneSpan-Sign-formerly-eSignLive-

https://community.onespan.com/documentation/onespan-sign/guides/feature-guides/developer/text-tag-extraction?origin=developeresignlive

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:

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";}}

1. To create a field of TYPE signature, with required REQUIREMENT, and ROLE 'Signer'
    {{t:s;r:y;o:"Signer";}}
2. 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";}}
3. To create a Field of TYPE Initial, with optional REQUIREMENT, and ROLE 'Signer':
    {{t:i;r:n;o:"Signer";}}
4. 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