Release Schedule
| Name | Description | Date |
|---|---|---|
| Sandbox Update | All installs in sandboxes will receive the update automatically | 3/15/2021 |
| Production Update | All installs in production orgs will receive the update automatically | 3/17/2021 |
Release At-a-Glance
|
Item |
Type |
Summary |
Automatically visible to all users |
Not automatically visible, requires some setup |
Contact Support to enable |
|---|---|---|---|---|---|
| Journey Explorer | New Feature | Visualization that allows you to explore all campaign touches related to the originating contact for an opportunity. | X | ||
| Session Landing Page Data | Improvement | New fields added to the CampaignMember to show the information about the session landing page for the digital touch. | X |
New Features
Journey Explorer
What:
Journey Explorer enables marketers to visualize all marketing touches for the originating contact on an opportunity, including responses in Salesforce as well as all digital touches that are stored outside of Salesforce, giving you a complete view of marketing interactions for the contact/opportunity. For more info see the Journey Explorer documentation.
Where:
Journey Explorer can be accessed by clicking on the "Journey Explorer" button on an opportunity.
Who:
Journey Explorer helps marketers better understand what campaigns, both digital and non-digital, were influential in the creation of the opportunity. Marketers can gain insights into key dimensions of the customer journey including utm source, campaign, medium, content, term, website location, first touch, last touch, and days to form fill.
Why:
Digital Source Tracker tracks all digital touch points for prospects on your web properties and stores them outside of Salesforce. Only a subset of those touches are saved to your Salesforce environment (to avoid data bloat). Journey Explorer enables you to see all of the touch points, within Salesforce and external to Salesforce, in a unified view, providing you with a complete picture of the journey. DST continues to store only a limited number of touch points in Salesforce, but Journey Explorer dynamically pulls in touch points stored externally to provide you insight into the full set of touch points.
When:
Journey Explorer needs to be enabled in order for users to access it. See below for how to enable the feature.
How:
In order to make the feature available to users in your org, be sure to do the following:
- A system administrator will need to add the "Journey Explorer" button to the opportunity page layout(s)
- For classic, add the custom button from the "Buttons" list to the "Custom Buttons" section
- For lightning experience, add the custom button from the "Mobile & Lightning Actions" list to the "Salesforce Mobile and Lightning Experience Actions" section
- Ensure that the DST application is enabled in your org
Key considerations
- In order for Journey Explorer to be able to connect externally to the DST service where digital touch points are stored, the DST application must be enabled in your org. If you are unsure about this contact your system administrator.
- Journey Explorer is dependent on the Admin Originating Contact field being populated on the opportunity. Passive orgs may experience limited functionality.
- Because Journey Explorer is blending Salesforce data with external data to create a visualization, it is not possible to run standard Salesforce reports on the data set. The data is only available in the user interface of Journey Explorer.
Improvements
Session Landing Page Data
What:
Digital Source Tracker (DST) now keeps track of a visitors' session start time when they visit your web property, and will put information about the landing page for a session, the referring page, and other data onto the form fill campaign member. The default session duration is 60 minutes. If you would like to modify this for your site(s), contact your Full Circle customer success manager.
Where:
The following new fields have been added to the CampaignMember object and are part of the Digital Source Tracker managed package.
| Field | Description |
|---|---|
| Session Landing Page Property Domain | The domain associated to the landing page for the session |
| Session Landing Page Property Location | The URL path of the landing page for the session |
| Session Landing Page Referrer Page Raw | The entire URL (including parameters) of the referring page to the landing page |
| Session Landing Page URL Raw | The entire URL (including parameters) of the session landing page |
| Session Landing Page UTM Campaign | The value that was present in the utm_campaign parameter when visitor viewed the landing page |
| Session Landing Page UTM Content | The value that was present in the utm_content parameter when visitor viewed the landing page |
| Session Landing Page UTM Medium | The value that was present in the utm_medium parameter when visitor viewed the landing page |
| Session Landing Page UTM Source | The value that was present in the utm_medium parameter when visitor viewed the landing page |
| Session Landing Page UTM Term | The value that was present in the utm_term parameter when visitor viewed the landing page |
| Session Landing Page Visit ID | The unique identifier of the landing page touch in the DST database |
| Session Landing Page Visit Date/Time | The date/time that the visitor viewed the landing page |
Who:
Marketers can see the landing page for the session, the landing page referring URL, and other information related to a form fill response (see above table).
Why:
Providing the session landing page and referring URL provides the marketer with better insights about the effectiveness of referring sources and landing pages on their sites that result in conversions.
When:
Once V1.7 is deployed to your org, the data for this feature will automatically start to flow into your Salesforce org and will be saved to the CampaignMember
How:
In order to view the data on individual records, a system administrator will need to place the new fields on the CampaignMember page layout(s).
Key considerations
- DST will not back-populate responses with this information, which means that you will only have this data on records after V1.7 of DST is deployed to your org.
- In the case where a form fill occurs outside of the session duration window, the form fill response is treated as the session landing page.
Comments
0 comments
Please sign in to leave a comment.