> 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 based tagging

This section outlines the usage rules and behaviors of the Docusign Anchor-Based Tagging feature. Anchor-Based Tagging enables a Docusign customer to send documents for signature that do not have a fixed layout or format. In these documents, you can not anticipate the absolute location of the tabs when you design your API client application because the tabs must move with text. As an alternative to sending X and Y coordinates for tabs, the Docusign Signing Service derives anchor tab locations by correlating XML instructions from the SOAP request to data within the document.

* [Using Anchor Tags](/docs/esign-soap-api/esign101/anchor-tagging/using-anchor-tags)

* [Rules for Anchor Tagging](/docs/esign-soap-api/esign101/anchor-tagging/rules)
  * [Anchor Tagging Tips and Tricks](/docs/esign-soap-api/esign101/anchor-tagging/tips-tricks)

## Docs

- [Using anchor tags](https://developers.docusign.com/docs/esign-soap-api/esign101/anchor-tagging/using-anchor-tags.md)
- [Rules for Anchor tagging](https://developers.docusign.com/docs/esign-soap-api/esign101/anchor-tagging/rules.md)
- [Anchor tagging tips and tricks](https://developers.docusign.com/docs/esign-soap-api/esign101/anchor-tagging/tips-tricks.md)