Forum Moderators: martinibuster
Has anybody tried it/one? If so I have some questions:
- does it really work?
- does what it do violate the AdSense TOS?
- how is it on server load?
The package I saw was almost $200 so I'm trying to get some info before I spring for it.
Thanks.
One common thread in the discussions was encoding a web page or some part thereof. If that's what you're talking about, I THINK Google would be okay with it but overall the cure sounds worse than the disease, and I'm not sure it would work anyway.
Hmm, a server side program that overrides a client side application?...
Was thinking the same thing.
$200 is an awful lot of dosh for something where info on its performance, how it works & with no recommendations for its use, seems it might be easier to find these WMD in IRAQ ;)
Put your $200 back in your pocket, if there is a problem i am sure the Adsense Team are aware of it and will be working with the Vendor in getting it resolved.
Maybe ASA can shed some light on this problem, which i thought had been cleared up anyway.
So am I misinterpreting something? What do you have to have installed to have the ads blocked?
added: The only thing that I've actually noticed Norton blocked are some of the dynamic media links from one of the affiliate networks.
Hmm, a server side program that overrides a client side application?...
Well, kind of, yes. I assume that Norton is blocking the AdSense googlesyndication host. If that's the case, then instead of the AdSense code, you could put in something that just goes out and pulls the JavaScript with appropriate arguments, and displays what you get.
In other words, instead of having the AdSense code, you'd use a URL to the CGI script (or whatever) on your own server, and it would act as sort of a "buffer" between Norton and AdSense.
If Norton is just blocking the AdSense host, it would be possible to write a little script that acts as a browser for the purpose of AdSense, and have it display the ads. (If you can get to the actual AdSense ad source HTML by doing View Source in your browser (which you can), then you can get there with a script as well, and just display the HTML instead of the Google URL.) If Norton is also blocking clicks, then you could also have the script replace [google...] with something on your site that the script redirects to.
I think there are a lot of ways that a server-side deal could get around a client-side ad blocker, mostly by fooling the ad blocker by appearing to be something other than ads.
HOWEVER, I do think that this would be WAY against the AdSense TOS.
Just an interesting thing to think about, tho'. :-)
JK
In other words, instead of having the AdSense code, you'd use a URL to the CGI script (or whatever) on your own server, and it would act as sort of a "buffer" between Norton and AdSense.
This is definately against the TOS, since I have done it. The thing is, because of the fact that you use a URL to include the Adsense banner, the banner will be requested server side. Therefore Google looks at it as if it is the same user looking at it again and again and again. With the normal javascript version, the request comes from the client side...
I tried this in order to track clicks etc. I was succesfull except for the IP thing I just explained...
It is up to the advertisers to choose a decent URL to point to.
When I use Google or view adsense ads, I often get about half of them blocked. The other half work fine. It's all down to the URL that they point to...
Norton will always be competing against software like this and also the ad suppliers.
G wants the ads to be displayed as much as the publishers do, so I see little point in spending $200 for something that may be defeated in the next NIS or NAV update.