Add Text Tags to the Document with SignNow

Format your text in a document by adding text tags. Specify the type, location and size of your fields. Add tags before uploading a document to airSlate SignNow.

Award-winning eSignature solution

What adding text tags to the document means

Adding text tags to the document is a method of embedding machine-readable placeholders directly into a document that instruct an eSignature platform where to place fields, what data to collect, and how to validate input. Text tags use a compact syntax so senders can prepare documents without a visual editor, enabling automated field placement, conditional logic, and consistent templates. This approach supports repeatable workflows for contracts, forms, and intake documents while preserving the underlying PDF or text layout for accurate rendering across devices and platforms.

Why embed text tags in documents

Embedding text tags reduces manual form editing, enforces consistent field placement, and accelerates document preparation for recurring processes while maintaining accuracy and auditability across signing sessions.

Why embed text tags in documents

Common challenges when using text tags

  • Incorrect tag syntax can cause fields to miss render or appear in wrong positions, requiring manual fixes.
  • Legacy documents with complex layouts may need reflow or manual tag placement to avoid overlapping content.
  • Absent or inconsistent naming conventions for tags lead to data mapping errors in downstream systems.
  • Insufficient validation rules on tags increase the risk of incomplete or incorrectly formatted submissions.

Representative user roles

Contract Manager

A Contract Manager uses text tags to create reusable agreement templates, enforce required fields such as effective date and signature blocks, and coordinate approval routing. They rely on tag conventions to ensure accurate data extraction for contract analytics and to minimize legal review time.

HR Administrator

An HR Administrator embeds text tags in onboarding and benefits forms to capture employee data, apply input validation for SSNs or tax IDs, and ensure consistent field placement so documents render correctly across desktop and mobile signers.

Who typically uses add text tags to the document

Legal, HR, sales operations, and administrative teams commonly embed text tags to standardize forms and speed routing.

  • Legal teams preparing recurring contract templates that must preserve clause placement and signature sequencing.
  • Human resources departments automating onboarding packets and benefits enrollment with consistent data fields.
  • Sales operations generating quotes and order forms that integrate with CRM systems and require precise field mapping.

Teams benefit from fewer manual edits and clearer audit trails when tags are applied consistently across templates.

Core capabilities supporting add text tags to the document

A robust text-tag workflow includes field types, conditional logic, validation, and template management to support enterprise use cases.

Field types

Support for text, date, checkbox, radio, dropdown, and signature fields to mirror form needs and capture structured data consistently from signers.

Conditional tags

Display logic that shows or hides fields based on prior inputs, reducing signer confusion and ensuring only relevant information is requested.

Validation rules

Built-in validators for formats such as dates, emails, phone numbers, and custom regex to ensure collected values meet required patterns.

Repeating sections

Ability to define repeatable tag groups for line items or multi-entry sections so templates accommodate variable-length data cleanly.

Template library

Centralized storage of tagged templates with version control, access permissions, and standard naming for consistent organization across teams.

Preview and testing

Preview mode that renders tags as interactive fields prior to sending, allowing validation of placement and logic with test signers.

be ready to get more

Choose a better solution

Integrations and tag interoperability

Text tags work best when integrated with document editors, storage, and business systems to keep data flowing without manual steps.

Google Docs

Convert templates from Google Docs by exporting to DOCX or PDF and applying tag syntax so document layout and collaborative editing stay intact before finalizing tags.

CRM systems

Map tag-named fields directly to CRM object fields to populate records automatically after signing and reduce duplicate data entry across sales or account teams.

Cloud storage

Store tag-enabled templates in Dropbox or Google Drive to maintain version control and allow non-technical users to update base content without touching tag logic.

Accounting tools

Export tagged form data to invoicing or ERP systems to trigger billing workflows after signature completion, reducing manual processing time.

How tag parsing and placement works

Understanding the parsing process helps troubleshoot layout issues and ensure consistent field mapping across documents.

  • Tag detection: Parser scans document for recognized tag patterns and token names.
  • Field rendering: Platform converts tags into interactive form fields at the same coordinates.
  • Validation rules: Tags can include input constraints and required flags enforced at signing.
  • Data mapping: Collected values map to named fields for exports or integrations.
Collect signatures
24x
faster
Reduce costs by
$30
per document
Save up to
40h
per employee / month

Quick step-by-step: Add text tags to the document

Follow these core steps to convert a form or agreement into a tag-enabled document ready for automated sending and signing.

  • 01
    Prepare document: Open the source PDF or DOCX and identify field locations.
  • 02
    Insert tags: Place tag syntax at each desired field position.
  • 03
    Validate tags: Verify tag syntax and preview field positions.
  • 04
    Save template: Store as a reusable template for future sends.

Audit trail and recordkeeping steps for tagged documents

Maintain clear audit records for legal and compliance review when using tags to collect signer input and approvals.

01

Record creation:

Log template and tag author details
02

Signer events:

Capture timestamps for each action
03

Field changes:

Track edits and value history
04

Versioning:

Keep template versions archived
05

Export logs:

Provide CSV or PDF audit exports
06

Retention policies:

Apply legal hold where required
be ready to get more

Why choose airSlate SignNow

  • Free 7-day trial. Choose the plan you need and try it risk-free.
  • Honest pricing for full-featured plans. airSlate SignNow offers subscription plans with no overages or hidden fees at renewal.
  • Enterprise-grade security. airSlate SignNow helps you comply with global security standards.
illustrations signature

Typical workflow settings for tag-enabled sending

Configure these workflow settings to ensure tag parsing, notifications, and data routing behave as expected for tagged documents.

Setting Name Configuration
Tag Syntax Standard Bracketed tokens
Reminder Frequency 48 hours
Field Validation Mode Strict
Template Access Role restricted
Data Export Format CSV or JSON

Supported devices and platform notes

Tag parsing and field rendering generally work across desktop, tablet, and modern mobile browsers, but device-specific testing is recommended.

  • Desktop: Full editor support
  • Mobile browsers: Field rendering only
  • signNow apps: Native support available

Verify templates on the actual target devices used by signers; small layout shifts can affect field alignment, and native apps may offer improved rendering for complex tagged documents.

Security and authentication elements for text-tagged documents

Document encryption: TLS in transit
At-rest protection: AES-256 encryption
User authentication: Password or 2FA
Access controls: Role-based limits
Audit logging: Detailed event records
Data minimization: Field-level restrictions

Industry examples of text tag use

Representative cases show how text tags streamline routine document flows across regulated and fast-moving environments.

Healthcare intake forms

A medical group embeds text tags in patient intake PDFs to capture demographic and insurance details in predefined fields

  • Tag-based validation ensures date and ID formats are enforced at signing
  • Data maps automatically to the EHR to reduce manual entry and transcription errors

Leading to reduced intake time and fewer billing discrepancies.

Sales order processing

A B2B seller uses text tags in quotes and order forms to place price, quantity, and signature fields precisely

  • Conditional tags show tax or shipping only when applicable
  • Integrated field mapping pushes order details to CRM and invoicing systems

Ensures faster order fulfillment and cleaner downstream revenue recognition.

Best practices for accurate tag implementation

Adopt clear conventions and testing routines to reduce errors and improve maintainability of tag-enabled documents across teams.

Establish tag naming conventions and documentation
Define and document consistent tag names, namespaces, and allowed characters so integrations and data exports map predictably and reduce mapping errors.
Keep tag syntax simple and modular
Prefer short, descriptive names and avoid embedding complex logic directly in tags; use external workflow rules when available to maintain readability.
Preview templates on multiple devices
Test rendering on desktop, tablet, and mobile to identify layout shifts or overlapping fields, especially for responsive or complex page designs.
Version templates and restrict edits
Use template versioning and role-based permissions so only authorized users can change tags, preserving consistency and auditability.

FAQs and troubleshooting for tag implementation

Common questions address parsing errors, incorrect placements, and integration mapping issues; answers focus on diagnostics and configuration steps to resolve problems.

Feature availability comparison for tagged documents

A concise feature matrix comparing text tag support and related capabilities across leading eSignature vendors, with signNow listed first as Recommended.

Feature / Criteria signNow (Recommended) DocuSign Adobe Sign
Add Text Tags Support Yes, native parser Yes, limited helper tools Yes, manual placement
Template Library Built-in templates Template folders Template management
Bulk Send Bulk Send supported Bulk Send supported Bulk Send supported
Mobile Tagging Yes, mobile-friendly Partial support Limited mobile features
be ready to get more

Get legally-binding signatures now!

Document retention and legal timelines

Retention schedules and access windows should reflect regulatory needs and institutional policies for signed records and underlying source documents.

Retention for contracts:

Seven years recommended for business contracts

Healthcare records:

Follow HIPAA and state rules

Education records:

Comply with FERPA retention guidance

Tax and payroll:

Maintain according to IRS schedules

Audit logs:

Preserve for minimum compliance period

Regulatory and operational risks

Noncompliant records: Retention gaps
Invalid signatures: Weak authentication
Data exposure: Unencrypted exports
Audit failures: Missing logs
Integration errors: Mapping mismatch
Operational delays: Manual rework

Pricing snapshot for tag-enabled workflows

Overview of common plan characteristics relevant to teams that rely on text-tag workflows; signNow is listed first and labeled Recommended.

Plan Feature signNow (Recommended) DocuSign Adobe Sign HelloSign PandaDoc
Free tier availability Free plan available with basic features and limited sends per month suitable for small teams. Free trial available for limited time with full features. No ongoing free tier; trial only and paid plans required. Free tier with limited monthly documents and branding restrictions. Free trial followed by paid subscription for full feature access.
Entry-level monthly price Affordable per-user starter price that includes templates, basic tagging, and mobile signing. Mid-range per-user pricing focused on enterprise-grade controls and integrations. Higher entry price aimed at Adobe product ecosystem customers with added cloud services. Competitive starter price for independent professionals and small businesses. Pricing aimed at sales teams with document automation at moderate cost.
Business plan features Includes advanced templates, API access, bulk send, and role-based permissions suitable for teams. Offers advanced workflow and enterprise connectors with strong compliance features. Business plans integrate with Creative Cloud and Enterprise ID management. Business tier adds team management and basic API capabilities. Business plan emphasizes document workflows and CRM integrations for sellers.
Enterprise capabilities Enterprise tier provides SSO, advanced security controls, custom branding, and dedicated support. Enterprise includes global compliance, large-scale deployments, and advanced admin controls. Enterprise focuses on large organizations with centralized Adobe identity and rights management. Enterprise offers SSO and enhanced admin features for larger teams. Enterprise supports custom workflows, SSO, and admin tooling for scale.
Notes on tag support Native text tag parser plus documentation and testing tools for reliable template creation. Tag-like templates supported via APIs and template tools; requires additional configuration. Field placement primarily via visual editor with template APIs available. Simple tag support through templates and basic editors; fewer advanced validators. Strong document automation features with visual editors and tag mapping capabilities.

How to use text tags in documents

Text tags in airSlate SignNow are specifically formatted combinations of symbols that can be placed anywhere within your documents in order to preset the location, size and type of various fields such as Signature, Text, Initial fields etc.

1. To use text tags, you must add them to your document before uploading.

For example, the text tags being used for the ‘Date’ line are the following:

{t (for the Type of field): t (for Text): r (for Required): y (for Yes): o (for Role): “Customer”; l (for Label): “Date”; }

The text tags being used on first the ‘Sign Here’ line are the following:

{ t (for Type of field): s (for Signature); r (for Required): y (for Yes); o (for Role): “Customer”;}

The text tags being used on the second ‘Sign Here’ line are the following:

{ t (for Type of field): s (for Signature); r (for Required): y (for Yes); o (for Role): “Agent”; }

After placing text tags in your document and uploading it to airSlate SignNow, the document fields will show up automatically:

The table below shows the most widely used text tags in airSlate SignNow along with the types of fields for which these text tags can be applied.

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)

c (for checkboxes) 

For every field
r REQUIRED

y (for required)

n (for optional)

For every field
o ROLE " " For every field
l LABEL " Only for Text and Drop down fields
dd DROPDOWN "option1, option2, option2, ...." Only for Drop down fields
f FILE " ".pdf" File attachment
w WIDTH w (width) For every field
h HEIGHT h (height) For every field
v VALIDATOR_ID v (validator_id) Only for Text field

You can preset standard fields, such as Initials, and also more complex fields with data validations, such as a US phone number.

1 To create a  field of TYPE signature, with required REQUIREMENT, ROLE 'CEO', WIDTH '100', and HEIGHT '15' {{t:s;r:y;o:"CEO";w:100;h:15;}} 
2 To create a  field of TYPE initials, with optional REQUIREMENT, ROLE 'CEO', and WIDTH '50' {{t:i;r:n;o:"CEO";w:50;}}
3 To create a  field of TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', and HEIGHT '75'

{{t:t;r:n;o:"CEO";l:"Label";h:75;}}

4 To validate a date for TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', WIDTH '100', and VALIDATOR_ID '13435fa6c2a17f83177fcbb5c4a9376ce85befeb'

Date: {{t:t;r:n;o:"CEO";l:"Label";w:100;v:"13435fa6c2a17f83177fcbb5c4a9376ce85befeb";}}

5 To validate a US phone number for TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', WIDTH '100', and VALIDATOR_ID '13cc1d661da456d27b249b73056ed4d1f2e72d8e' {{t:t;r:n;o:"CEO";l:"Label";w:100;v:"13cc1d661da456d27b249b73056ed4d1f2e72d8e";}}
6 To validate a US zip code for TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', WIDTH '100', and VALIDATOR_ID '1671f4eb87444a24e1e00f149bade8b7cf3af5da' {{t:t;r:n;o:"CEO";l:"Label";w:100;v:"1671f4eb87444a24e1e00f149bade8b7cf3af5da";}}
7 To validate an age for TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', WIDTH '100', and VALIDATOR_ID '1a203fa91791b0458608be045a454ba90557fb26'

{{t:t;r:n;o:"CEO";l:"Label";w:100;v:"1a203fa91791b0458608be045a454ba90557fb26";}}

8 To validate an email address for TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', WIDTH '100', and VALIDATOR_ID '7cd795fd64ce63b670b52b2e83457d59ac796a39'

{{t:t;r:n;o:"CEO";l:"Label";w:100;v:“7cd795fd64ce63b670b52b2e83457d59ac796a39”;}}

9 To validate a US state for TYPE text, with optional REQUIREMENT, ROLE 'CEO', LABEL 'Label', WIDTH '100', and VALIDATOR_ID '3123849de563f9e14acacc2739467e3d30e426b6'

{{t:t;r:n;o:"CEO";l:"Label";w:100;v:“3123849de563f9e14acacc2739467e3d30e426b6”;}}

10

To create a  field of TYPE signature, with required REQUIREMENT, and ROLE 'CFO'

{{t:s;r:y;o:"CFO";}}
11

To create a Field of TYPE Text, with optional REQUIREMENT, with ROLE 'CFO', and with LABEL "notes"

{{t:t;r:n;o:"CFO";l:"notes";}}
12

To create a Field of TYPE Initial, with optional REQUIREMENT, and ROLE 'CFO'

{{t:i;r:n;o:"CFO";}}
13 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:"Year";dd:"2012,2013,2014";}}
14

To create a Field of TYPE Text, with a Date label which will auto-fill with current date

{{t:t;r:y;o:"CFO";l:"Date";}}
15

To create an Invite tag with signing order, with required REQUIREMENT, with ROLE 'Role1', 'Client', 'Manager':

{{t:e;o:"Role1";e:"siri@mailinator.com";order:1;}}
{{t:e;o:"Client";e:"siri2@mailinator.com";order:2;}}
{{t:e;o:"Manager";e:"siri3@mailinator.com";order:3;}}

There can also be more complex tags which consist of a tag_name and the airSlate SignNow field creation information as presented in the call PUT /document/.

These complex tags appear in the format {{}} such as {{my signature}} or {{ClientSignatureDate}}.

Here are some of the most popular examples of such complex tags:

Text Tag

      {

tag_name:'TextTagExample',
role:'Role1',
label:'Label1',
required:true,
type:'text',
prefilled_text:’family-name',
width:100,
height:20

},

Date Validator Tag

    {

"tag_name":"DateValidatorTagExample",
"role":"Role1",
"label":"Date of Birth",
"required":true,
" type":"text",
"height":15,
"width":100,
"validator_id":"13435fa6c2a17f83177fcbb5c4a9376ce85befeb"

},

Initials Tag

    {

"tag_name":"InitialsTagExample",
"role":"CLIENT",
"required":true,
"type":"initials",
"height":15,
"width":40

},

Signature Tag

    {

"tag_name":"SignatureTagExample",
"role":"CLIENT",
"required":true,
"type":"signature",
"height":15,
"width":200

},

Drop-Down Tag

    {

"tag_name":"DropDownTagExample",
"role":"Role1",
"label":"Options",
"required":true,
"type":"enumeration",
"height":15,
"width":100,
"custom_defined_option":false,
"enumeration_options":["All","None"]

},

Attachment Tag

    {

tag_name:'AttachmentTagExample',
role:'Role2',
label:'Label2',
required:true,
type:'attachment',
width:100,
height:20

}

Checkbox Tag

{
"tag_name":"CheckboxTagExample",
"role":"CLIENT",
"required":true,
"type":"checkbox",
"height":12,
"width":12,
},

To begin, you can simply copy-paste the needed tag from the table below and add it your document prior to uploading it to airSlate SignNow. Height and width are easily adjusted manually, just change the numbers as per your needs.

walmart logo
exonMobil logo
apple logo
comcast logo
facebook logo
FedEx logo
be ready to get more

Get legally-binding signatures now!