What is a Digital Touch?
A digital touch is a page view by a visitor to your site that originated from a digital channel. With some media, like email, you have a good idea who that visitor is, since they're associated with something unique like an email address.
Other digital marketing approaches (like paid ads on Google) also drive visitors to your site. These visitors are often harder to uniquely identify. We call these visitors anonymous digital touches, as you don't yet have identifying information on them.
Touchpoint Capture tracks digital and anonymous digital touches. The following types of digital touches are tracked:
- Clicks from paid ads, where the clicked link contains UTM parameters in the URL that you have configured
- Organic search engine traffic from major search engines (Google, Bing, Yahoo!)
- Organic traffic from social networking sites (Facebook, Twitter, LinkedIn)
- Other referral traffic that comes from links that do not contain UTM parameters, such as a blog post of someone reviewing your site, or a third-party partner
Touchpoint Capture Technical Data Flow
Below is a more detailed explanation and view of how visitor data from tracked links flows into Salesforce.
- Each time a visitor clicks on a digital link to your website, Touchpoint Capture saves information about that visit.
- When a visitor to your site fills out and submits a form:
- This action is captured by your marketing automation platform (MAP).
- The email address from the form submission is associated with the (now formerly) anonymous digital touch information.
- The MAP will create a Lead and add that Lead to a campaign in Salesforce.
- If that associated campaign in Salesforce is noted as one that should track digital touches, it will receive the anonymous digital touch information from Touchpoint Capture and populate this on the related Campaign Member record.
- The first anonymous digital touch's details will be associated as a Campaign Member, added to the Anonymous Digital Campaign record.
Tracking Details
This section provides details about what Touchpoint Capture tracks.
UTM Parameters
When a visitor views a page and one or more of the following UTM parameters are present in the URL, Touchpoint Capture will record this page view as a digital touch.
- utm_campaign
- utm_content
- utm_medium
- utm_source
- utm_term
Non-UTM-Tracked Referrals
When a visitor views a page and there are no UTM parameters present in the URL, it still may be tracked as a digital touch if it meets any of the following conditions:
Organic search engine referrals
When the referring URL is Google, Yahoo, or Bing, a digital touch will be recorded and the following UTM data will be set on the touch:
- utm_source will be set to the name of the search engine ("google," "bing," "yahoo").
- utm_medium will be set to "organic."
- utm_term will be set to the search term that produced the search result that was clicked on. This is only applicable to Bing, as Yahoo and Google prevent access to that information.
Social network referrals
When the referring URL is Facebook, LinkedIn, or Twitter a digital touch will be recorded and the following UTM data will be set on the touch:
- utm_source will be set to the name of the social network ("facebook," "linkedin," "twitter").
- utm_medium will be set to "social."
Other referrals
When the referring URL is any other website than the ones listed above, a digital touch will be recorded and the following UTM data will be set on the touch:
- utm_medium will be set to "referral."
NOTE: All digital touches get the Referring Page and Referring Page Raw fields populated when the referring URL is available. See also What Data Gets Tracked.
Non-Referrals
When there is no referring URL and no UTM parameters present in the URL, a digital touch will be recorded and the following UTM data will be set on the touch:
- utm_source will be set to "direct."
Duplicate Digital Touches
Touchpoint Capture does not track duplicate digital touches. When a user visits the same page with the same UTM parameters more than once, Touchpoint Capture will only record the first digital touch and will ignore the subsequent ones.
Sample Visitor Journey: One-Click Conversion
Let's imagine that a visitor has clicked on a paid ad, arrived at your landing page, and filled out a form.
Understanding the Steps
- The First Anonymous Digital Touch is recorded and saved to the anonymous visits database in AWS. Unique visitor ID is saved to a cookie.
-
Visitor fills out form.
- In this case, the First & Last Digital Touch are the same. This touch is recorded by the MAP and saved to the known visits database in AWS by DST.
- This Digital Touch data is then captured on the Campaign Member associated with this Campaign.
- Visitor arrives at the confirmation page.
Sample Visitor Journey: Multiple Bounces and Visits
This describes a sample visitor journey and corresponding digital touch tracking that occurs. In this case, a visitor has clicked on a paid ad, arrived at your landing page, left your site, returned via other paid ads or organic methods, until finally filling out a form.
Understanding the Steps
- Visitor arrives to site. First Anonymous Digital Touch is recorded and saved to the anonymous visits database in AWS. Unique visitor ID is saved to a cookie, then visitor bounces and leaves site.
- Visitor returns to site. Anonymous Digital touch is recorded under user's visitor id. Visitor bounces and leaves site.
-
Visitor returns to site and fills out a form.
- Last Digital Touch is recorded by MAP and saved to AWS by DST. The visits from the anonymous visits database are transferred to the known visits database in AWS.
- Last Digital Touch is captured on the Campaign Member associated with this Campaign.
- First Digital Touch data is pulled into Salesforce from AWS.
- First Digital Touch data is captured on the Campaign Member associated with Anonymous Digital Touch Campaign.
- If Middle Touchpoint Sync is enabled: Digital Touches occurring between First Digital Touch and Last Digital Touch are pulled into Salesforce and associated to defined "Middle Touch Campaign." Repeat campaigns are automatically created to accommodate multiple middle touches.
- Visitor arrives at confirmation page.
Sample Visitor Journey: Conversion From Internal Page Traffic
NOTE: This section is only for FCI employee education.
This describes a sample visitor journey and corresponding digital touch tracking that occurs. In this case, a visitor has clicked on a paid ad, arrived at your site, visited other pages on your site, until finally filling out a form.
Understanding the Steps
- First Anonymous Digital Touch recorded in AWS.
- Visitor arrives to site, then visits other pages on the site.
-
Visitor fills out a form.
- Form fill recorded by MAP, but not considered a Digital Touch as it came from an internal referral (with no UTM parameters). No Digital Touch information recorded.
- First Digital Touch data is pulled into Salesforce from AWS as DST recognizes this also as the Last Digital Touch. Digital Touch data is captured on the Campaign Member associated with this campaign.
- Visitor arrives at the confirmation page.
Digital Touch Data Elements
Touchpoint Capture captures a variety of useful data for each digital touch (listed below). Consider the following URL examples while reviewing the data below:
Digital touch: https://mycompany.com/the-great-white-paper?utm_source=foo
Referring URL: https://acmeco.com/press-release/123456?param1=abc
| Field Name | Description |
|---|---|
| Property Domain | The domain present in the URL at the time of the digital touch. For example: "mycompany.com." |
| Property Location | The location within the property where the touch occurred. This is typically a landing page. For example: "/contact-us." |
| Email Address | The email address that the user provides on the form submission. |
| External Visit ID | The unique identifier of the digital touch in the DST database. |
| First Digital Touch | True/False. The earliest digital touch on record in the DST database for a given visitor. |
| Location | The location present in the URL at the time of the digital touch. For example: "the-great-white-paper." |
| Referrer Page | The hostname of the referring URL, if available. For example: "https://acmeco.com." |
| Referrer Page Raw | The entire referring URL, if available. For example: "https://acmeco.com/press-release/123456?param1=abc." |
| UTM Campaign | The value of the utm_campaign parameter that was present in the URL for the digital touch. |
| UTM Content | The value of the utm_content parameter that was present in the URL for the digital touch. |
| UTM Medium | The value of the utm_medium parameter that was present in the URL for the digital touch, or the inferred value that DST populated based on the referring URL. |
| UTM Source | The value of the utm_source parameter that was present in the URL for the digital touch, or the inferred value that DST populated based on the referring URL. |
| UTM Term | The value of the utm_term parameter that was present in the URL for the digital touch. |
| Visit Date/Time | The date/time that the digital touch occurred. |
| Number of Middle Touchpoints | The number of middle digital touchpoints that occurred between the first digital touchpoint and the form fill digital touchpoint |
Where Are Digital Touches Stored?
This section describes architectural details of the feature.
DST Cookie
The Touchpoint Capture cookie stores a unique identifier for the visitor that is used to consolidate anonymous touches with the visitor's email address once they submit a form.
NOTE the following bullet points are only visible to internal FCI users of MindTouch:
- Upon form fill, all of the touches currently in the anonymous visits database (DynamoDB) are saved to the known visits database (RDS).
-
The cookie holds the following piece of information:
- Visitor ID, which is a unique identifier for the user.
- The cookie has an expiration period of two years.
Anonymous Visits Database (DynamoDB)
- Each Full Circle customer has their own dedicated anonymous visits database where all anonymous digital touches for visitors who have not yet converted (e.g. filled out a form) are stored.
- The database is hosted and managed by Full Circle at Amazon Web Services (AWS) using the DynamoDB microservice.
- Anonymous visit records are stored for 6 months by default before they are deleted if the visitor has not yet converted. If you would like to change this timeframe, please reach out to your Customer Success Manager.
NOTE the following bullet points are only visible to internal FCI users of MindTouch:
- Customers are not able to directly access this database.
- Upon form fill, all of the touches currently in the anonymous visits database (DynamoDB) are saved to the RDS database.
Touchpoint Capture Database (RDS)
- Each Full Circle customer has their own dedicated Touchpoint Capture database where all digital touches for converted visitors and related user information are stored.
- The database is hosted and managed by Full Circle at Amazon Web Services (AWS) and is fully encrypted while at rest.
NOTE the following bullet points are only visible to internal FCI users of MindTouch:
- Customers are not able to directly access this database.
- Upon form fill, all of the touches currently in the anonymous visits database (DynamoDB) are saved to the RDS database.
Salesforce
- Digital touches are stored in Salesforce as Campaign Member records.
NOTE the following bullet points are only visible to internal FCI users of MindTouch:
-
Digital touches get created by DST in Salesforce in the following ways:
-
DST will augment a Campaign Member record by populating DST fields on the record.
- Specifically, the DST field called Digital Touch will be set to true.
- These records are typically created by marketing automation and will get their DST fields populated if there is a digital touch that took place.
- DST may insert one new Campaign Member for a lead/contact as the first Anonymous Digital Touch. These get added to the campaign (typically with the same name) specified in the app configuration. However, if the first digital touch is not anonymous (it's a form fill), DST will not create this campaign member. Instead, it will augment the record as described above.
- DST may insert additional Campaign Members for a lead/contact for the digital touches that occur between the first Anonymous Digital Touch and the Digital Touch associated to the Form Fill member. This will only occur if customer has enabled Middle Touches in DST Configuration. These touches will get added to the "Middle Touch Campaign" as specified in the configuration. Repeat campaigns will automatically be generated (up until the Auto Cascade Limit) for multiple middle touchpoints.
-
DST will augment a Campaign Member record by populating DST fields on the record.
Comments
0 comments
Please sign in to leave a comment.