I work for such a company, and I'm afraid this kind of proprietary information is considered extremely sensitive. AFAIK there are no public standards, and the bulk of the documentation available is as required for user implementation only.
There may be some white papers out there, probably from academia, but it's possible google may have benevolently published something.
If you conform to these guidelines, you can ask IAB to approve your ad server. Once approved, advertisers and publishers should trust the numbers being generated through your reports.
They have specs on some commonly agreed-upon things like ad-banner formats. They seem to deal mostly in business issues and less on the technical/implementation specifics.
The simplest implementation is simply pointing to an image from another server. That server will identify on which site the advertisement is being displayed (from the 'Referer' header, or from an id or token passed with the image request). Then the image is returned and the pageview is recorded. If the viewer clicks on the ad, a link also pointing back to the ad server will record a 'clickthrough' and then forward the request on to the advertiser.
The database might look like this (drasticly oversimplified, for example only):
When a user viewed the page, the request for the image would go to the ad-server. The ad-server would look up the request, select an advertisement to show (many proprietary algorithms here), record the request, and finally return the response.
Now the image is loaded and shown on the page. If the user decides to click on it, again the request goes to the ad server which records the click and finally redirects the request to the page being advertised.
GET /ads/click?id=1
301 Moved Permanently
Location: http://mycoolsite.com
发布评论
评论（3）
我在这样的公司工作，恐怕这种专有信息被认为是极其敏感的。 据我所知，没有公共标准，并且大部分可用文档仅是用户实施所需的。
可能有一些白皮书，可能来自学术界，但谷歌可能已经仁慈地发表了一些东西。
I work for such a company, and I'm afraid this kind of proprietary information is considered extremely sensitive. AFAIK there are no public standards, and the bulk of the documentation available is as required for user implementation only.
There may be some white papers out there, probably from academia, but it's possible google may have benevolently published something.
实际上，对于如何衡量展示次数、点击次数、转化次数、富媒体事件等，有一些非常具体的指南。这些指南可以在以下网址找到：http://www.iab.net/iab_products_and_industry_services/508676/guidelines
如果您遵守这些准则，您可以要求 IAB 批准您的广告服务器。 一旦获得批准，广告商和发布商应该信任通过您的报告生成的数字。
There are actually some very specific guidelines for how to measure things like impressions, clicks, conversions, Rich Media Events, etc. These guidelines can be found at the following url: http://www.iab.net/iab_products_and_industry_services/508676/guidelines
If you conform to these guidelines, you can ask IAB to approve your ad server. Once approved, advertisers and publishers should trust the numbers being generated through your reports.
查看IAB（互动广告局）
他们对一些共同商定的事情有规范，例如广告-横幅格式。 他们似乎主要处理业务问题，较少处理技术/实施细节。
最简单的实现就是简单地指向来自另一台服务器的图像。 该服务器将识别广告正在哪个站点上显示（来自“Referer”标头，或者来自与图像请求一起传递的 ID 或令牌）。 然后返回图像并记录浏览量。 如果观看者点击广告，也指向广告服务器的链接将记录“点击”，然后将请求转发给广告商。
数据库可能看起来像这样（过于简单化，仅作为示例）：
Pages +---------+----------------+ | page_id | name | +---------+----------------+ | 1 | mycoolsite.com | +---------+----------------+ Advertisements +-----------------+------------------+--------------------------------+ |advertisement_id | image_name | target_url | +-----------------+------------------+--------------------------------+ | 1 | banner1_468.png | http://new-amazing-product.com | +-----------------+------------------+--------------------------------+ Activity +--------------+--------------------+--------+--------+ | page_id | advertisement_id | views | clicks | +--------------+--------------------+--------+--------+ | 1 | 1 | 0 | 0 | +--------------+--------------------+--------+--------+在将显示添加的页面中，您可以将其放入 html 中：
当用户查看页面时，对图像的请求将转到广告 -服务器。 广告服务器将查找请求，选择要显示的广告（这里有许多专有算法），记录请求，最后返回响应。
Activity +--------------+--------------------+--------+--------+ | page_id | advertisement_id | views | clicks | +--------------+--------------------+--------+--------+ | 1 | 1 | * 1 * | 0 | +--------------+--------------------+--------+--------+响应可能包含以下内容（从数据库检索）：
现在图像已加载并显示在页面上。 如果用户决定点击它，请求会再次发送到广告服务器，广告服务器记录点击并最终将请求重定向到正在广告的页面。
GET /ads/click?id=1 301 Moved Permanently Location: http://mycoolsite.comActvity +--------------+--------------------+--------+--------+ | page_id | advertisement_id | views | clicks | +--------------+--------------------+--------+--------+ | 1 | 1 | 1 | * 1 * | +--------------+--------------------+--------+--------+Check out the IAB (Interactive Advertising Bureau)
They have specs on some commonly agreed-upon things like ad-banner formats. They seem to deal mostly in business issues and less on the technical/implementation specifics.
The simplest implementation is simply pointing to an image from another server. That server will identify on which site the advertisement is being displayed (from the 'Referer' header, or from an id or token passed with the image request). Then the image is returned and the pageview is recorded. If the viewer clicks on the ad, a link also pointing back to the ad server will record a 'clickthrough' and then forward the request on to the advertiser.
The database might look like this (drasticly oversimplified, for example only):
Pages +---------+----------------+ | page_id | name | +---------+----------------+ | 1 | mycoolsite.com | +---------+----------------+ Advertisements +-----------------+------------------+--------------------------------+ |advertisement_id | image_name | target_url | +-----------------+------------------+--------------------------------+ | 1 | banner1_468.png | http://new-amazing-product.com | +-----------------+------------------+--------------------------------+ Activity +--------------+--------------------+--------+--------+ | page_id | advertisement_id | views | clicks | +--------------+--------------------+--------+--------+ | 1 | 1 | 0 | 0 | +--------------+--------------------+--------+--------+In the page which will display the add you'd put this in the html:
When a user viewed the page, the request for the image would go to the ad-server. The ad-server would look up the request, select an advertisement to show (many proprietary algorithms here), record the request, and finally return the response.
Activity +--------------+--------------------+--------+--------+ | page_id | advertisement_id | views | clicks | +--------------+--------------------+--------+--------+ | 1 | 1 | * 1 * | 0 | +--------------+--------------------+--------+--------+The response could contain the following (retreived from the database):
Now the image is loaded and shown on the page. If the user decides to click on it, again the request goes to the ad server which records the click and finally redirects the request to the page being advertised.
GET /ads/click?id=1 301 Moved Permanently Location: http://mycoolsite.comActvity +--------------+--------------------+--------+--------+ | page_id | advertisement_id | views | clicks | +--------------+--------------------+--------+--------+ | 1 | 1 | 1 | * 1 * | +--------------+--------------------+--------+--------+