According to a post from another site, your destination url must contain your dispaly url.
So if your display url is www.cars.com your destination url would have to be www.cars.com/affiliate to get accepted. No CB hoplinks or www.abcdef.com/click-1234567-8910112.
Someone correct me if I am wrong.
CJ
However, I think the important point here might be: "end up at" the URL. You might go through several redirects and tracking URLs first, but as long as the place you end up at matches the display URL, you're performing as advertised. From the user's perpective, the fact that you went through a qksrv or hoplink or adfarm first before you arrived at the display URL shouldn't make a difference.
So, I'm guessing a more accurate description is:
"The final destination URL, after any series of redirects, must match the display URL. "
Requiring that the display & destination URL match in the adwords interface would shoot down all kinds of tracking server approaches, including CJ but also a very big auction site.
Shak
your destination url must contain your dispaly url.
That's basically what the new auto checker does is make sure the landing page URL matches the display URL.
Shak
You'll notice when the add comes up in red that you can click a "ask for exception" button. You can then explain that the id is a tracking or affiliate id in the notes. This will then be passed on to the editors when they come to edit the account..
Jamie
thank you for the clarification, much appreciated and stops the heart attacks for the ad mgmt companies :)
Shak
can we have some clarification on this from Google?
You'll notice when the add comes up in red that you can click a "ask for exception" button. You can then explain that the id is a tracking or affiliate id in the notes. This will then be passed on to the editors when they come to edit the account..
Exactly correct, jamie_h. Thanks for your timely heart attack prevention measures.
As mentioned in another thread, the policies running underneath the 'Create Ad Interface' changes are exactly the same as they were before.
No policy changes at all.
AWA
First is this only on new ads, or is it applied to existing ads?
Second, what is the requirement? Is it just the base site url must match, or does it have to be exactly as displayed?
Say I have:
Display: www.mysite.com/red-widgets
Actual: www.mysite.com/cart.ph?redwidgets
Or Actual: www.mysite.com/cart.ph?cat=124
First is this only on new ads, or is it applied to existing ads?
This applies to any ad which is being changed!
Second, what is the requirement? Is it just the base site url must match, or does it have to be exactly as displayed?
Not sure i'm afraid..will be one for adwordsadviser
Second, what is the requirement? Is it just the base site url must match, or does it have to be exactly as displayed?
Not sure i'm afraid..will be one for adwordsadviser
Before I say a word, though, please keep in mind that this is the same old policy we're talking about here. No changes to the policy. So if you have ads which don't seem to fit the rule mentioned below, but which were approved before, they'll still be approved now - in the exception request process.)
With that said, the rule is that the Display URL and the Destination name need to be in the same domain.
(And the intent behind the rule is that users are taken to the site which they expect to be taken to, having seen the Destination URL.)
So in your example, RedWolf:
Display: www.mysite.com/red-widgetsActual: www.mysite.com/cart.ph?redwidgets
Or Actual: www.mysite.com/cart.ph?cat=124
Both of your 'actuals' above would be fine, since they're both in the same domain as your Display URL - which is 'mysite.com'.
AWA
