Please enable JavaScript.
Coggle requires JavaScript to display documents.
User-ID: Measuring Real Users Instead Of Devices (allows us to: (Measure…
User-ID: Measuring Real Users Instead Of Devices
ability to track cross-device behavior for individuals. Real individuals – real unique users!
allows us to:
Measure the amount of users to our digital properties with far greater accuracy.
Unlock greater insights with user-specific reports that are otherwise unavailable in standard reports.
Segment prospective customers from current customers more effectively.
More accurately attribute value to key conversion channels by improving upon conversion paths.
Background
Client ID, which is unique to the specific browser and device and stored in cookies.
How to Implement
Step 1: Identify your visitors with unique User-IDs
pull them from an existing resource, such as a
customer database
CRM
cookie.
Campaigns
you could send out an email promotion which contains a dynamically generated link back to your website.
That link would contain a unique ID for each subscriber,
would be collected once the user clicks on the link and comes to your website.
Step 2: Configure GTM to Collect the User-ID and Assign It To Users.
alt 1.
Start by creating a variable in GTM
var dataLayer = window.dataLayer = window.dataLayer || []; dataLayer.push({'userID' : 'user132156'});
alt 2.
grab the ID out of a cookie that you already have on your site.
You can set up a First Party Cookie variable with the name of the cookie you will be getting the IDs from:
Click into your existing Google Analytics tag and choose Configure Tag to edit the existing settings.
Under More Settings > Fields to Set, add a new field and name it “userId.” As you
Step 3: Configure the User-ID settings in Google Analytics
read and agree to the User-ID policy and then enable the feature in the Admin settings at the Property level,
Tracking Info > User-ID.
Sessionization
users who have logged into your website in the past will not automatically have an ID assigned to them.
user will browse your website for a period of time, before they decide to login.
possible to group these hits set prior to when the User-ID was assigned,
session unification feature in the Admin settings when you configure the User-ID.
persisting the User-ID in a cookie so that each time users return to your website and do not log in you can still recognize their User-IDs.
Step 4: Configure a User-ID View
a specific View that will include only hits that were made by users who were assigned a User-ID.
In this View, each of your standard reports will be based off the User-IDs rather than the Client IDs. Granted,
Multi-Channel Funnel reports and Acquisition reports may be more accurate as they reflect upon users rather than cookies, for example.
Frequency and recency of returning users may also be more accurate.
you also receive new reports that are only available in User-ID-specific Views.
These reports help paint a more realistic picture of the number of devices used to access your website, which devices purchases are made on most frequently, and more.
Device Overlap
Path Options
see the steps that occurred before or after a particular event occurred
Acquisition Devices
which devices users originally used to access your website
revenue from each device in comparison to revenue from each originating device:
