Forum Moderators: buckworks & skibum

Message Too Old, No Replies

How to parse keywords into destination URL

         

skuba

12:01 am on Jan 26, 2005 (gmt 0)

10+ Year Member Top Contributors Of The Month



I am not sure how to parse the searched keywords in the destination URL of an ad.
Isn't it by placing {keywords} in the URL?

I wanted to do something like [example.com...] and then google would automatically ad the keywords there.

Does this work?

Will it work for the ads displayed on content network sites?

Thanks

[edited by: eWhisper at 5:48 am (utc) on Jan. 26, 2005]
[edit reason] Please use example.com for sample links. [/edit]

poster_boy

7:07 am on Jan 26, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You may use dynamic keyword insertion within an ad group's default URL (not keyword specific URLs) just as you would in the creative - same format, i.e. {Keyword}

inasisi

3:32 pm on Jan 26, 2005 (gmt 0)

10+ Year Member



I have 3 questions with regards to using dynamic keyword insertion in the actual URL of an ad.

  • How does it work for content clicks? As I understand content ads are triggered by the combination of keywords in the adgroup and not one particular keyword? Do we need to give a default value for this, just like how we do it when inserting it into the ad copy.[/li]

  • Would it be able distinguish between exact match, phrase match and broad match. I tend to add all 3 versions of a keyword to my adgroup but I would love to find the ROI of them individually. Overture has the feature of letting us know which particular match was used through their Tracking URL capability. A side question, for anyone who does track it, does the ROI vary across these 3 types or is it very similar.[/li]

  • Have there been cases of this dynamic insertion not working properly and thus not leading to the correct URL. I need to take the users to different pages based on the keyword triggering it and it is essential that I get the keyword correct. It would be worse if the apache server is not able to understand this malformed URL and throws an error[/li]
  •