Originating Authors:
Vivek S V & Jayanth Kanala, Nabler
Introduction:
In the language of an analytics tool, a device/cookie is a customer. But the real world is so different. A customer can visit your website through multiple devices and channels but still, he needs to be treated as a single customer. If you strictly go by the analytics-customer, then you are targeting the same human being through marketing efforts which can cost you millions. Also, you are barraging a customer with numerous touch points, unintentionally. The reality is that not many have realized this mistake. So, how this can be solved?
The popular analytics tools offer a feature called userID (aka <g class="gr_ gr_79 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" id="79" data-gr-id="79" style="color: #000000; font-size: 14px;">visitorID</g>) which could solve this problem. This recipe details out the process of leveraging User ID and its applications.
Analysis Overview:
In this recipe, we are going to
-
illustrate user flow and the role of userID
-
walk you through the steps involved in enabling userID
-
illustrate offline data integration process with the help of userID
-
elaborate on vendor specific userID / visitorID implementation steps
Analysis Benefits:
- More accurate view of unique users of your website and no duplication of users
- Cross device tracking and ability to integrate offline/CRM data with analytics data
- Find relationships between your acquisitions, engagement, and conversions
- Helps create more audience segments for marketing tools such as Adobe Target, Google Survey, Google Optimize etc.,
- Various reports are offered by analytics tools based on userID / <g class="gr_ gr_278 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" id="278" data-gr-id="278">visitorID</g> for further analysis
DAA members, go here to view full recipe.------------------------------
Jayanth Kanala
Nabler (Corporate Account)
Bangalore
------------------------------