Display URL vs Landing URL for new Ads?

[apiapi]

I will have a need to create several dozen ads for multiple clients using the API. This page:

        https://support.google.com/adwords/answer/2404246?hl=en

"URL Policies" states that the display URL and the landing URL should be on the same website. However, some of the advertisers have tracking/logging servers that are in the same domain but on different servers.

For example, with two hosts 33403.log.clientsite.com   and    www.clientsite.com

The landing URL would be https://33403.log.clientsite.com/product5?param1=a&param2=b&param3=etc
because the server "33403"  has code that will log everything and then HTTP 302 redirect the client browser to
http://www.clientsite.com/product5

I have a concern that if we create hundreds of ads this way with the API, they will all fail because the display URL and the landing URL are not the same.

Can anyone weigh-in on how this might work before we invest programming hours/resources on making a bulk tool that might "blow up"?

Thanks.

[Josh Radcliff (AdWords API Team)]

Hi,

For policy questions, please contact the Policy team via this link.

Thanks,

Josh, AdWords API Team

[apiapi]

The Policy team referred me to https://support.google.com/3pascertification/answer/94230?hl=en# which only mentions rules around the Display Network and 3rd party ad serving.

I need a clear answer to the question if for a Search ad, the display URL may be "clientsite.com", actual URL is "33403.log.clientsite.com" and if that URL may redirect to "clientsite.com" so the client's clicks will track/log on their servers using their existing framework.

Thanks.

[Josh Radcliff (AdWords API Team)]

Hi,

I just discussed with a colleague, and your use case should be fine. The key point is that your redirects must eventually redirect the user to a site in the display URL's domain. Therefore, if you are doing:

Display: clientsite.com

DestinationUrl: 33403.log.clientsite.com/param1=X&param2=Y

and 33403.log.clientsite.com/param1=X&param2=Y ultimately redirects the user to some clientsite.com/xyz... page, then that's acceptable.

What would not be acceptable would be if the final redirect from 33403.log.clientsite.com/param1=X&param2=Y was to a page on 33403.log.clientsite.com.

Let me know if that doesn't clear things up.

Thanks,

Josh, AdWords API Team