Wednesday, January 23rd, 2008
Today something exciting happened to me. Google replied to an email I sent them. Not only did they reply, but the response I got was exactly what I was looking for – you see, they read my question, and actually answered it!
This is a first for me, as the first response I always get is some auto-generated form response that doesn’t come close to addressing the original question. After several days of email tag, the question is eventually answered.
The problem with this response I got was that it isn’t really the answer I was hoping for.
We all know that Google does not allow the same keyword to be live in more than one AdGroup or Campaign. This is common sense because if they did, you could essentially have multiple ads appearing at the same time under the same search.
But what happens if you throw in the wrench of having each of these unique campaigns target different geographic areas? In my mind this should work – unsure I thought I would check with Google before putting in the time to set everything up.
“I may be setting up a new account in the coming weeks that will target 12 different geographic locations.
Essentially I will be creating 12 campaigns, one for each specific geographic location. The Ads will all be similar, with the main differences being the geographic location mentioned in the ad. Each of the 12 campaigns and their corresponding AdGroups will target the same Keyword set.
Will this work?”
“…As you are aware if you have the same keywords across multiple campaigns, in
this case twelve, only one ad (the better performing one) from the twelve campaigns will show. Hence, setting twelve campaigns each with a unique geographical location and having the same keywords will not be feasible…”
In short, it won’t work. Perhaps this little adjustment to the AdWords system would make perfect sense, and may even happen some day – but I’m not holding my breath. I will happily give credit where credit is due – Thank you Genevieve for actually reading my question and answering it without simply pulling a response from your database.