- From: Rigo Wenning <rigo@w3.org>
- Date: Thu, 21 Jun 2012 19:50:42 +0200
- To: public-tracking@w3.org
We took the list of permitted uses and discussed them. We have agreement on legal requirements. We tried to create a matrix with: - Frequency capping - Reporting - Security/Fraud - Product Improvement - Market Research - Debugging - Legal requirements (agreement) - Others Reporting - revenue reporting (Cost Per Click) (what makes it valuable is that I can find out if somebody came back and bought) Click converts the third party into a first party. We have also the purchase event (covered in advertiser revenue) View click, action measuring. If we can do this, that means we are able to bill people. do we need ID cookie? Brooks needs to know who the people are. - Delivery (Cost Per A) - aggregate reporting - Reach - Impression delivery Impressions: (do not need cookie/IP address) - Clicks (logging number of clicks per IP) (do not need uniqueID) - CPC - CPA (requires a cookie and a second event) Reach: - number of unique users (unique impressions) - advertiser revenue publisher revenue does not need ID-cookie collection. For measure effectiveness ROI, they need reporting and cookie. Have to measure activity to come to the conclusions CPA is related. - geo-reporting (according to IP) (is allowed with Jonathan) + targeting + real time near time reporting + long term reporting Central issue, measure of ROI for advertisers needs UI A person who saw that, bought that. Arvind: Class of things that can do the trick set a uniqueID that isn't all the time read back only on revenue event, using local storage. At this point I went to a different group
Received on Thursday, 21 June 2012 17:51:09 UTC