Re: Upgraded URL - URL_NOT_EQUIVALENT error although they should be

[Udo Gröbner]

Seems there is some sort of auto-decoding encoded {} ... yes, it's most 
likely an error in the URL to have encoded value track parameters, but that 
happens ...
When I substitute %7B and %7D by { and }, there's no URL_NOT_EQUIVALENT 
error any longer.

On Wednesday, May 6, 2015 at 1:53:00 PM UTC+2, Udo Gröbner wrote:
>
> Hi,
>
> we're currently preparing for the "upgraded url" migration for search 
> campaigns.
> As far as I understand it, this is what you have to do:
>
> Given
>
> http://tracking.server.com/tracker?param1={creative}&param2={network}&redirecturl=http%3A%2F%2Fwww.buystuff.com%2Fcatalogsearch%2Fresult%2F%3Fq%3Dthings%2520SN2%26adword%3Dgoogle%252FkampX%252F%257Bkeyword%257D
>  
> <http://tracking.server.com/tracker?param1=%7Bcreative%7D&param2=%7Bnetwork%7D&redirecturl=http%3A%2F%2Fwww.buystuff.com%2Fcatalogsearch%2Fresult%2F%3Fq%3Dthings%2520SN2%26adword%3Dgoogle%252FkampX%252F%257Bkeyword%257D>
> as initial destination url of an ad, the corresponding tracking template 
> should be
>
> http://tracking.server.com/tracker?param1={creative}&param2={network}&redirecturl={lpurl}
> and the final url for the ad would be
>
> http://www.buystuff.com/catalogsearch/result/?q=things%20SN2&adword=google%2FkampX%2F%7Bkeyword%7D
>
> The API upgrade process works for some ads, but doesn't for others.
> What I've found out so far:
> it works if i change the original destination url before the upgrading 
> process to correspond to final url 
> http://www.buystuff.com/catalogsearch/result/?q=things
> but doesn't work for the original destination url 
> http://www.buystuff.com/catalogsearch/result/?q=things%20SN2&adword=google%2FkampX%2F%7Bkeyword%7D
>
> Is that correct and intended?
>
> I don't understand though, why this would trigger a URL_NOT_EQUIVALENT 
> error. There have been parameters before and the same parameters 
> afterwards...
> Do you have some more information on this subject?
>
> Many thanks in advance!
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+unsubscr...@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+unsubscr...@googlegroups.com.
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/a434fd29-5038-4e05-81f8-7884cab321bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.