Related Posts
Menu
When someone first loads a website that contains. Analytics code, they are assigned a unique user identifier and saved in a file in their browser. As long as that file is present, Analytics will be able to recognize it as the what-is same user. As many times as you log in, no matter how many days pass, you will be considered a single user. So far so good. However, if that person empties the cookies, changes browser or accesses from their mobile or tablet, the file will not be present and they will be treated as a new user for Analytics. Then.
The same person visiting the website from top industry data different devices will be considered different users. For Analytics, a user is not a person. A user is a cookie, a file, an identifier, a thing… What is a user in a digital product what-is ecommerce or SaaS? In the case of a SaaS (also ecommerce, membership websites, digital products, etc.), the concept of user is much more associated with a person. The way we differentiate users in a SaaS is by their user account data . By your access credentials. For those data that a person has indicated as personal. While in Analytics the only way to identify a user is by the presence of a cookie.
Whose identifier has been generated randomly ATB Directory in the case of a SaaS it is done by the way in which that person accesses our service . So, that person (and now yes, a person and not a thing), regardless of the device they access, must introduce themselves, logging in, before using our product. And, as a general rule, that person, whether they log in today or in X years, will have the same access credentials. Or at least the same identifier… The concept of user, in these cases, is more linked to the person than in the previous case. This is a more humane definition of the omelet .