在服务器端代码中将引荐来源网址传递给omnature
我正在尝试在服务器端实现一些全方位请求。我已经设置了呼叫，并且请求发送到omnature，但是引荐来源网址没有显示在omnature 中。
下面是我的代码创建的 Omniture 网址之一的示例。我错过了什么吗？
http://[id].112.2o7.net/b/ss/[group]/1/H23.2/s1328206514850?AQB=1&ndh=1&ns=[id]&g=http%3A% 2楼%2 F[域名]%2Flogin.asp&vid=1328206514850&pageName=Login%20Page%20!test!&r=http%3A%2F%2Ftest.com
I'm trying to implement some omniture requests on server-side. I've got the calls set up, and the requests make it to omniture, but the referrer is not showing up in omniture.
Here is an example of one of the urls for omniture my code creates. Am I missing something?
http://[id].112.2o7.net/b/ss/[group]/1/H23.2/s1328206514850?AQB=1&ndh=1&ns=[id]&g=http%3A%2F%2F[domain]%2Flogin.asp&vid=1328206514850&pageName=Login%20Page%20!test!&r=http%3A%2F%2Ftest.com
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
报表包管理控制台中的内部 URL 过滤器指定您的内部域（即您的域）。来自任何其他域的任何引用都将被视为引用者。
我通常使用 WATS 之类的 Firefox 插件来调试特定页面上的变量，包括引用者。
请记住，需要来自外部网站的推荐。如果您只是输入 URL、重新加载或从您自己的网站点击，则不会有推荐。测试此功能时，我将在另一个域（例如本地主机）上创建一个页面，并创建指向我的页面的链接。
https://omniture-help.custhelp .com/app/answers/detail/a_id/1652/kw/JavaScript/lated/1
比较：s.linkInternalFilters 与内部 URL 过滤器
s.linkInternalFilters：s_code.js 文件中的 linkInternalFilters 变量用于退出链接跟踪。如果 s.trackExternalLinks 设置为 true，则用于确定访问者单击的特定链接是否是您组织网站的内部链接。与 s.linkInternalFilters 中的值匹配的单击链接将被忽略，而与任何值不匹配的链接将作为退出链接发送到 SiteCatalyst。
内部 URL 过滤器：管理控制台中的内部 URL 过滤器用于流量来源报告，例如引用域报告。每个 st() 请求都会检查引用 URL（包含在引用变量中）是否与设置的任何规则匹配。与任何这些规则匹配的引荐 URL 将从所有流量来源报告中排除，而不包含的引荐 URL 则包含在内。
建议 s.linkInternalFilters 和内部 URL 过滤器相互匹配，但是两者完全独立运行并提供完全不同的功能。
The Internal URL Filters in the Report Suite Admin Console specifies what your internal domains are (i.e your domains). Any referal from any other domain will be recognised as a referrer.
I generally use a Firefox addon like WATS to debug the variables that are on a particular page, including referrer.
Keep in mind that there needs to be a referral from an external site. If you just type in the URL, or reload, or click from your own site, there is no referral. When testing this, I would create a page on another domain (e.g. localhost), and create a link to my page.
https://omniture-help.custhelp.com/app/answers/detail/a_id/1652/kw/JavaScript/related/1
COMPARISON: s.linkInternalFilters vs. Internal URL Filters
s.linkInternalFilters: The linkInternalFilters variable within the s_code.js file is used in exit link tracking. If s.trackExternalLinks is set to true, it is used to determine if a specific link a visitor clicked on is internal to your organization's site or not. Clicked links that match a value in s.linkInternalFilters are ignored, while links that do not match any values are sent to SiteCatalyst as an exit link.
Internal URL Filters: The Internal URL filters within the Admin Console is used in Traffic Sources reports, such as the Referring Domain report. Every s.t() request checks to see if the referring URL (contained within the referrer variable) matches any of the rules set up. Referring URLs that match any of these rules are excluded from all Traffic Sources reports, while referring URLs that do not are included.
It is recommended that s.linkInternalFilters and Internal URL filters match eachother, however the two operate completely independently and serve completely different functions.
该图像的最后一部分是引用值 r= 。这是正确的值吗？此外，您还应该在管理控制台中检查该报表包的内部 URL 过滤器。通常，对于新的报表包，您会发现 的值。 （单个时期）设置在那里。如果您确实有，则不会记录任何推荐人。
The last part of that image is the referrer value, r= . Is that the correct value? Also you should check your Internal URL Filters in the admin console for that report suite. Typically for new report suites you will find the value of . (a single period) set in there. If you do have that then no referrers will be recorded.