As shown in figure:
The answer has something to do with this analytics. Js, Google home stuff.
In order for Google Analytics to determine whether two different matches belong to the same user, a unique identity associated with a particular user must be sent along with each match. The analytics. Js library accomplishes this with the client-ID field, which is a randomly generated unique string whose ID is stored in a browser Cookie to associate a user with the same web sites he or she visits. By default, analytics. Js uses a first-party Cookie named _ga to store the client-ID, but the Cookie’s name, domain, and expiration date are all customizable. Other cookies created by analytics. Js include _GID, AMP_TOKEN, and GAC. These cookies store the user’s other randomly generated ids and advertising series of information. Analytics. Js can identify uniquely identified users across browsing sessions with cookies, but not across browsers or devices. If your site has its own authentication system, you can use the User ID feature in addition to the client ID to more accurately identify users across all devices they use to access your site.
From Google:Developers.google.com/analytics/d…
[ImG-fSIFWyil-1566692797962] (https://upload-images.jianshu.io/upload_images/2085791-dcc88e58a67cac8c.png?imageM Ogr2 /auto-orient/strip% 7cimageview2/2 /w/1240)] For more original articles from Jerry, please follow the public account “Wang Zixi “:
