Electronic Signature Text Tags: Document Field Markers

What are electronic signature text tags?

Electronic signature text tags are specially formatted text markers that a compatible signing system interprets as instructions for creating document fields. A tag can describe a field’s location, type, recipient assignment or supported properties, rather than being information the recipient is supposed to sign as ordinary document text.

A compatible parser converts recognized text markers into signing fields. Syntax and supported directives belong to the selected system, so markers must be checked against its documentation.

What is different from a placeholder or PDF field?

A document-generation placeholder typically inserts content, such as a client’s name. A signing text tag tells a compatible parser to create an interactive field. A structured PDF form field is already a field object in the PDF. These mechanisms can participate in the same workflow, but they are not interchangeable.

Likewise, AI field detection may suggest locations from a rendered page without recognizing an explicit tag. A product’s ability to detect fields does not establish support for another vendor’s text-tag language.

What needs to match?

• Syntax: the provider’s exact marker structure and supported directives.
• Recipient: the field’s assignment must correspond to the intended signer or supported role.
• Rendered layout: conversion, wrapping or editing can affect whether a marker is recognized and where the field appears.

Preview the resulting document and assignments before sending. A tag that looks plausible can remain literal text or create an unintended field if the chosen system interprets it differently.

How do text tags relate to an API?

An electronic-signature API may instead create fields using structured request data. Sign.Plus documents annotations assigned to recipients, including signature, initials, text, date and checkbox fields. Structured annotation data specifies each field directly; text-tag parsing is a separate method of creating fields.

Whether the request is prepared manually or through an AI-enabled integration, the resulting fields still need review. Tags prepare fields; they do not establish a recipient’s identity, signing intention or legal authority.