view release on metacpan or  search on metacpan

articles/102.html  view on Meta::CPAN

<br />
<br />
<b>What should I know about Google proxies and flagged clicks?</b><br />
<br />
A proxy acts as an intermediary for requests from web browsers, and Google has lots of proxies they use in conjunction with various Google services &hellip;<br />
<br />
&hellip; including but not limited to Data Compression for mobile Chrome users, Google website previews, Google Translate, and Google Mobilizer just to name a few.<br />
<br />
Here&rsquo;s what you need to know about Google proxies and ClickMagick&rsquo;s auditing system &hellip;<br />
<br />
Any time an end-user&rsquo;s request is routed through Google&rsquo;s proxies for any reason, Google adds an &ldquo;X-Forwarded-For&rdquo; header to the HTTP request which contains the user&rsquo;s actual IP address.<br />
<br />
This allows ClickMagick to grab the user&rsquo;s actual IP address and process the click correctly, even though the request came from one of Google&rsquo;s proxy servers.<br />
<br />
On the other hand, if a Google proxy request does not contain a valid &ldquo;X-Forwarded-For&rdquo; header that means the request did not come from a real user, but rather it came from one of Google&rsquo;s automated systems i.e. a &ldquo;bot.&rdquo;...
<br />
You can identify these requests in your ClickMagick logs because the hostname for such a request will always start with &ldquo;google-proxy.&rdquo;<br />
<br />
If you want us to take a look at a particular flagged IP, please report the details to us as outlined below.<br />
<br />
<br />
<b>Why can&rsquo;t I redirect flagged clicks somewhere else?</b><br />
<br />
Some of our users who sell &ldquo;solo ads&rdquo; have asked us to add the ability to redirect flagged clicks to a separate URL, because they are generally obsessed with maximizing the value of each and every click.<br />
<br />