{"id":120,"date":"2010-07-29T10:13:27","date_gmt":"2010-07-30T03:13:27","guid":{"rendered":"http:\/\/www.searchforecast.com\/blog\/2010\/07\/29\/searchforecast-de-anonymizes-urls-in-googles-content-network-with-disruptive-technology\/"},"modified":"2010-07-29T11:09:58","modified_gmt":"2010-07-30T04:09:58","slug":"searchforecast-de-anonymizes-urls-in-googles-content-network-with-disruptive-technology","status":"publish","type":"post","link":"https:\/\/www.searchforecast.com\/blog\/searchforecast-de-anonymizes-urls-in-googles-content-network-with-disruptive-technology\/","title":{"rendered":"SearchForecast de-anonymizes URLs in Google&#8217;s Content Network with disruptive technology"},"content":{"rendered":"<p>I&#8217;ve been updating the senior management of the major ad networks today that SearchForecast has been &#8220;de-anonymizing&#8221; the anonymous URLs Google show on their &#8216;placement targeting&#8217; within Adwords for advertisers who spend money on their Content Network.<\/p>\n<p>As pictured here, we are providing to media buyers and advertisers a list of URLs which we believe are those URLs which Google run the ads on across their Content Display Network and 3rd party networks via the exchanges.<\/p>\n<p><a href=\"https:\/\/www.searchforecast.com\/blog\/wp-content\/uploads\/2010\/07\/picture-36.png\" title=\"picture-36.png\"><img src=\"https:\/\/www.searchforecast.com\/blog\/wp-content\/uploads\/2010\/07\/picture-36.png\" alt=\"picture-36.png\" \/><\/a><\/p>\n<p>For those technically minded, our &#8220;de-anonymizing&#8221; process includes the following:<\/p>\n<p>1. The first method is to basically match the numbers in the PubID string. So if for example the Pub ID is 5ca654dd9821cb84, we check for the following sequence numbers in our <a href=\"http:\/\/www.searchforecast.com\/adsense_directory_index.php\" title=\"AdSense Directory\">adsense database<\/a>:<\/p>\n<p>1.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 654 \u2013 how many id\u2019s match this number<br \/>\n2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 9821 \u2013 how many id\u2019s match this number<br \/>\n3.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 84 \u2013 how many id\u2019s contain this number<br \/>\n4.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 654 and 9821 \u2013 how many id\u2019s contain 654 and 9821<br \/>\n5.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 654 and 84 \u2013 how many id\u2019s contain 654 and 84<br \/>\n6.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 9821 and 84 \u2013 how many id\u2019s contain both these combinations<br \/>\n7.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 654, 9821 &amp; 84 \u2013 how many id\u2019s contain all of these combinations<\/p>\n<p>2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 The second method is to use a standard bit encryption on our database of adsense id\u2019s. So for example if the id is 654981, we run an encryption code sequence of 16 bit upon it. This gives us a alphanumeric character string of 16 characters. We then use the same code we used in the above example to run a combination.<\/p>\n<p>3.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 The third method is to do the same with an advanced bit encryption sequence<br \/>\n4.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Fourth method is to use an proprietary encryption sequence.<\/p>\n<p>The simple fact is that advertisers are spending with Google and don&#8217;t know where their dollars are being spent. Lack of transparency leads to market inefficiency affecting advertisers and agencies. Advertisers and large media buyers are welcome to contact us for further information on how we can provide more transparency when advertising across the Google Content Network.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve been updating the senior management of the major ad networks today that SearchForecast has been &#8220;de-anonymizing&#8221; the anonymous URLs Google show on their &#8216;placement targeting&#8217; within Adwords for advertisers who spend money on their Content Network. As pictured here, &hellip; <a href=\"https:\/\/www.searchforecast.com\/blog\/searchforecast-de-anonymizes-urls-in-googles-content-network-with-disruptive-technology\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[],"tags":[],"_links":{"self":[{"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/posts\/120"}],"collection":[{"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/comments?post=120"}],"version-history":[{"count":0,"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/posts\/120\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/media?parent=120"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/categories?post=120"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.searchforecast.com\/blog\/wp-json\/wp\/v2\/tags?post=120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}