Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/CreatingContent/ConfigTokens.htm

## 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?**

* Content Creation Users - Browser, iPad, iPhone
* [Inserting Email Fragments and Template Fragments](#Inserting)
* Users require an Approved Email license

Approved Email Tokens fall into one of the following categories:

* [Inserting Email Fragments and Template Fragments](#Insertin)
* [Content Tokens](#Content)
* [Standard Tokens](#Standard)
* [Object Reference Tokens](#Object)
* [Sent Email Related Tokens](#Sent)
* [Functionality Tokens](#Function)
* [Vault Tokens](#Vault)
* [User Input Tokens](#Text)
* [Text Tokens](#Text)
* [Picklist Tokens](#Picklist)
* [Signature Transaction Receipt Tokens](#Signatur)
* [Consent Capture Tokens](#Consent)
* [Unsubscribe Tokens](#Unsubscr)
* [Unsubscribe Link Tokens](#Unsubscr2)
* [Unsubscribe Page Tokens](#Unsubscr3)

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 CRM Desktop (Windows) 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

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Content Creation Users](#)

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{insertEmailFragments}} | Insert Email Fragments | 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](CreatingAETemplates.htm) for more information about template requirements. | All except Receipts and Double Opt In | Email Templates |
| {{insertEmailFragments[Minimum,Maximum]}} | Insert Email Fragments | 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.  To allow an unlimited maximum number of fragments, enter 0 as the maximum, or leave the maximum parameter blank. For example, the following fragments both require the user to select at least two fragments with no maximum limit:   * {{insertEmailFragments[2,0]}} * {{insertEmailFragments[2,]}}   To enable adding fragments with no minimum or maximum limits, leave both parameters blank. For example:   * {{insertEmailFragments[,]}} * {{insertEmailFragments[]}}   Do not insert multiple {{insertEmailFragments[Minimum,Maximum]}} tokens into the same Email Template. | All except Receipts and Double Opt In | Email Templates |
| {{emailTemplateFragment}} | Email Template Fragment | 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 |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Content Tokens](#)

Content tokens are tokens that add specific content or add links to related content.

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}} | Account Salutation | Inserts Account salutation | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{accFname}} | Account First Name | Inserts Account first name | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{accLname}} | Account Last Name | Inserts Account last name | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{accCredentials}} | Account Credentials | Inserts Account credentials from Account.Credentials\_\_v | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{userEmailAddress}} | User Email Address | Inserts the end user's email address from the Email (email\_\_sys) field on the User object.  This token is typically used in the from or reply-to fields of an outbound email template. | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{userName}} | User Name | Inserts the end user’s name. | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{userPhoto}} | User Photo | Photo of user stored in the user\_detail\_\_v object.  End users can view and edit their photo from the My Profile tab. Uploaded photos are resized to 160x120 pixels. To preserve clarity, resize the photo to 160x120 pixels prior to uploading the photo. | All | * Email Templates * Email Fragments * Template Fragments |
| {{parentCallDatetime}} | Parent Call Datetime | 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 call2\_\_v.call\_datetime\_\_v, if neither call2\_\_v.parent\_call\_\_v nor call2\_\_v.parent\_call\_mobile\_id\_\_v is populated * Value stored in call2\_\_v.parent\_call\_\_v.call\_datetime\_\_v, if call2\_\_v.parent\_call\_\_v is populated * Value stored in call2\_\_v.call\_datetime\_\_v of the call2\_\_v record, where the parent call2\_\_v.mobile\_id\_\_v = child call2\_\_v.parent\_call\_mobile\_id\_\_v | * Call * Remote Meeting | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{parentCallDatetime(FORMAT)}} | Parent Call Datetime | Creators can additionally specify the displayed format of the date or time.  See [Formatting Tokens to Display Date and Time](FormattingDateTime.htm) for more information. | * Call * Remote Meeting | * Email Templates * Email Fragments * Template Fragments |
| {{timeZone}} | Time Zone | 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 | * Email Templates * Email Fragments * Template Fragments * Subject Field |

#### Object Reference Tokens

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](SettingTargetPlatform.htm) for more information.

| Token |  | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| [{{ObjectName.FieldName}}](https://player.vimeo.com/video/547601104) | Object Reference | Content creators can use this token to directly reference any field of a supported field type on the following objects:   * account\_\_v * approved\_document\_\_v  Referencing the approved\_document\_\_v object is only supported in Email Templates. * call2\_\_v * user\_\_sys * user\_detail\_\_v   The following field types are supported:   * checkbox * Currency * Date * Date/Time * Email * Formula  Tokens for formula fields on the User object should be formatted according to the selected [target platform](SettingTargetPlatform.htm) on the approved document.  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. * ID * Number * Percent * Phone * Picklist * Text * Text Area   Examples:   * {{account\_\_v.formatted\_name\_\_v}} * {{account\_\_v.id\_\_v}} * {{account\_\_v.id}} * {{approved\_document\_\_v.language\_\_v}} * {{user\_\_sys.office\_phone\_\_sys}} | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{ObjectName.RelationshipName.FieldName}} | Object Reference | 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 | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{customContent}} | Custom Content | Inserts data from a defined custom query.  See [Inserting Queried Data into an Approved Email](InsertingQueriedData.htm) for more information.  This token is not supported on the CRM Desktop (Windows) platform. | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |

#### Sent Email Related tokens

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{EmailAddressUnsub}} | Email Address Unsubscribe | 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 | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{EmailId}} | Email ID | Inserts the ID of the sent\_email\_\_v record.  This token is not supported in Edit and Preview mode. | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{OrgId}} | Vault ID | Inserts the ID of the Vault CRM environment from which the email was sent. | All | * Email Templates * Email Fragments * Template Fragments * Subject Field |
| {{AppDocId}} | Approved Document ID | 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](../ReportAE/TrackingActivity.htm#Tracking) for more information. | n/a | * Email Templates * Email Fragments (URLs Only) * Template Fragments (URLs Only) |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Functionality Tokens](#)

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{addToCalendar}} | ICD Calendar Reminder | Inserts an .ICS attachment for recipients to add to their calendars. | * Engage Meeting * Medical Events * Events Management | * Email Templates * Email Fragments |
| {{approvedEmailAction[LandingPageURL,MessageIdentifier]}} | Approved Email Action | 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.  Uses the following parameters:   * LandingPageURL – The external, customer managed landing page. See the Landing Page Requirements section for more information. * MessageIdentifier – The value of a message\_identifier\_\_v field of a specific multichannel\_message\_\_v object   See [Tracking Multichannel Activities from Approved Emails](../ReportAE/TrackMCActivitesAE.htm) for more information. | All | * Email Templates * Email Fragments * Template Fragments |
| {{insertZoomDialInNumbers[Language Code]}} | Zoom Dial-in Numbers | 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](../../EngageOLD/EngageMeeting/AdvFunct/AddZoomDialIn.htm) for more information. | * Remote Meeting * Events Management | Email Templates |
| {{aiRewriteStart}}  And  {{aiRewriteEnd}} | AI Rewrite Start  And  AI Rewrite End | Used with Agentic Email to designate text eligible for AI Rewrites.  See [AI Rewrite Token for Approved Emails](../../../VeevaAI/EmailAgent/RewriteToken.htm) for more information. | All | Email Templates |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Vault Tokens](#)

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{$VaultDocID}} | Vault Document | Expands to a URL pointing to a 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](https://verteobiopharma.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 | * Email Templates * Email Fragments |
| {{ISILink}} | ISI Link | Expands to a URL pointing to a Vault document of type Important Safety Information. | All | * Email Templates * Email Fragments |
| {{PieceLink}} | Piece Link | Displays a URL to the Vault document associated as the Related Piece. | All | * Email Templates * Email Fragments |
| {{PILink}} | PI Link | Displays a URL to a Prescribing Information Vault document. | All | * Email Templates * Email Fragments |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### User Input Tokens](#)

#### Text Tokens

The {{customText}} tokens should not be accompanied by any other text when used as a Subject. Any additional text prevents the token from functioning.

End users should not enter HTML tags as input in free text and rich text fields.

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 (&zwnj;) should not be used in User Input Tokens (Text and Picklist Tokens).

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{customText}} | Custom Text | 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 | * Email Templates * Subject Field |
| {{customText(Length)}} | Custom Text 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 | * Email Templates * Subject Field |
| {{customText(Length|DefaultText)}} | Custom Default Text | 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 | * Email Templates * Subject Field |
| {{customText:Required}} | Custom Text | 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}} | Custom Rich Text | 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:   * Bold, italicize, and underline text * Add bullets and numbers * Increase or decrease indents   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](../ManagingContent/RestrictedWords.htm). | 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 (&zwnj;) should not be used in User Input Tokens (Text and Picklist Tokens).

| Token |  | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{customText[options]}} | Custom Picklist | 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. | All except Receipts and Double Opt In | * Email Templates * Subject Field |
| {{customText[##ContentToken1##|##ContentToken2##]}} | Custom Picklist | 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\_\_v   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. | All except Receipts and Double Opt In | * Email Templates * Subject Field |
| {{customText[##ContentToken1##|##ContentToken2(FORMAT)##]}} | Custom Picklist | 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](FormattingDateTime.htm) for more information. | All except Receipts and Double Opt In | Email Templates |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Signature Transaction Receipt Tokens](#)

See [Creating Approved Email Receipt Templates for Signature Transactions](../SendAE/EmailReceiptsforSignatureTransactions.htm) for more information.

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{insertCallSample[Column1,Column2](FORMAT)}} | Insert Call Sample | 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]}}  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](FormattingDateTime.htm) for more information. | Receipts | Email Templates |
| {{insertCallSample[filterProductType=TYPE,Column1,Column2]}}}} | Insert Call Sample | 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 |
| {{insertMedicalInquiry[Column1,Column2(FORMAT)]}} | Insert Medical Inquiry | 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\_\_v,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](FormattingDateTime.htm) for more information. | Receipts | Email Templates |
| {{insertOrderLine}} | Insert Order Line | 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\_\_v,product\_\_v.Nname\_\_vame,net\_price\_\_v,total\_discount\_\_v]}} | Receipts | Email Templates |
| {{insertSignature}} | Insert Signature | Inserts a photo copy of the signature. | Receipts | Email Templates |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Consent Capture Tokens](#)

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{insertConsentLines}} | Insert Consent Lines | 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. | * Double Opt In * Consent Confirmation | Email Templates |
| {{insertMCConsentLines[Subscribed,Unsubscribed]}} | Insert Multichannel Consent Lines | Inserts multichannel\_consent\_\_v records into the Approved Email. The two parameters represent the label of the section headers.   * Subscribed – Displays all Multichannel Consent records with an opt\_type\_\_v of either opt\_in\_\_v or opt\_in\_pending\_\_v * Unsubscribed – Displays all Multichannel Consent records with an an opt\_type\_\_v of opt\_out\_\_v   If the parameters are blank, default labels are defined by the SUBSCRIBED;;ConsentCapture and UNSUBSCRIBED;;ConsentCapture Veeva Messages.  This token is only supported in emails sent as receipts for Consent Capture. | Consent Capture Receipts | Email Templates |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Unsubscribe Tokens](#)

#### Unsubscribe Link Tokens

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{unsubscribe\_product\_link}} | Unsubscribe Product Link | 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\_\_v 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. | All except Receipts and Double Opt In | * Email Templates * Email Fragments |
| {{unsubscribe\_product\_link[,unsubscribe\_\_v.unsubscribe\_identifier\_\_v]}} | Unsubscribe Product Link | Allows content creators to customize the provided unsubscribe page to better control branding, translation, and wording.  See [Adding and Customizing Unsubscribe Links](ConfigurableUnsubscribe.htm) for more information. | All except Receipts and Double Opt In | * Email Templates * Email Fragments |
| {{unsubscribe\_product\_link[External URL,unsubscribe\_identifier\_\_v]}} | Unsubscribe Product Link | Embeds an unsubscribe link that directs users to an external hosted site defined by the External URL parameter.  Used by the [Embedded Unsubscribe](EmbeddedUnsubscribe.htm) feature. | All except Receipts and Double Opt In | * Email Templates * Email Fragments |

#### Unsubscribe Page Tokens

| Token | Token Label | Description | Rendered Format | Required? |
| --- | --- | --- | --- | --- |
| {{EmailAddressUnsub}} | Email Address Unsubscribe | Displays the email address associated with the unsubscribe request. | Label |  |
| {{emailProduct}} | Email Product | Displays the Detail Product or Detail Group 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. | Label |  |
| {{submitUnsub}} | Submit Unsubscribe | 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. | Button |  |
| {{productModList}} | Unsubscribe Product List | Displays a selection menu with all Detail Products and Detail Groups with Approved Document records in Vault 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. | Label |  |
| {{submitPerfOptions}} | Submit Preference Options | Enables recipients to modify their preferences. Used as the action attribute in the associated HTML form data. | Button |  |
| {{cancel}} | Cancel | Creates a Cancel button. When recipients select this button, no information is saved and the Cancel Confirmation page displays. | Button |  |
| {{unsubscribeAll}} | Unsubscribe All | Enables email recipients to unsubscribe from all Approved Email communications. This enables compliance in certain markets that require this option. | checkbox |  |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)

### Website Tokens](#)

| Token | Token Label | Description | Supported Entry Points | Works In |
| --- | --- | --- | --- | --- |
| {{linkTracker}} | Link Tracker | 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 Vault CRM, the value is set to VeevaCRM. * Device – The device used by the user to share the link. When shared from Vault 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](../../Engage/Share/ShareCLMLink.htm#TrackWeb) for more information about tracking websites. | n/a | Website URLS |
| {{MessageId}} | Message ID | Inserts the Mobile Id of the sent\_message\_\_v record when the website is sent from the mobile device. | n/a | Website URLS |

### Related Topics

[Creating Approved Email Fragments](CreatingAEFragments.htm)

[Creating Approved Email Templates](CreatingAETemplates.htm)