Hi,
another update (that's the last one, promised :).
We did some tests and found that semicolons inside URLs are actually
escaped. That's the good news. The bad news is that empty attributes are
not returned in the Attribute Values field. Here's an example of actual
downloaded data:
"Placeho
Hi Dorian,
Unfortunately, that's correct. You won't be able to differentiate between a
semicolon that's indicating a new attribute and a semicolon that's
indicating another finalUrl or finalMobileUrl for the current attribute.
I'll raise this with the reporting team to see if we can improve on
Hi Josh,
thanks again for your quick reply. To be honest I don't really know whether
there will be a lot of these use cases at our company. We're just in the
process of preparing our tools to handle Upgraded URLs so we will be ready
for the migration in July, and we found the whole topic of mul
Hi Dorian,
The correct field type for *finalURLs* is *URL_LIST*. I'll fix the
documentation accordingly -- thanks for pointing out this inconsistency.
Regarding parsing the *AttributeValues* field, do you actually have cases
where you are specifying multiple *finalURLs* for feed items? I ask be
Hi Josh,
a quick follow-up about URL lists from Upgraded URLs.
In the Placeholder Feed Item Report, we can get a FeedItem's attribute
values in the "AttributeValues" field, which contains a semicolon-delimited
list of the FeedItem's attributes.
Now, for a FeedItem representing a sitelink exten
Hi Josh,
many thanks for your quick and concise reply!
Best regards,
Dorian
On Wednesday, April 22, 2015 at 10:28:31 PM UTC+2, Josh Radcliff (AdWords
API Team) wrote:
>
> Hi Dorian,
>
> AdWords allows multiple final URLs specifically for the use case where you
> are *not* including *lpurl* in
Hi Dorian,
AdWords allows multiple final URLs specifically for the use case where you
are *not* including *lpurl* in your tracking template. For example, if your
tracking template is directing traffic to a tracker that redirects some
traffic to one URL and other traffic to another URL, e.g., fo
Hello there,
>From the API documentation we know that the final URL fields of Ad objects
("finalUrls", "finalMobileUrls", "finalAppUrls") are lists.
I'm having a hard time understanding how ad serving works if there are
multiple final URLs for a given ad, for example, how does Adwords choose
w
