Referer 字段是否存在无效内容？
我想知道通过单击本机应用程序中的链接访问我的网站的用户的身份。
我的应用程序可以使用唯一的用户 ID 填充引用字段吗？
Referer 字段必须是有效的 URL 吗？
Google Analytics（分析）是否会处理非 URL 的引用站点？
我可以模拟一个类似 http://www.user.com/656 的 URL，其中 656 是用户 ID 。
有什么注意事项吗？
I'd like to know the identities of users who come to my website by clicking on a link in my native application.
Could my app populate the referer field with a unique user ID?
Does the referer field have to be a valid URL?
Will Google Analytics handle a referer that isn't a URL?
I could mockup a URL like http://www.user.com/656 where 656 is the user ID.
Any caveats?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
好问题。一方面，我已经重新映射了相当多的 GA 字段（包括推荐），而且我从未遇到过问题。此外，这样做是 GA 的核心功能（见下文）；换句话说（我相信你知道）GA 实际上为其用户提供了模板（通过高级过滤器）来将这些字段处理得无法识别。
)
另一方面，我可以想到一种我相信 Google 会反对的情况（实际上只有一种）在这种情况下，替换信息违反了 GA 隐私政策。特别是，通过 GA 显示或存储或跟踪任何个人身份信息均违反了本政策[斜体是我的，不是来自 GA 隐私的引用政策]。
谷歌的实际定义：
是唯一的用户ID、个人身份信息吗？用于清楚区分一个用户与另一个用户的数据与用于识别每个用户的数据之间存在差异。这种区别可能取决于安全性，即拥有您的唯一用户 ID 列表的人如何容易地发现其背后的用户身份？
Good question. On one hand, i have remapped quite a few of these GA Fields (including Referral) and i have never had a problem. In addition, doing so is core functionality in GA (see below); in other words (as i am sure you know) GA actually provides its users with the templates (via Advanced Filters) to munge these Fields beyond recognition.
)
On the other hand, i can think of one situation (only one actually) in which i believe Google would object and that's the case where the replacement information violates the GA Privacy Policy. In particular, displaying or storing or tracking via GA any personally identifiable information violates the Policy [italics are mine, not a quote from the GA Privacy Policy].
The actual definition from Google:
Is a unique user ID, personally identifiable information? There is a difference between data intended to clearly distinguish one user from another, and data intended to identify each user. The distinction might depend on security--i.e., how easily could someone who had in their possession a list of your unique user IDs, discover the user identifies behind them?
从技术上讲，Referrer 标头仅指定 URL。如果您想构建“假”URL，请提出一个特定于您的应用程序的 URI 方案。类似
userid:656。Technically, the referrer header just specifies a URL. If you want to construct "fake" URLs, come up with a URI scheme specific to your application. Something like
userid:656.