og:url 与谷歌分析活动的行为是什么？
我正在努力在我们的网站上实施开放图谱协议。 如果我参考 Open Graph 文档，我应该为 og:url 值输入这些类型：
<meta property="og:url" content="http://www.website.com/section/article.html" />
如果我像这样继续，我应该能够：
- 从 facebook 洞察中访问特定 url + 所有网站的统计数据。
但我想要更多！事实上我希望能够：
- 在谷歌分析上查看这些数据（不仅在 Facebook 上）
- 根据部分进行另一个级别的分析
- 查看来自“点赞按钮”与复制/过去的流量
为此，我想拥有这样的东西：
<meta property="og:url" content="http://www.website.com/section/article.html?utm_source=section&utm_medium=web&utm_campaign=social" />
所以这是我的问题：
- 是否允许、推荐、是否有效？
- 如果我这样做，我可以确保 FB 分析上没有重复的项目吗（http://www.website.com/section/article.html vs website.com/section/article.html?utm_source=section&） utm_medium=web&utm_campaign=social)
- 还有其他解决方案吗？ （链接到 facebook.website.com/section/article.html 并使用重定向到 website.com/section/article.html 的分析代码？）
非常感谢
抱歉我的英语语法很差（法国人）
I'm working to implement Open Graph protocole on ours websites.
If I refer to the Open Graph documentation, I should put these kind of input for the og:url value :
<meta property="og:url" content="http://www.website.com/section/article.html" />
If I proceed like this, I should be able to :
- access stats from the facebook insight for a specific url + for the all website.
But I want more ! Indeed I want to be able to :
- See these data on google analytics (not only in Facebook)
- Have another level of analytics based on section
- See what traffic coming from "like button" vs copy/past
To do this, I was thinking to have something like this :
<meta property="og:url" content="http://www.website.com/section/article.html?utm_source=section&utm_medium=web&utm_campaign=social" />
So here are my questions :
- Is it allowed, recommanded, gonna worked ?
- If I do so, could I be sure to not have duplicate item on the FB analytics (http://www.website.com/section/article.html vs website.com/section/article.html?utm_source=section&utm_medium=web&utm_campaign=social)
- Is there another solution ? (linking to facebook.website.com/section/article.html with an analytics code redirecting to website.com/section/article.html ?)
Thank's a lot
Sorry for my poor english syntax (a french guy)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你一次问了太多问题。我要把它分解。
从 Facebook 洞察中访问特定网址 + 所有网站的统计信息。 错误！ Open Graph 协议旨在为 Facebook 和其他网站提供有关您网站上的内容类型及其内容的语义信息。这是在 Facebook 上共享链接时填充的默认信息的来源。 再次阅读手册。如果您想要 Insights，转到此页面。
在 Google Analytics 上查看这些数据 只有傻瓜才会相信 Facebook 会允许将 Insights 导出到 Google Analytics。 Google Analytics 和 Facebook Insights 不可互换。如果您想跟踪您的网页，请使用前者，如果您想跟踪您的 Facebook 页面，请使用后者。
基于部分进行另一级别的分析 Facebook 不提供跟踪用户在每个标签上停留的时间和数量的服务。
查看来自“点赞按钮”与复制/过去的流量Facebook Insights。对我有用！
如果我这样做，我能否确保 FB 分析上没有重复的项目 查询字符串将被视为单独的页面，就像没有查询字符串的同一页面一样。对于我的网站
?id=32和?id=92被视为不同的页面。那是我的在线流媒体广播网站。每个查询字符串显示一首不同的歌曲。 您可以自己解决查询字符串问题。更新！ 规范网址可以解决这个问题。
如果您以易于理解的方式表达了您的问题，您的问题现在就会得到解答；而不必在 Twitter 上要求我回答。
结局！
You're asking too many questions at once. I'm going to break it down.
access stats from the facebook insight for a specific url + for the all website. Wrong! The Open Graph protocol is designed to give Facebook and other websites semantic information of the type of content on your website, and what it is. That's where the default information populated when sharing links on Facebook is taken from. Read the manual again. If you want Insights, go to this page.
See these data on google analytics Only a fool would believe that Facebook would allow Insights to be exported to Google Analytics. Google Analytics and Facebook Insights are not interchangable. If you want to track your webpages, use the former, to track your Facebook Page, use the latter.
Have another level of analytics based on section Facebook doesn't provide services to track how long and how much users are on each tab.
See what traffic coming from "like button" vs copy/past Facebook Insights. Works for me!
If I do so, could I be sure to not have duplicate item on the FB analytics Query strings are treat as separate pages as the same page without a query string. For my website
?id=32and?id=92are treat as different pages. That was for my online streaming radio site. Each query string showed a different song. You can sort the query string problem out yourself.Update! Canonical url's can solve that problem.
If you had phrased your question in an understandable way, you would have your question answered by now; instead of having to ask me on Twitter to answer it.
The End!