Question

Do I need to Encode the URL Parameters in Event Calls?

Answer

As a general rule, we recommend that you URL encode the event call whenever making event requests.  As an example for click data, the AAM product documentation recommends encoding the values like this:

http://client.demdex.net/event?d_event=click&d_creative=1235&d_src=203&d_campaign=4709&d_adgroup=3408&d_placement=1001&
d_rd=http%3A%2F%2Fadobe.com%2Fcallback%3Fcreative%3D%25d_creative%25%26campaign%3D%25d_campaign%25%26adgroup%3D%25
d_adgroup%25%26d_placement%3D%25placement%25%26src%3D%25d_src%25

In rare situations where the demdex event call is being embedded within another partner call, you may need to encode that string (in addition to the prior encoding done on the redirect URL) as follows:

http%3A%2F%2Fclient.demdex.net%2Fevent%3Fd_event%3Dclick%26d_creative%3D1235%26d_src%3D203%26d_campaign%3D4709%26d_adgroup%3D3408%26d_placement%3D1001%26%0D%0Ad_rd%3Dhttp%253A%252F%252Fadobe.com%252Fcallback%253Fcreative%253D%2525d_creative%2525%2526campaign%253D%2525d_campaign%2525%2526adgroup%253D%2525%0D%0Ad_adgroup%2525%2526d_placement%253D%2525placement%2525%2526src%253D%2525d_src%2525

This ensures that each phase of the URL is properly encoded, and will be decoded as the various URLs are processed and triggered.

Questo prodotto è concesso in licenza in base alla licenza di Attribuzione-Non commerciale-Condividi allo stesso modo 3.0 Unported di Creative Commons.  I post su Twitter™ e Facebook non sono coperti dai termini di Creative Commons.

Note legali   |   Informativa sulla privacy online