Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ReportAE/TrackingActivity.htm
## Tracking Approved Email Activity
Tracking Approved Email activity enables end users to review the efficacy of sent emails and adjust sending habits to best suit each account relationship. Content admins can review Approved Email activity to learn how Approved Email content is being used by recipients, leading to optimization of content.
**Who can use this feature?**
* Content Admin Users — Browser, iPad, iPhone
* [Storing Sent Email Content](#Storing1)
* [Stamping Sent Emails with Source Information](#Stamping1)
* [Sent Email Statuses](#Statuses1)
* [Email Activity Event Types](#Types1)
* [Tracking Email Activity at the Fragment Level](#Tracking1)
* Users require an Approved Email license
### Configuring Tracking of Approved Email Activity for
[Content Admin Users](#)
To configure this feature, ensure [Configuring Approved Email](../InitialConfig/ConfiguringAE.htm) is complete.
### Using Tracking of Approved Email Activity as
[Content Admin Users](#)
Due to supporting [Universal Linking](https://developer.apple.com/ios/universal-links/) on the iOS HCP Engage app, click tracking is not supported for Approved Emails containing the following tokens:
* {{call2\_\_v.cobrowse\_url\_participant\_\_v}}
* {{em\_attendee\_\_v.webinar\_participant\_url\_\_v}}
* {{em\_event\_speaker\_\_v.webinar\_panelist\_url\_\_v}}
#### Storing Sent Email Content
A Sent Email record can record up to 262,144 HTML characters worth of content of a sent Approved Email. The first 131,072 characters of content is stored in the email\_content\_\_v field of the Sent Email. If there are more than 131,072 characters, the remaining characters up to the maximum are stored in the email\_content2\_\_v field.
#### Stamping Sent Emails with Source Information
The following sent\_email\_\_v fields automatically stamp with contextual information to inform end users and content admins the circumstances around when the email is sent:
* territory\_\_v – References the sender's territory. If the sender belongs to multiple territories, this field references the first common territory between the user and the recipient.
* email\_source\_\_v – References the field that is the source of the recipient’s email address
If an HCP is the recipient of an Approved Email, and the source of the email address used to send the HCP the email is the personemail\_\_v field on the account, the email\_source\_\_v field on the resulting Sent Email is account\_\_v.personemail\_\_v.
* email\_config\_values\_\_v – Stamps consent information, if applicable, and indicates if a test email address is used. This field also shows headers, free text entered by the user, and any selected picklist values.
#### Sent Email Statuses
The status\_\_v field on the sent\_email\_\_v object indicates the status of the sent email:
* approved\_\_v – Used to track review status
* bounced\_\_v – The email is successfully delivered to the recipient's email server, but not delivered to the recipient's mailbox. This may happen if the mailbox could not be found by the server. [Bounced emails](../SendAE/BouncedEmailManagement.htm) are reattempted once by Vault CRM.
* delivered\_\_v – The email is successfully delivered to the recipient's email server
* dropped\_\_v – The email is not delivered to the recipient's server. This may be because the email address is in the Email Engine's suppression list. Any email sent to an email address with an existing bounced record automatically receives a status of Dropped.
* failed\_\_v – Vault CRM did not successfully send the email, either due to expired content or the presence of an opt-out record. The reason for failure is stamped on the status\_details\_\_v field.
* group\_\_v – The email is sent from a group call. The associated business account does not receive the email, but is still tracked with this status.
* marked\_spam\_\_v – The email is successfully delivered to the recipient's email server, but the server marked the email as spam
* pending\_\_v – Used to track review status
* pending\_approval\_\_v – Used to track review status
* rejected\_\_v – Used to track review status
* saved\_\_v – The email is sent from Vault CRM and is awaiting confirmation from the server
* scheduled\_\_v – The email is scheduled to be sent from Vault CRM
* sent\_\_v – The email engine successfully sent the email but confirmation of delivery is not received
* unsubscribed\_\_v – The email is delivered successfully and the recipient unsubscribed via the link in the email
To improve performance, the email\_content\_file\_\_v attachment field on the sent\_email\_\_v record updates within hours after the completion of the process that sends scheduled emails. This has no impact on the delivery of email messages, tracking of activity, or the HCP experience.
#### Email Activity Event Types
The event\_type\_\_v picklist on the email\_activity\_\_v is automatically populated when the record is created and indicates the type of activity:
* opened\_\_v – The recipient opened the email. Mailgun tracks Opened events based on an image in the email rendering in the recipient's email client, usually a 1x1 pixel transparent image. If the recipient opens the email, the image downloads from the sending server, indicating the email is opened.
Opened events are imprecise due to email clients behaving differently. There are scenarios where the email is opened, but an Opened event is not tracked, for example, if the email client rendered the email as plain-text, or if the email client cannot display images. To help improve the accuracy of tracking opened emails, Veeva automatically creates an Opened event if a Clicked event is logged and no Opened event already exists.
* clicked\_\_v – A link in the email is selected
* unsubscribed\_\_v – The recipient completed the unsubscribe process. Generates an opt-out multichannel\_consent\_\_v record.
* unsubscribed\_all\_\_v – The email is delivered successfully and the recipient completed the global Approved Email unsubscribe process. Generates an opt-out multichannel\_consent\_\_v record and expires any previous opt-ins.
* bounced\_\_v – The delivery of the email failed
If the email bounced, the email address is added to the suppression list and any email sent to the address are automatically dropped. To remove an address from the suppression list, contact Veeva support. Once the address is removed from the suppression list, delete the associated multichannel\_consent\_\_v record.
* marked\_spam\_\_v – The email is marked as spam by the recipient
* dropped\_\_v – The delivery of the email failed. Generated automatically if there is a Bounced or Marked as Spam event.
If the [Bot field](CapturingBotActivity.htm) is populated on an Email Activity record, the activity is not counted toward the Opened, Last Opened, Total Opens, Clicked, Last Clicked, and Total Clicks amounts or the Last Email Activity Date field on the Sent Email record.
The following additional event types are tracked by Vault when Vault documents in an Approved Email are viewed. These events are written into Vault CRM during the Vault-CRM scheduled integration:
* viewed\_\_v – A document included in the email is viewed in PromoMats
* downloaded\_\_v – A document included in the email is downloaded from PromoMats
Some email clients do not track when a recipient selects a link in an email. When this occurs, the event types tracked by Vault do not have corresponding opened or selected events.
Additionally, the event\_msg\_\_v field on the email\_activity\_\_v object contains information about the event, including any applicable [SMTP Error Codes](https://www.usps.org/info/smtp_status.html).
#### Tracking Email Activity at the Email Fragment Level
End users and content admins can track activity from a fragment included in an Approved Email to gain further insight into what kind of content is accessed most frequently. The approved\_document\_\_v field on the email\_activity\_\_v object references the fragment responsible for the email activity.
For the Vault link, a content change is not required. For non-Vault links, Content Administrators need to add the {{AppDocId}} token to the tag in the Email Template or Fragment to indicate which URL needs tracking.
For example: Example - Click Here. .
If the AppDocId token is added to Vault links, the links are not accessible by users when previewing or editing the email.
### Related Topics
[Creating Approved Email Templates](../CreatingContent/CreatingAETemplates.htm)
[Approved Email Configuration Tokens](../CreatingContent/ConfigTokens.htm)
[Understanding Approved Email Deliverability Flightpath](https://vaultcrmflightpathqa.veevacrmqa.com/doc/Content/ApprovedEmail/ApprovedEmailDeliverability/1-Intro.htm)