如何从内部广告系统跟踪转化率（点击到销售）？
我目前正在为公司客户的网站编写一个内部广告系统，其中的广告只会被内部用户看到，并且所有交易都在网站内部进行（即广告仅针对网站上的会员内容）。
有人对跟踪这些广告的转化率（即浏览量：点击量：销售量）的最佳方法有任何建议吗？
编辑
我不是在寻找“为什么不使用谷歌分析”类型的答案，我正在研究可能的架构轮廓，即“为什么不使用存储指南”暂时缓存，看看它是否与广告类型的答案相关。
/编辑
在之前的工作中，我做了一些基于内部缓存的事情，它只是做了视图：点击跟踪，但是销售率的添加使这个任务变得更加复杂，特别是如果我们考虑到认为有人可能会点击广告但不会立即购买。
干杯，艾德
（注意，我故意留下这个含糊不清的地方，是为了（希望）得到一些答案，通过从不同的角度来解决问题，从而提供我尚未想到的想法）
I am currently writing an interal advertising system for a company client's website, where the adverts will only be seen by internal users, and all transactions take place internally to the site (i.e. the adverts are for member-only content available on the site).
Does anyone have any recommendations as to the best way to track the conversion rate of these adverts (i.e. views:clicks:sales)?
EDIT
I'm not looking for a 'Why don't you use google analystics'-type answer, I'm looking into possible architecture outlines, i.e. a 'why don't use store a guid in a cache temporarily and see if it ties to the advert' kind of answer.
/EDIT
In a previous job I did something based on an internal cache, which simply did view:click tracking, however the addition of the sales rate makes this task more complex, especially if we take into account the idea that someone may click through to an advert and not purchase immediately.
Cheers, Ed
(N.B. I'm leaving this purposely vague in order to (hopefully) get some answers that provide ideas I've yet to have thought of by coming at the problem from a different angle)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
典型的方法是使用 cookie 来跟踪用户在网站上的活动，例如
用户查看广告 - 此页面上将存在一个 img 标签，该标签指向返回单个像素图像的服务器脚本。服务器脚本将检查用户计算机上是否存在 cookie，如果未找到，则为用户生成一个 GUID，并创建一个。然后保存有关印象所需的任何详细信息（IP、日期时间等），并在此 GUID
用户点击广告时进行保存。这会将用户带到一个页面，该页面会查找查看广告时创建的 cookie，存储点击的详细信息，并在用户计算机上放置一个点击 cookie，并带有标识该点击的 guid
我通常有 3 个表，每个表用于印象、点击和转化，每个表存储所需的尽可能多的数据。使用这种类型的架构，您可以按用户进行跟踪，并且还可以进行特定的查看->点击->销售
一个考虑因素是 cookie 不会 100%，因为它们可能在某些计算机上被阻止，但是您可以采取通过在会话中存储必要的指南来解决这个问题，这是首先尝试的。如果没有会话，则查找 cookie，如果没有 cookie，您可以回退到 IP 地址。如果这都是内部的，并且您确保所有跟踪都在与网站相同的域上运行，那么您应该很少遇到 cookie 问题
A typical approach would be to use cookies for tracking the users activity through the site, e.g.
User views the advert - on this page would exist an img tag which points to a server script that returns a single pixe image. The server script would check for an existing cookie on the users machine, if one isn't found then generate a GUID for the user, and create one. Then save any details required about the impression (IP, date time etc), aginst this GUID
User clicks on the advert. This would tak ethe user to a page which looks for the cookie created when the advert was viewed, stores details of the click, and drops a click cookie on the users machine, with a guid identifying the click
Transaction completed. At this point have another pixel on the page which looks for the click cookie and stores the fact that the click has converted into a sale. Would also be very simple to pass in a querystring param with a sales reference
I would typically have 3 tables, one each for impression, click and conversion, with each storing as much data as is necessary. With this type of architecture you are then able to track by user, and also specific view->click->sale
One consideration is that cookies are not going to be 100% as they maybe blocked on some machines, however you could take steps to counter that by also storing the necessary Guids in a session, which is attempted first. if there is no session then look for a cookie, and then if there is no cookie you could fallback on IP address. If this is all internal and you make sure that all of the tracking runs on the same domain as the website you should have very few problems with cookies however
我不确定它是否适合您（也许您需要一些内部开发的特定解决方案），但是使用 Google Website Optimizer，您可以创建整个场景并跟踪交易的每一步直至转换（+更多功能） 。 http://www.google.com/websiteoptimizer
I am not sure if it would work for you (maybe you need some in-house developed specific solution), but with Google Website Optimizer you can create whole scenarios and track every step of the transaction up to the conversion (+ much more features). http://www.google.com/websiteoptimizer
像素和 cookie 都非常脆弱，您最终会过度依赖浏览器正确加载数据。
我建议使用在销售事件上触发的 API。这样它“总是”有效，并且不会意外完成。您还可以更轻松地协调数据。
Pixels and cookies are both very brittle, and you end up relying too much on a browser loading data properly.
I'd suggest using an API which is triggered on a sale event. This way it "always" works, and won't be done accidently. You'll also be able to reconcile data more easily.