> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Anchor tagging tips and tricks

The following are tips for effective use of Anchor-based tagging:

* In order to avoid unintentional conflicts between AnchorTabStrings and the text that naturally exists in documents, establish a codified syntax for AnchorTabStrings that is unlikely to otherwise appear in a document.
* Develop an extensible and consistent syntax that can be used across multiple document types. i.e. \[RecipientIdentifier.TabType.TabQualifier]. Examples of this syntax might include \[R1.InitialHere] or \[CoSign1.Custom.SSN].
* Especially for documents that have variable numbers of tabs or signers (ex: optional Co-signers), author the source document to include hidden anchor tabs for all potential signers/permutations. Then, control the tabs that are actually placed by including/excluding the Anchors in the XML request. This approach allows a single document to be used for all use cases instead of maintaining separate documents for each scenario.