What it is
If tracking returning usage from logged in users is desirable, we recommend the deployment of a user ID view.
Why it matters
This allocates a unique (but not personally identifiable) code to each user based on their login details and uses these to identify the user and tie their sessions together, rather than the much less reliable cookie method Google Analytics generally uses.
This provides additional information such as access through multiple devices and user returns over long time periods and allows us to differentiate clearly between habitual site users with login and the browsing public.
What to do
- If a user ID view is desirable, it would require developer to push user information into GTM’s data layer at the point of login.
- Once implemented, JB could do the rest of the required setup through GTM and GA.