VDP (Variable Data Printing)

VDP combines a reusable design with records that change text, image references or code values. The public legacy canvas and VDP Bulk product surface are currently disabled. Remaining parsers, mapping models and protected batch-generation code do not establish a current VDP tab or an unlimited production service.

Academy: The Power of Personalization

Names, addresses and record identifiers can vary while common artwork stays the same. Personalization can be useful, but response rate, conversion, ROI and cost depend on the campaign and production workflow. No measured 2%/15% uplift or guaranteed lower cost is claimed here.

How does it work?

This is a conceptual flow, not proof that thousands of PDFs can be generated in the current public interface.

Guides in this section

Dynamic Field Mapping: Live Simulation

The teaching example is to map FirstName to a text object and TicketID to a code value. A simulated mapping being marked complete does not upload CSV, invoke a renderer, validate a code or generate PDFs. The retained Turkish demo uses fixed example labels; its illustrative “10,000 PDFs” text is not an active limit or product capability.

Use Cases and Data Structures

Event badges

FirstName,Company,TicketID
Alex,Example Ltd,T9823
Sam,Sample Studio,T9824

Check long names, company details and the actual ticket-validation system. Different rows do not automatically guarantee unique or valid entry tokens.

Product labels

Use product identifiers, display price and code values as explicit strings. Preserve leading zeros; validate any retail-code/check-digit requirements with the target system.

Targeted marketing

A record may supply an offer or coupon value. Use an authorized data source, review recipient/offer matching and keep unnecessary personal information out of the dataset.

Quick Start

For an explicitly authorized compatible legacy workflow:

1. Keep the source master and agree which object properties may vary.
2. Prepare a small UTF-8 CSV and validate headers, rows and required values.
3. Configure mappings explicitly, including missing-value/conditional behavior.
4. Check representative long, empty, special-character and code records.
5. Confirm the selected renderer supports every object and the bounded batch size.
6. Inspect output before any proof, sharing or print handoff.

There is no current public Enable VDP → Download All procedure. A remaining protected endpoint has its own admission limits and authorization; it does not enable the public editor.

Knowledge Check

VDP means Variable Data Printing. Changing record content is separate from changing paper or machine setup. Template metadata, an example mapping or a PDF file header does not prove correct rendered content or production readiness.

Tips and Best Practices

Data preparation

Use explicit header names, string identifiers and resolved values. Keep genuinely missing values distinguishable from real text such as N/A. Do not automatically replace missing names with invented content.

Design tips

Check longest text, line breaks, required glyphs, images and every code value. Auto-fit and automatic missing-font repair are not established guarantees.

Performance

Do not use the old 10,000/50,000-record or processing-time claims. The protected batch API is capped at 500 rows and a 5 MiB JSON body, with a 50 MiB result budget; the fallback has additional object/page restrictions. See Batch Export.

Keep the original data and output association. A batch result does not bypass the order's payment, file, proof or production-release requirements.