This may seem dumb....but, instead of going through all that trouble wouldn't it be just better to limit the Yahoo Ads to those who have US English. I mean, the odds are someone who has US English would most probably lives in US.
I am using maxmind's apache mod_geoip which resolves 10k+ IPs per second on a dual proc server
I'm sure maxmind is upto date and high performance but we have to pay for it. If you have a high traffic site , its worth it but otherwise?
how good is the solution of using US-English to find US users..!
there are a ton of ip db's around
maxmind is a good one, there is also ip-to-country which I have used.
I don't think targetting US-English is a good way. I think I would identify as US english and I am in canada
geo ip solutions are solid and in my experience I have had no false positives though I know there are a couple ranges that are funky.
>> but we have to pay for it
but shouldn't the YPN cheque cover ;)
the most important thing with geoip is to have up to date records, and you should really use a database
well the issue here is more than paying for getting solutions like MAxmind. Its setting these things up thats time consuming and not easy for beginners.
I mean i sat down today and installed phpadsnew and was going through their 75 page manual for admins. Its too long and tedious. And they want u to download wget and install it, set up schedulers and do this and do that - I finally gave up.
If its something simple like write couple of lines of code to check the US-En, its easy.
Back to your point about how US-EN would even qualify you as US traffic.
Keeping in mind that YPN allows minimal international traffic, would it be acceptable to say that users who pass the US-EN test and do not belong to US would be minimum?
Could you sticky me the URL of the script you found? I'd really like to take a look at it.
Just sent it to u - let me know what u think of it
To ALL - sorry did'nt know we cud not post URL's on the forum.
I serve ads based upon browser language headers. I log any hit that isn't en/en-us. Most of the hits are bots, followed by browsers with malformed headers that do not include a language, followed by non-us/non-English browsers. But these only account for a very small portion of the total hits. I also track the ip and language headers of browsers that click on the ads. Overall, I find it's a fast, easy to implement solution, that is surprisingly accurate. By the way, most Canadians show up as en-ca or ca.
Sure, a US visitor traveling abroad will be served an ad but that isn't necessarily a bad thing. Geotargeting by ip has it's drawbacks too. I have seen many examples of US based proxy ips showing language headers other than English and I would be very surprised if the ppc services didn't use this same header info for their click algorithms.
One thing I don't think is debatable. Any solution with the potential to curb the rate of click throughs from International traffic is better than no solution at all.
Ugh! So lame. I am still baffled that YAHOO doesn't implement the country detection. It's completely within their ability to do, rather than makin EVERY publisher do it. *sigh* Thankfully MOST (95%+) of my traffic is US, so I'm not worrying too much about it, but I still think it's lame they don't handle it themself.
|Sure, a US visitor traveling abroad will be served an ad but that isn't necessarily a bad thing. |
Except that you would be violating the Terms and conditions for doing so. After all, you agreed not to
|display all or part of the Ad Unit to any user located outside the US; |
|One thing I don't think is debatable. Any solution with the potential to curb the rate of click throughs from International traffic is better than no solution at all. |
The thing is though, the TOS doesn't mention anything about minimizing international traffic. It clearly states that any international traffic violates the TOS.
|geo ip solutions are solid and in my experience I have had no false positives though I know there are a couple ranges that are funky [emphasis added]. |
|The thing is though, the TOS doesn't mention anything about minimizing international traffic. It clearly states that any international traffic violates the TOS. |
There is no perfect technology to block absolutely all foreign traffic. We must conclude that in all likelihood, every YPN publisher is in technical violation of this provision of the TOS at one time or another.
I agree that Yahoo has the means to detect and disregard foreign traffic at their end, but they choose not to do so.
I think that this TOS provision exists partly as a handy, easy excuse for Yahoo to ban any publisher that they don't like for whatever reason.
|I think that this TOS provision exists partly as a handy, easy excuse for Yahoo to ban any publisher that they don't like for whatever reason. |
.. and I believe partly that you're correct.
You said the right thing:
"I think that this TOS provision exists partly as a handy, easy excuse for Yahoo to ban any publisher that they don't like for whatever reason. "
Thats exactly what it is. A friend of mine who is also a YPN publisher spoke to a rep some time back in November about this issue and all he had to say is
"If you have a LOT of international traffic, then your account MIGHT be terminated"
There are two things to note here. One he says "Lot" and the other "MIGHT".
So like Berto said - whenever they dont like a publisher - they'll have ur account terminated.
It would be nice to know how much money IQBAL was making when his account was terminated. :) - might give us a hint of the actual reason :)
sarah can you please sticky me for the php script as well. I need to block the 3% international traffic I have on one of my sites.