Analytics
2K members online now
2K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
 
Guide Me
star_border
Reply

Cookies & Javascript code

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi all,

 

I have a doubt regarding this HC article.

 

I don't understand what does it mean that I can "also create an use your own identifier"

 

As the tracking code executes, Google Analytics creates anonymous, unique identifiers to distinguish between users. There are different ways an identifier can be created. By default, the Google Analytics JavaScript uses a first-party cookie, but you can also create and use your own identifier.

 

 

  • Why a developer would want to use its own identifier and not the GA one?
  • Which are the benefits of this decision?

Thanks,

 

Jennifer

 

 

 

 

Marked as Best Answer.
Solution
Accepted by topic author Learning A
December 2015

Re: Cookies & Javascript code

A T
Participant ✭ ✭ ✭
# 2

Re: Cookies & Javascript code

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭
Hi GA Guru,

Thanks for the shared information.

I only have a doubt: I know that if I install the default cookie (CLIENT ID), I will be able to see the devices and browsers from the visits. Because I did it in the past. So, isn't that the main difference (advantage) with the USER_ID cookie?

Why would I need the USER_ID if I do have the metrics with CLIENT_ID?

Thanks,

Jennifer

Re: Cookies & Javascript code

A T
Participant ✭ ✭ ✭
# 4
A T
Participant ✭ ✭ ✭