Jump to content

The Town Dish

Approved members
  • Content Count

    1
  • Joined

  • Last visited

  1. We are using Revive Adserver to deliver ads on our site using the single page call technique. We are also using a lead generation plugin on our site called Leadin that tracks visitor behavior on the site and shows a popup to offer a mailing list signup. I'm having a problem that is derived from the interaction between Leadin and Revive Adserver with URLs on our ads when Leadin adds its tracking parameters to the query string. For example, Revive Adserver will generate the following URL for an ad on our site, which works just fine: http://ads.thetowndish.com/app/www/delivery/ck.php?oaparams=2__bannerid=1056__zoneid=14__cb=dd7303011d__oadest=http%3A%2F%2Fwww.visithersheyharrisburg.org%2F There is only one query string parameter there called oaparams. Now, Leadin adds a few parameters: http://ads.thetowndish.com/app/www/delivery/ck.php?oaparams=2__bannerid=1056__zoneid=14__cb=167ef5bc50__oadest=http%3A%2F%2Fwww.visithersheyharrisburg.org%2F&__hstc=211194890.66e909c717dcfae3509a4e4a5f1af1d0.1472162590241.1473090973416.1473124673060.25&__hssc=211194890.5.1473124673060&__hsfp=3145843587 That's three new parameters added: __hstc, __hssc, and __hsfp. These additional parameters are correctly separated by the ampersand character, and so should not cause an issue with Revive Adserver. However, when clicking the link, Revive Adserver ends up redirecting to this URL: http://www.visithersheyharrisburg.org/%26__hstc%3d211194890.66e909c717dcfae3509a4e4a5f1af1d0.1472162590241.1473090973416.1473124673060.25%26__hssc%3d211194890.5.1473124673060%26__hsfp%3d3145843587/?__hstc=211194890.66e909c717dcfae3509a4e4a5f1af1d0.1472162590241.1473090973416.1473124673060.25&__hssc=211194890.5.1473124673060&__hsfp=3145843587 Those additional query params are still there, though they should have been thrown out. Seems like Revive Adserver is just pulling everything after oaparams in the query string and assuming that it all should be processed together instead of just pulling out the oaparams value up to the ampersand the preceeds the next query argument. This seems like a URL parsing bug to me. Can anyone validate my assumptions?
×
×
  • Create New...