用户ID，测量协议中的CID [英] UserId, CID in measurement protocol

问题描述

测量协议
为了识别新用户与返回用户，我们可以使用用户标识字段。 （也就是说，我们可以散列用户名或用户特有的其他标识符并将其与特定用户相关联。这样我们就可以识别新用户与有效返回用户。

问题关于CID -
CID用于唯一标识用户会话，直到会话过期。
我们是否必须手动跟踪会话过期以生成每用户会话的cid？

请澄清

解决方案

很久以后，这可以帮助其他人......

我的理解是，当用户标识引用已认证的用户时，CID引用设备。

因此，基本上，所有命中使用相同的客户端ID或用户ID将与GA中的同一用户相关联（请参阅 session unification ）。
$ b

客户端id代表一个独特的设备/浏览器，而用户id表示可以使用多个设备/浏览器与您的网站进行互动的唯一用户。from 优化智能文章

A GA中的会话由以下两组匹配组成：

• 具有相同来源/媒介/广告系列的前一个匹配


• 不到30分钟


• 具有相同的CID

您不需要手动跟踪会话过期，您可以始终发送相同的CID，Google会处理会话分割。
您只需要明确会话过期，如果您自己的会话感与Google不同。

所以在您的情况下，我会为每个会生成一个CID设备连接到该服务，并让Google处理为该设备分配的会话。

如果您添加用于跨设备跟踪的用户ID，则Google会考虑所有例如：

• 使用相同的用户ID作为单个用户的会话。
  用户A在设备X上的网站上出现（CID = X）


• 2小时后用户A在设备X上登录您的网站（CID = X）

此时Google会理解1个用户的2个会话。

• 用户在设备X上登录您的网站（CID = X，UID = A）


• 用户A在设备Y（CID = Y）上附带您的移动应用程序
  
• 用户A登录您的移动应用程序（CID = Y，UID = A）
  

使用会话统一功能，用户ID A将传播到设备Y上的所有会话，以便Google了解3个会话（2个设备） ，1位用户。

返回的用户使用该计划进行计算，此处用户A生成1次新访问和2次返回访问。

我目前正在使用这种模式，一切看起来都很好，但它是一个敏感的话题，如果有人知道更好或有评论和建议，我会带他们去！

Measurement protocol To Identify a new user vs. returning user , can we use the user id field . ( i.e we can hash username or other identifier unique to the user and associate it with a particular user . This way we can identify new users vs. returning users effectively.

Question on CID -- CID is used to indentify a user's session uniquely till the session expires. Do we have to track the session expiration manually to generate cid per user session ?

Pls clarify

解决方案

A long time after but that could help other people ...

My understanding is that the CID references a device while the UserID references an authenticated user.

So basically, all the hits with the same Client ID or User ID will be associated to the same user in GA (take a look at session unification though).

"A client id represents a unique device/browser. Whereas a user id represents a unique user that may interact with your website using multiple devices/browsers." from Optimizesmart article

A session in GA is represented by a group of hits both :

• less than 30 minutes away from the previous hit
• having the same source/medium/campaign
• having the same CID

You don't need to track the session expiration manually, you can always send the same CID, Google will handle the sessions split. You only need to explicit the session expiration if your own sense of session is different from Google's.

So in your case, I would generate a CID for each device that is connecting to the service and let Google handle the sessions split for that device.

If you add a UserID for cross-device tracking, then Google will consider all the sessions with the same UserID as being a single user.

Example :

• User A comes on your website on device X (CID = X)
• User A comes on your website on device X 2 hours later (CID = X)

At that point Google will understand 2 sessions for 1 user.

• User A logs on your website on device X (CID = X, UID = A)
• User A comes on your mobile app on device Y (CID = Y)
• User A logs on your mobile app (CID = Y, UID = A)

With session unification enabled, the UserID A will be propagated to all the session on device Y so Google will understand 3 sessions, (2 devices), 1 user.

Returning users are calculated with that scheme, here User A generated 1 new visit and 2 returning visits.

I'm currently working with that pattern and everything looks just fine but it's a touchy subject and if anyone knows better or has remarks and advices, I would take them !

这篇关于用户ID，测量协议中的CID的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！