Approved Email

Detecting Automated Email Interactions

Email bots crawl email content to identify and prevent links to malware or phishing attacks from entering a recipient's inbox. Bots interacting with emails can trigger false events. When bots traverse emails, they interact with links which trigger the associated tracking code. Similar false events can be triggered when email clients pre-fetch content and store it on their servers to improve the user experience by reducing load times. When possible, information about the bot is captured to help organizations distinguish false events from real events triggered by recipients.

By filtering bot activity, organizations can gain a clearer picture of genuine recipient engagement with emails. With more accurate event data, organizations can identify which emails resonate most with their audience and make data-driven decisions about email marketing strategies.

Using Bot Activity Capturing

When there is an Email Activity that Mailgun detects to have been triggered by a bot, the Bot_vod field on Email_Activity_vod object is populated with one of the following values:

• apple - Indicates an Apple MPP bot
• gmail - Indicates a Gmail bot
• generic - Indicates an unknown bot (most likely a firewall or anti virus scan)

When an Email Activity is triggered due to the recipient taking an action on the email, the resulting Bot_vod field is blank.

Engage

Syncing Custom Document Types of ISI and PI Documents

Customers who use custom document types for ISI and PI documents can sync them to Veeva CRM. When editing the appropriate Vault connection in the CLM Admin Console, populate the ISI Document Type and Subtype and/or PI Document Type and Subtype fields in the Reference Documents section appropriately. Use the following format: type = 'document type api name' and subtype = 'subtype api name'.

The Document Type and Subtype combination must be different for ISI documents and PI documents. Subtypes are optional.

Populating these fields overrides the default document types and subtypes. See Supported Document Types for more information about the default document types and subtypes.