Approved Email Configuration Tokens
Approved Email tokens are used for personalization by customers and for limited personalization by users. Personalization values are pulled from the account__v and user__sys objects and allow emails to contain personalized content. Configuration tokens enable specific behavior prior to an email being sent.
Do not include tokens in commented out sections of Approved Email content.
All tokens are case sensitive.
Who can use this feature?
- Browser, iPad, iPhone Users
- Users require an Approved Email license
- Content Creation Users
Approved Email Tokens fall into one of the following categories:
- Inserting Email Fragments and Template Fragments
- Content Tokens
- Standard Tokens
- Object Reference Tokens
- Sent Email Related Tokens
- Functionality Tokens
- Vault Tokens
- User Input Tokens
- Text Tokens
- Picklist Tokens
- Signature Transaction Receipt Tokens
Tokens that can be used in Email Fragments can also be used in Master Email Fragments.
Tokens in Email Fragments and Template Fragments are not supported on the Windows Tablet platform.
Do not use multiple lines when adding tokens to the Subject Field.
Do not use Approved Email tokens in unsupported entry points or content types. This may result in unexpected behavior.

Inserting Email Fragments and Template Fragments
Description |
Supported Entry Points |
Works In |
|
---|---|---|---|
{{insertEmailFragments}} |
Defines where fragments are inserted in templates. This token must be inserted in an empty <table> tag in the Email Template. Do not insert multiple {{insertEmailFragments}} tokens into the same Email Template. See Creating Approved Email Templates for more information about template requirements. |
All except Receipts and Double Opt In |
Email Templates |
{{insertEmailFragments[Minimum,Maximum]}} |
Defines the minimum and maximum number of fragments end users can add to a template. For example, {{insertEmailFragments[2,4]}} requires end users to select between two and four fragments to add to the email. Do not insert multiple {{insertEmailFragments[Minimum,Maximum]}} tokens into the same Email Template. |
All except Receipts and Double Opt In |
Email Templates |
{{emailTemplateFragment}} |
Inserts an HTML snippet that is managed by the Vault Email Template Fragment document type. Typically used to append a standard disclaimer or ISI to the end of the selected template. |
All |
Email Templates |

Content Tokens
Content tokens are tokens that add specific content or add links to related content.
Content that includes tokens with reference to API Names must be set with the appropriate content target platform. See Setting the Target Platform for Approved Email Content for more information.
Select tokens with blue names to play an instructional video on the token.
Tokens in Email Fragment URLs are not accessible in Preview mod
Standard Tokens
Token |
Description |
Supported Entry Points |
Works In |
---|---|---|---|
{{accTitle}} |
Inserts Account salutation |
All |
|
{{accFname}} |
Inserts Account first name |
All |
|
{{accLname}} |
Inserts Account last name |
All |
|
{{accCredentials}} |
Inserts Account credentials from Account.Credentials__v |
All |
|
{{userEmailAddress}} |
Inserts the end user's email address from the SenderEmail field on the User object. This token is typically used in the from or reply-to fields of an outbound email template. |
All |
|
{{userName}} |
Inserts the end user’s name. |
All |
|
{{userPhoto}} |
Photo of user stored in the user_detail__v object. Photos display at their native size, except for in the My Profile tab, where it displays in 160x120 pixels. |
All |
|
{{parentCallDatetime}} |
Inserts the date and time of the associated Parent Call, ensuring this information is correct when the email is sent. This token does not include the timezone. Use the {{timeZone}} token to insert the timezone. When an email template has the token {{parentCallDatetime}}, it will be replaced by the:
|
|
|
{{parentCallDatetime(FORMAT)}} |
Creators can additionally specify the displayed format of the date or time. See Formatting Tokens to Display Date and Time for more information. |
|
|
{{timeZone}} |
For iPad end users, this token displays the value of the time zone of the device. The format is based on the user’s locale. For Online end users, this token displays the value of the TimeZoneSidKey field on the User record and displays with the format: GMT +/- X hours. |
All |
|
Object Reference Tokens
Token |
Description |
Supported Entry Points |
Works In |
---|---|---|---|
Content creators can use this token to directly reference any field of a supported field type on the following objects:
The following field types are supported:
Examples:
|
All |
|
|
Enables referencing fields from lookup objects. See above for the list of supported objects and field types. This token is not supported for lookups on standard fields. Examples: {{call2__v.remote_meeting__vr.host_link__v}} {{account__v.custom_reference_field__cr.custom_field__c}} |
All |
|
|
{{customContent}} |
Inserts data from a defined custom query. See Inserting Queried Data into an Approved Email for more information. This token is not supported on the Windows Tablet platform. |
All |
|
Sent Email Related tokens
Token |
Description |
Supported Entry Points |
Works In |
---|---|---|---|
{{EmailAddressUnsub}} |
Inserts the sent email address in a URL. The links are not available in Preview mode. This token can not be inserted in the body of the email. |
All |
|
{{EmailId}} |
Inserts the ID of the sent_email__v record. This token is not supported in Edit and Preview mode. |
All |
|
{{OrgId}} |
Inserts the ID of the Vault CRM environment from which the email was sent. |
All |
|
{{AppDocId}} |
To track email activity of which content is accessed most frequently, content creators may add this token to expand to the 18 digit Id of the Approved Document record the token resides in. Example: <a href = "https://www.veeva.com/?{{AppDocId}}"> Click Here. </a> The expanded URL will be: https://www.veeva.com/?AppDocId=a1sJ0000003u458ADS See Tracking Email Activity at the Email Fragment Level for more information. |
n/a |
|

Functionality Tokens
Description |
Supported Entry Points | Works In | |
---|---|---|---|
{{approvedEmailAction}} |
Creates a link in the email that, when selected, tracks as a standard click event. An email activity record is created in Vault CRM, and a Multichannel Activity record is created with the appropriate object type. See Tracking Multichannel Activities from Approved Emails for more information. |
All |
|

Vault Tokens
Description |
Supported Entry Points | Works In | |
---|---|---|---|
{{$VaultDocID}} |
Expands to a URL pointing to a Vault PromoMats document with the corresponding VaultDocID. When using this token, replace VaultDocID with the ID of the appropriate document in Vault. The document ID is visible in the URL when viewing a Vault document. The integer to the right of #doc_info is always the unique Vault document ID. For example, {{$20}} points to Vault document ID 20. Example: https://customer.veevavault.com/ui/#doc_info/20/3/0 The document referenced by the token should be added to the Approved Document's Other Related Documents relationship in Vault. |
All |
|
{{ISILink}} |
Expands to a URL pointing to a Vault document of type Important Safety Information. |
All |
|
{{PieceLink}} |
Displays a URL to the Vault document associated as the Related Piece. |
All |
|
{{PILink}} |
Displays a URL to a Prescribing Information Vault document. |
All |
|

User Input Tokens
Text Tokens
All user input text is stamped on the user_input_text__v field on the corresponding sent_email__v record.
Zero-width non-joiner tokens (‌) should not be used in User Input Tokens (Text and Picklist Tokens).
Token |
Description |
Supported Entry Points |
Works In |
---|---|---|---|
{{customText}} |
Creates a blank text area in the email where the end user can enter free text. All entered text is evaluated against any defined restricted words or phrases. |
All except Receipts and Double Opt In |
|
{{customText(Length)}} |
Sets a maximum length for the entered free text. For example, {{customText(255)}} adds a text input area that can accept up to 255 characters. |
All except Receipts and Double Opt In |
|
{{customText(Length|DefaultText)}} |
Enables default text that displays when the text input area initially renders to the end user. The end user can then choose to replace the default text with their own. The DefaultText parameter can be used with the Length, or can be used independently using {{customText(|DefaultText)}}. Square brackets are not supported within default text for the custom free text token. |
All except Receipts and Double Opt In |
|
{{customText:Required}} |
Marks the free text field as required, ensuring end users do not exclude critical information in an email. |
All except Receipts and Double Opt In |
Email Templates |
{{customRichText}} |
Enables end users to add more versatile free text to an email through displaying a rich text area. Rich text enables end users to do the following:
The default size of the text area is 400 x 300 pixels. Do not enclose this token in <br> or <p> tags. It should only be enclosed by tags that are designed to have a closing tag, for example, <span> or <td> tags. This is because the rich text editor includes its own <p> tags, so enclosing the token in these tags causes styles to be lost. Images are not supported in the Rich Text editor. Entered text in a custom rich text field is checked against all defined Restricted Words and Phrases. |
All except Receipts and Double Opt In |
Email Templates |
Picklist Tokens
All configured picklist options are stamped on the email_config_values__v field of the corresponding sent_email__v record.
Zero-width non-joiner tokens (‌) should not be used in User Input Tokens (Text and Picklist Tokens).
Token |
Description |
Supported Entry Points |
Works In |
---|---|---|---|
{{customText[options]}} |
Adds a picklist field. All values are defined by the content creator, assuring that entries remain compliant while also granting a degree of personalization to the end user. Picklists can also be made with blank values by entering a picklist value of one space character. Do not use the |, ", or quot; characters in picklist values. The width of the picklist can be controlled by including CSS styling in the template's <style> tag for the CSS selector style.hideCustomTextValues. HTML tags inside this token are not supported. Example: {{customText[Hello|Dear|Hi]}} renders to the end user as a picklist with the following values:
The below two tokens will display blank value options in the picklist the end user sees:
Do not include line breaks or new lines in picklist values. |
All except Receipts and Double Opt In |
|
{{customText[##ContentToken1##|##ContentToken2##]}} |
Content Tokens can be used as values of this picklist by replacing the { and } characters of the content token with #. Do not use the |, ", or quot; characters in picklist values. Tokens from the following objects are supported:
Referenced fields display by their labels in the email rather than their values, though the values of these fields populate when the email is sent. HTML tags inside this token are not supported. Example: Sarah Jones composes an email to Dr. Clinton Ackerman with the following custom text token: {{customText[##accTitle## ##accFname## ##accLname##, ##accCredentials##|##accTitle## ##accLname##|##accFname##]}} In Edit mode, this token renders to Sarah as a picklist with the following options:
In Preview mode, this token renders to Sarah as the actual values of the selected option. Do not include line breaks or new lines in picklist values. |
All except Receipts and Double Opt In |
|
{{customText[##ContentToken1##|##ContentToken2(FORMAT)##]}} |
If the referenced field is a Date or a Date/Time type field, creators can additionally specify the displayed format of the date or time. See Formatting Tokens to Display Date and Time for more information. |
All except Receipts and Double Opt In |
Email Templates |

Signature Transaction Receipt Tokens
See Creating Approved Email Receipt Templates for Signature Transactions for more information.
Token |
Description |
Supported Entry Points |
Works In |
---|---|---|---|
{{insertCallSample[Column1,Column2]}} |
If call sample records exist, a table is rendered displaying all call samples associated with the call as rows. Columns can be defined as parameters of the token. For example: {{insertCallSample[product__v.name__v,quantity__v]}} |
Receipts |
Email Templates |
{{insertCallSample[Column1,Column2(FORMAT)]}} |
If the referenced field is a Date or a Date/Time type field, creators can additionally specify the displayed format of the date or time. See Formatting Tokens to Display Date and Time for more information. |
Receipts |
Email Templates |
{{insertCallSample[filterProductType=TYPE,Column1,Column2]}}}} |
The filterProductType parameter on the {{insertCallSample}} filters all call samples on the call and only adds a row for each call sample of the specified product type. For example, the following renders two separate tables, one that only contains Samples, the other that only contains Educational Materials. Each table has different columns. {{insertCallSample[filterProductType=Sample,quantity__v,product__v.name__v,product__v.manufacturer__v]}} </br> {{insertCallSample[filterProductType=Educational Material,quantity__v,product__v.name__v]}} |
Receipts |
Email Templates |
{{insertSignature}} |
Inserts a photo copy of the signature. |
Receipts |
Email Templates |

Website Tokens
Description |
Supported Entry Points |
Works In |
|
---|---|---|---|
Tracks the following data about a web link shared with an HCP when appended to the link URL:
Example: https://www.verteobiopharma.com?{{linkTracker}} The tokens resolve to the following: https://verteobiopharma.com?src=VeevaCRM&dvc=iPad&sentDateTime=2021-08-25T20:05:28Z See Adding Tracking Tokens to Website URLs for more information about tracking websites. |
n/a |
Website URLS |
|
Inserts the Mobile Id of the sent_message__v record when the website is sent from the mobile device. |
n/a |
Website URLS |