Hi Dorian, AdWords allows multiple final URLs specifically for the use case where you are *not* including *lpurl* in your tracking template. For example, if your tracking template is directing traffic to a tracker that redirects some traffic to one URL and other traffic to another URL, e.g., for a landing page experiment.
If you do have multiple final URLs *and* you are using a tracking template that includes *lpurl*, AdWords will simply pass the first final URL for the *lpurl* parameter value. Also, if you have multiple final URLs and you are *not* using a tracking template at all, AdWords will simply serve the ads with the first final URL as the destination URL. Currently, the UI does not support *adding* multiple final URLs, although you can *view* additional final URLs by hovering over the callout to the right of the *Final URL* entry field, at which point you'll see an *Additional final URLs* tooltip that shows the 2..n final URLs. Regarding reports, the semicolon in your *CreativeFinalUrls* will not be escaped. However, it does appear that there will be a space following the semicolon delimiter, e.g.: "AD_PERFORMANCE_REPORT (Apr 22, 2015)" Ad ID,Final URL,Impressions 123456789,http://www.example.com/1?a;b; http://www.example.com/2?c;d,0 Cheers, Josh, AdWords API Team On Wednesday, April 22, 2015 at 11:16:56 AM UTC-4, Dorian Kind wrote: > > Hello there, > > From the API documentation we know that the final URL fields of Ad objects > ("finalUrls", "finalMobileUrls", "finalAppUrls") are lists. > > I'm having a hard time understanding how ad serving works if there are > multiple final URLs for a given ad, for example, how does Adwords choose > which final URL to use for the "lpurl" parameter? > > Additionally, is there currently any way that one can add multiple final > URLs in the web interface, or is this just possible using the API? > > And lastly, it's mentioned that in reports, values for the final URL field > for a given creative are separated by semicolons. But what if the URLs > themselves contain semicolons (for example, they can be used in place of > "&" as the item separator in query strings), are they going to be escaped? > > Thanks for your feedback and best regards, > Dorian > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/4484d623-f0e6-4f63-94f0-4e7d38f44007%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
