Hi Anash,
many thanks for your comprehensive answer! One follow-up question: Based on
your examples I take it that there is no longer a ValueTrack parameter
which only encodes the query string of the final URL—like {lpurl} used to
do for Dynamic Search ads. Ex.
trackingTemplate: tracker.example.com?url={old_behavior_of_lpurl},
finalUrl1 = http://www.example.com?foo=bar
Serving URL = tracker.example.com?url=http://www.example.com%3Ffoo%3Dbar
Is it correct that this escaping behavior is no longer available?
I'm asking because I seem to remember that there were a few third-party
tracking setups that required the destination URL to be encoded like this.
But maybe these tools were adjusted in the meantime.
Thanks again & best regards,
Dorian
On Thursday, May 21, 2015 at 7:24:20 PM UTC+2, Anash P. Oommen (AdWords API
Team) wrote:
>
> Hi Dorian,
>
> TL;DR; don't use {escapedlpurl}, use {lpurl} instead.
>
> The longer answer is that {escapedlpurl} works exactly like {lpurl},
> except when used at the beginning of the url. {lpurl} works fine in this
> case, whereas {escapedlpurl} would break the serving URL. This is because
> {lpurl} escapes the URL while keeping the validity of serving URL in mind,
> whereas {escapedlpurl} always escapes the URL completely, thus breaking the
> URL in some cases if it appears at the beginning.
>
> E.g. consider the following setup:
>
> (1) Param within a URL
>
> (a) trackingTemplate: tracker.example.com?url={lpurl}
> <http://tracker.example.com?url=%7Blpurl%7D>, finalUrl1 =
> http://www.example.com?foo=bar
> Serving URL1 =
> tracker.example.com?url=http%3A%2F%2Fwww.example.com%3Ffoo%3Dbar
> (b) trackingTemplate: tracker.example.com?url={escapedlpurl}
> <http://tracker.example.com?url=%7Bescapedlpurl%7D>, finalUrl1 =
> http://www.example.com?foo=bar
> Serving URL1 =
> tracker.example.com?url=http%3A%2F%2Fwww.example.com%3Ffoo%3Dbar
>
> (2) Param at the beginning of a URL
>
> (a) trackingTemplate: {lpurl}&trackerid={_trackerid}, finalUrl1 =
> http://www.example.com?foo=bar, trackerid = 1234
> Serving URL1 = http://www.example.com?foo=bar&trackerid=1234
> (b) trackingTemplate: {escapedlpurl}&trackerid={_trackerid}, finalUrl1 =
> http://www.example.com?foo=bar, trackerid = 1234
> Serving URL1 = http%3A%2F%2Fwww.example.com%3Ffoo%3Dbar&trackerid=1234
>
> Hope this helps?
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Wednesday, May 20, 2015 at 6:17:14 AM UTC-4, Dorian Kind wrote:
>>
>> Hello,
>>
>> while preparing for the upcoming Upgraded URLs migration, we started to
>> wonder about the difference between {lpurl} and {escapedlpurl} in
>> Tracking Templates. Previously, the two parameters would be encoded
>> differently, insofar that {lpurl} would not encode colons and slashes
>> (but some other characters like question marks), whereas {escapedlpurl}
>> would encode all reserved characters. The current documentation at
>> https://support.google.com/adwords/answer/2375447 only states that
>> {lpurl} won't be escaped at all if it's located at the beginning of the
>> tracking template. Can you confirm that {lpurl} and {escapedlpurl} are
>> still encoded differently (and if so, maybe update the documentation)?
>>
>> Thanks for any feedback and best regards,
>> Dorian
>>
>> PS. I realize this is not strictly an API-related question, however I
>> have the feeling that I am more likely to get a correct answer here than I
>> would on the Adwords product forum...
>>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5e873f1a-a106-4d36-8346-284181595903%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
