Re: Percent Encoding of Custom Parameters

Hello Dorian,

Sorry for the delay.

Could you please share your tracking template too, apart from the final URL and custom parameters in the below image?

Thanks in advance.

Best,

Thanet, AdWords API Team

On Thursday, May 12, 2016 at 9:43:11 PM UTC+9, Dorian Kind wrote:

Hi Thanet,

I'm not sure if that's correct. To me it seems that there's clearly some percent-encoding going on:

Or am I misunderstanding you?

Thanks & cheers,

Dorian

On Thursday, May 12, 2016 at 8:03:28 AM UTC+2, Thanet Knack Praneenararat (AdWords API Team) wrote:

Hi Dorian,

For custom parameters, if they're used in a final URL and the final URL is used in tracking template then they're escaped with final URL 

So the list of escaped char depends on if {lpurl} or {escapedlpurl} is used.

If they're used directly in the tracking template, they're not escaped.

Best,

Thanet, AdWords API Team

On Wednesday, May 11, 2016 at 1:55:01 AM UTC+9, Dorian Kind wrote:

Hi Shwetha,

thanks for your quick reply. I'm afraid the ValueTrack documentation isn't of much help, though. What I'm observing is that custom parameters are neither being handled "as per standard URL specifications" (as not all reserved characters are escaped) nor does the escaping for {lpurl} apply (as the character { is being percent-encoded, for example).

Actually we're just going to do all URL-encoding on our end so it's not really relevant, but I'm still curious about what the exact behavior is.

Cheers,

Dorian

On Tuesday, May 10, 2016 at 6:45:47 PM UTC+2, Shwetha Vastrad (AdWords API Team) wrote:

Hi Dorian,

You can use this document as a reference for ValueTrack parameters. The characters which are escaped depends on what variant of the ValueTrack parameter you are using. For example, the {lpurl} is the landing page url escaped as per standard URL specifications. The characters being escaped also depends on the position of the parameter in the tracking template. If {lpurl} is not at the beginning of your tracking template, it escapes the single quote character along with the characters ?,=,",#,\t, and [space]. 

I hope this helps. 

Regards,

Shwetha, AdWords API Team.

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscribe@googlegroups.com
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 adwords-api+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/96276c5c-771e-426c-a0f2-59c03a73bf57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.