Watermark tokens let XERIA turn one watermark design into recipient-specific output. Instead of typing a different name into the watermark for every recipient, you can place a supported token such as {NAME} in the watermark text and let XERIA resolve that token from the selected recipient record during personalized generation.
This is especially useful in batch workflows because the watermark design stays consistent while the recipient value changes automatically from one generated PDF to the next. Tokens reduce repetitive editing, but they also make recipient-data quality more important: if the selected list contains an incorrect name or other mapped value, that mistake can be reproduced across the personalized output.
The Short Answer
Create or select the recipient list you want to use, open the watermark text settings in the personalized workflow, insert the supported token you need—such as {NAME}—and combine it with any fixed text you want. XERIA resolves the token separately for each recipient when it generates the personalized PDFs.
A token is a placeholder, not the final visible text. For example, a watermark design such as “Confidential — {NAME}” keeps the word “Confidential” fixed while replacing {NAME} with the name stored in the active recipient record.
What a Watermark Token Does
A watermark token links the watermark text to recipient data. The watermark template is created once, while the value inserted at generation time comes from the recipient record selected for that copy. This allows the same PDF and the same watermark layout to produce many visually distinct recipient-specific files.
Tokens are therefore most useful in personalized batch mode, where each output PDF is associated with a recipient. They are different from manually typing a fixed watermark because the final text is resolved during processing rather than being identical on every generated copy.
1. Prepare the Recipient Data First
Before working with tokens, review the recipient list that will supply the data. The recipient name should be accurate, consistent, and appropriate for visible display. Test entries, blank names, duplicate recipients, or values copied from another project can all produce misleading personalized watermarks.
- Select the intended recipient list before production
- Review names and other recipient values used by the workflow
- Remove or exclude test recipients
- Check duplicate or obsolete records
- Keep recipient identity consistent with trace and delivery records
- Use clear recipient-list names so the wrong list is not selected accidentally
2. Insert and Use a Watermark Token
Step 1: Open the Personalized Watermark Workflow
Start from the XERIA workflow where recipient-specific PDF generation is configured. Select the recipient list and the source PDF, then open the watermark text settings that will be applied to the personalized outputs.
Step 2: Insert a Supported Token
Insert a token offered by XERIA. The confirmed example is {NAME}, which represents the recipient name. Keep the token spelling and braces exactly as required by the interface so the placeholder can be recognized correctly during generation.
Step 3: Add Fixed Text Around the Token
A token can be combined with ordinary fixed text. For example, “Prepared for {NAME}” or “Confidential — {NAME}” creates a consistent watermark phrase while still changing the recipient portion for every generated copy.
Step 4: Configure the Watermark Appearance
After defining the text, configure the visual watermark settings you need, such as placement, angle, opacity, color, and related appearance controls. The token changes the text value; it does not replace the visual watermark configuration.
Step 5: Preview or Test Before Production
Run a small test or preview with a few known recipient records before generating the full batch. Confirm that the token resolves to the expected name, the fixed text remains correct, and the final watermark is readable without unnecessarily obscuring the document.
3. Combine Dynamic and Fixed Watermark Text
The most practical token designs mix fixed wording with a dynamic value. A fixed phrase explains the handling requirement while the token associates the copy with a recipient. Examples include “Confidential — {NAME}”, “Prepared for {NAME}”, or “Recipient copy: {NAME}”.
Keep the wording concise. Long recipient names combined with long fixed phrases can create crowded watermarks, especially when tiled or repeated. Test the longest realistic recipient name in your list so that the final design remains readable across the entire batch.
4. Check the Resolved Watermark Before a Large Batch
A valid token can still produce an undesirable result if the underlying recipient data is wrong or the visual design does not fit long values. Use a test set that includes short and long names, non-English characters when relevant, and any edge cases you expect in production.
- Confirm that {NAME} is replaced rather than printed literally
- Check that long names fit the selected watermark layout
- Review opacity and contrast against light and dark page areas
- Check the result at the intended angle and position
- Verify that repeated or tiled watermarks remain readable
- Confirm that the correct recipient list supplied the values
5. Use Tokens in Personalized Batch Generation
Tokens become most valuable when one source PDF must be prepared for many recipients. XERIA can use the selected recipient list to generate separate copies while resolving the watermark token for each record. This avoids manually editing the watermark text before every output file.
The recipient list remains the data source, while the watermark design remains the template. If you need to create or reorganize the list first, see [Create and Manage Recipient Lists in XERIA](/resources/articles/create-manage-recipient-lists-in-xeria/). Review the list before every important production run because the token will reflect the data stored there.
6. Watermark Tokens and Trace Information Are Related but Different
A visible recipient token and XERIA's trace-oriented features serve related accountability goals, but they should not be treated as the same mechanism. {NAME} places recipient information visibly in the watermark. Trace codes and optional QR trace information provide additional trace-oriented data that can support later association and analysis.
Do not assume that a trace field automatically corresponds to a watermark token with a particular syntax unless XERIA explicitly exposes that token. Keep visible watermark tokens, trace codes, QR trace information, filenames, and recipient records logically consistent so that later review does not depend on conflicting identities.
Common Token Mistakes to Avoid
Most token problems come from typing, recipient data, or workflow selection rather than from the concept itself. A token can remain unresolved if it is entered incorrectly, or it can resolve to an unexpected value if the wrong recipient list or record is being used.
- Typing an unsupported or invented token name
- Changing the required braces or token spelling
- Using the wrong recipient list for the batch
- Leaving test or blank recipient names in the selected list
- Designing fixed text that becomes too long with real recipient names
- Assuming token output proves who later copied or redistributed the document
Practical Best Practices
Treat the watermark template and the recipient list as two parts of one controlled workflow. Keep the token syntax exactly as supported by XERIA, maintain clean recipient data, test the longest realistic values, and verify a small sample before full production. Use visible recipient marking as an accountability and deterrence measure rather than as a guarantee that redistribution is impossible.
- Use only tokens exposed by the current XERIA interface
- Keep fixed text short and easy to understand
- Test short, long, and non-English recipient names when relevant
- Review the selected recipient list before production
- Keep watermark identity consistent with trace and delivery data
- Do not describe a visible watermark as absolute copy prevention
How Watermark Tokens Fit into XERIA
XERIA uses watermark tokens as part of its recipient-specific PDF preparation workflow. A supported token can pull recipient data into visible watermark text while the rest of the watermark design remains reusable across the batch.
This works alongside XERIA's personalized batch generation, visible watermarking, trace codes, optional QR trace information, password and permission settings, controlled e-mail delivery, cloud-connected outputs, and Mail Log records. These controls address different parts of the distribution workflow and can be combined when appropriate.
Frequently Asked Questions
What does {NAME} do in XERIA?
{NAME} is a confirmed watermark token for the recipient name. During personalized generation, XERIA replaces the token with the name from the relevant recipient record so each generated copy can display its intended recipient.
Can I type any recipient field inside braces and use it as a token?
Do not assume so. Use only token names that XERIA exposes as supported options. A recipient field existing in the database does not automatically mean that a matching watermark token exists with the same name.
Can I combine a token with normal text?
Yes. A token can be placed inside fixed wording such as “Prepared for {NAME}” or “Confidential — {NAME}”. The fixed text remains the same while the token is resolved separately for each recipient.
Does a personalized watermark prevent the recipient from copying the document?
No. A visible personalized watermark can support deterrence, recipient accountability, and later attribution, but an authorized viewer may still take screenshots, photographs, retype content, or redistribute the file. Watermarking should be treated as one layer in the distribution workflow.
Conclusion
Watermark tokens make XERIA's personalized watermarking workflow reusable and scalable. Prepare clean recipient data, insert only supported tokens such as {NAME}, combine them with concise fixed text, test the resolved output, and then run the personalized batch. The result is a consistent watermark design that can automatically produce recipient-specific visible markings across many PDFs.