Sharing presentations by email attachment versus secure link
Key Takeaway
Field users can email a presentation to an HCP as a PDF attachment or as a secure link. On the desktop site, they can send links only, even when both methods are enabled.
In Life Sciences Customer Engagement, field users can email presentations to healthcare professionals (HCPs) in two ways. An attachment sends the PDF that is included in the presentation's source files. A secure link opens the presentation on a dedicated Experience Cloud site, shows the latest version, expires after a set time, and captures engagement data. Admins decide which methods users can use, and each method has its own setup.
Attachments and secure links
An attachment is a PDF. The presentation's ZIP source files should include a PDF of the presentation, because that PDF is the file sent as the email attachment.
A secure link goes in the email body instead of being attached. A link does the following:
- Opens the presentation in the presentation player on a dedicated Experience Cloud site.
- Gives HCPs token-based access, so they don't need to log in or download attachments.
- References the latest version of the presentation in the org, so HCPs see up-to-date content.
- Needs no additional storage, because it references the presentation in the org.
- Expires after a set number of days, which is 7 days by default.
- Captures engagement data when HCPs view the presentation, such as pages viewed, time spent per page, and navigation path. Teams can use this data to optimize future presentations.
Ana, a field rep, emails Dr. Lee a link to a product presentation on March 1. The org uses the default 7-day link validity. On March 3, a newer version of the presentation is added to the org. When Dr. Lee opens the link on March 4, she sees the newer version, and Salesforce records the pages she viewed and how long she spent on each one. When she tries the link again on March 12, it has expired. If Ana had sent an attachment instead, Dr. Lee would have the PDF that was in the source files when Ana sent the email.