|If you block an IP in your web.config, and that person clicks Adwords|
| 11:21 pm on Mar 1, 2013 (gmt 0)|
If you block an IP in your web.config (which takes them to a 404), and that person clicks on one of your Adwords ads, will you be charged for that click? In other words, does Google check it's own code within your page to make sure that person actually arrived at the destination page? Thanks for your experience.
| 8:43 pm on Mar 2, 2013 (gmt 0)|
They clicked, you get charged.
You need to block their IP from serving your ads, to avoid clicks, to avoid being charged.
| 10:38 pm on Mar 2, 2013 (gmt 0)|
First, appreciate your response.
Second, sure, that would be the first and most obvious guess. But what if (theoretically) someone's destination page is down (404, whatever). Seems like the right thing for Google to do would be (if they don't already have this?) an immediate check (for their code string) on your page to ensure the destination page is as described (although not for the IPs on our web.config). I'm having to try this ridiculous workaround since we're maxed out past adwords ip exclusions--see my other related post.
I know the obvious answer (after having fine-tuned all our exclusions, which we did) would be to have Adwords increase their # of max IP exclusions to 2000 like Bing does. That makes things a lot easier on a lot of webmasters.
Any help would be appreciated.
| 8:29 pm on Mar 3, 2013 (gmt 0)|
It's a live auction, so they'd need to know the IPs that make your page dynamically 404... hence the IP entry area.
Your work around posed here, ends up needing to know the IP -before- they show the ad.
If they don't understand that it is the IP causing the 404, they'll assume it's down for many, and shut off your ads for bad landing pages. Once you tell them it's for certain IPs, they'd need to know which ones, to prevent serving your ads to people from those IPs. See, it's a circle.
| 9:04 pm on Mar 3, 2013 (gmt 0)|
Yes, I've thought of those basic things too. Well, thanks for your time.