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.

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.

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.

Inserts Account salutation

Inserts Account first name

Inserts Account last name

Inserts Account credentials from Account.Credentials_vod

Inserts the end user's email address from the Email field on the User object. 

This token is typically used in the from or reply-to fields of an outbound email template.

Inserts the end user’s name.

Photo of user stored in the User_Detail_vod object.

Photos display at their native size, except for in the My Profile tab, where it displays in 160x120 pixels. To preserve clarity, resize the photo to 160x120 pixels prior to uploading the photo.

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:

• Value stored in the Call2_vod.Call_Datetime_vod, if neither Call2_vod.Parent_Call_vod nor Call2_vod.Parent_Call_Mobile_ID_vod is populated
• Value stored in Call2_vod.Parent_Call_vod__r.Call_Datetime_vod, if Call2_vod.Parent_Call_vod is populated
• Value stored in Call2_vod.Call_Dateime_vod of the Call2_vod record, where the Parent Call2_vod.Mobile_ID_vod = Child Call2_vod.Parent_Call_Mobile_ID_vod

Creators can additionally specify the displayed format of the date or time.

See Formatting Tokens to Display Date and Time for more information.

Content creators can use this token to directly reference any field of a supported field type on the following objects:

• Account

• Approved_Document_vod

  Referencing the Approved_Document_vod object is only supported in Email Templates.

• Call2_vod
• User
• User_Detail_vod

The following field types are supported:

• Check box
• Currency
• Date
• Date/Time
• Email

• Formula*

  Unavailable on the User object

  Formula field values are not updated automatically on iPad, so an email may contain an outdated formula field value if the user changed a value used by the formula field but had not yet synced.

• Number
• Percent
• Phone
• Picklist

• Roll-Up Summary*

  Only available on the Account object

  Roll-up field values are not updated automatically on iPad, so an email may contain an outdated roll-up field value if the user changed a value used by the roll-up field but had not yet synced.

• Text
• Text Area

Examples:

• {{Account.Formatted_Name_vod__c}}
• {{Approved_Document_vod__c.Language_vod__c}}
• {{User.Phone}}

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.

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.

Example:

{{Call2_vod__c.Remote_Meeting_vod__r.Host_Link_vod__c}}

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.

In Events Management, Speaker, content creators may use this token to reference fields from Speaker, Attendee and Team Member objects in an email template, as an attendee can fall under multiple different types.

To avoid creating email templates for each attendee type, this token will choose the first field that returns the value for a given recipient. The order of preference is given to the field that is referenced first in the token.

See Using Approved Email for Events Management for more information.

Example:

{{EM_Attendee_vod__c.Name;;EM_Event_Speaker_vod__c.Name;;EM_Event_Team_Member_vod.Name}}

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.

The field to format must be listed last in the list of tokens.

Inserts data from a defined custom query.

See Inserting Queried Data into an Approved Email for more information.

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.

Inserts the ID of the Sent_Email_vod record.

This token is not supported in Edit and Preview mode.

Inserts the ID of the CRM environment from which the email was sent.

Inserts an .ICS attachment for recipients to add to their calendars.

Creates a link in the email that, when selected, tracks as a standard click event. An email activity record is created in CRM, and a Multichannel Activity record is created with the appropriate record type.

See Tracking Multichannel Activities from Approved Emails for more information.

Creates a table that lists out all of the sessions of a planned event.

See Event Session and Event Speaker Tokens for more information

Line breaks and spaces are not supported in this token.

Creates a table that lists out all of the speakers of a planned event.

See Event Session and Event Speaker Tokens for more information

Line breaks and spaces are not supported in this token.

Used to insert both Engage and Zoom URLs in invitations sent to attendees of an Engage meeting or of a virtual event.

See Joining an Engage Meeting via Zoom and Joining a Virtual Event via Zoom for more information.

This token is not supported for Event Speakers.

Used to insert dial-in numbers in invitations sent to attendees of an Engage meeting or virtual event.

See Adding Dial-in Numbers to Engage Invitations for more information.

This token is not supported for Event Speakers.

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.

Allows end users to send dynamic content to HCPs

Expands to a URL pointing to a Vault document of type Important Safety Information.

Displays a URL to the Vault document associated as the Related Piece.

Displays a URL to a Prescribing Information Vault document.

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.

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.

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.

Marks the free text field as required, ensuring end users do not exclude critical information in an email.

This token is not supported on the Browser platform

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:

• Hello
• Dear
• Hi

The below two tokens will display blank value options in the picklist the end user sees:

• {{customText[option1| |option2]}}
• {{customText[option1|option2| ]}}

Do not include line breaks or new lines in picklist values.

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:

• Account
• User
• User_Detail_vod

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:

• Salutation First Name Last Name, Credentials
• Salutation Last NameFirst Name

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.

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_vod__r.Name,Quantity_vod__c]}}

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.

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_vod__c,Product_vod__r.Name,Product_vod__r.Manufacturer_vod__c]}}

 </br>

{{insertCallSample[filterProductType=Educational Material,Quantity_vod__c,Product_vod__r.Name]}}

If Medical Inquiries exist associated with the email, a table is rendered displaying all Medical Inquiries as rows. Columns can be defined as parameters of the token.

For example:

{{insertMedicalInquiry[Delivery_Method_vod__c,Product__c,Inquiry_Text__c]}}

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.

If Order Lines exist associated with the email, a table is rendered displaying all Order Lines as rows. Columns can be defined as parameters of the token.

For example:

{{insertOrderLine[Quantity_vod__c,Product_vod__r.Name,Net_Price_vod__c,Total_Discount_vod__c]}}

Inserts the name of the products, content types, or sub-channels in the sent email. If an account selected Subscribe All, this message displays the channel label and the channel value.

Inserts an unsubscribe link in an email. The unsubscribe link inherits the Product or Detail Group + Product associated with the template.

When the recipient clicks the unsubscribe link, the opt-out activity is recorded for the Account, email address, and Product or Detail Group + Product in the corresponding Multichannel_Consent_vod record. All future emails to the Account plus the email address are suppressed for this Product or Detail Group + Product until an opt-in activity is collected or the opt-out expiration date is set.

Allows content creators to customize the provided unsubscribe page to better control branding, translation, and wording.

See Adding and Customizing Unsubscribe Links for more information.

Displays the email address associated with the unsubscribe request.

Displays the Detail Product, Detail Group, or Content Type associated with the simple unsubscribe request.

Although not required, it is recommended to include this token in unsubscribe pages to provide the end user information on what their simple unsubscribe request is for.

Renders as an unsubscribe button that is used as the action of an HTML form data for a simple unsubscribe.

The opt-out record created from the simple unsubscribe will be for the Product or Content Type of the Email Template where the unsubscribe link is clicked from.

Displays a selection menu with all Detail Products and Detail Groups with Approved Document records in Veeva CRM. Recipients can select which products or groups to unsubscribe from.

If the customized Unsubscribe page is used, the Unsubscribe object has an HTML field where Admins can configure a custom Unsubscribe Page

Related Unsubscribe Product records can be created to define the list of Product / Detail Groups displayed.

Detail Products and Detail Groups restricted to the recipient do not display in this list.

Enables recipients to modify their preferences. Used as the action attribute in the associated HTML form data.

Creates a Cancel button. When recipients select this button, no information is saved and the Cancel Confirmation page displays.

Tracks the following data about a web link shared with an HCP when appended to the link URL:

• Source – The location from where the users shared the link. When shared from Veeva CRM, the value is set to VeevaCRM.
• Device – The device used by the user to share the link. When shared from Veeva CRM on iPad, the value is set to iPad.
• Sent Datetime – The datetime when the user shared the link in ISO 8601 format

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.