A token is written between double braces, for example {{firstName}}, {{email}}, or {{org_address_route}}.

Fields that depend on the contact (name, email, phone, custom fields fields.* / properties.*) are filled per contact row.

The sender-side groups are always resolved and never count as "missing data": user.* (sender identity), company.* (company / brand), campaign.*, as well as the computed values qr.*, shortUrl, and today.

A token that finds no value for a contact is rendered as an empty string in the PDF. The contact list flags these missing fields for the tokens it can evaluate client-side (base fields and known custom keys); the full check is done server-side at export time.

Resolution accepts a short form: if {{myfield}} does not resolve directly, QR Queen tries fields.myfield, which lets short tags work.

Tokens can also be inserted as blocks (merge-token) from the editor, not just typed in plain text.