While upgrading current ads, the AdUrlUpgrade object allows only one final
URL. Is there a way to upgrade ADs with multiple final URLS with out losing
stats?
Thanks
Gopi
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https
Hi Gopi,
I'm guessing this is related to our earlier discussion
https://groups.google.com/d/msg/adwords-api/QQBgwf0l67U/uyy6CupkADcJ.
Could you clarify what you mean by final and landing URLs? Just to be
clear, the *trackingUrlTemplate* and *finalUrls* do *not* have to be in the
same domain,
Just checking if anyone is in the same boat in regards to Upgraded URLS
with redirect templates
My current destination URL will be a redirect URL and A/B tests are mapped
with the redirect URL, we can added new A/B tests for the same domain to
the redirect URL dynamically in our internal
={adposition}AdID={creative}keywordId={targetid}
And then we dont need to have ANY DestinationUrl or FinalUrl on our
keywords
BUT
We have many many keywords already in existance. What we want to do is
simply remove all the Destination urls / Final urls (if auto upgraded) from
the Keywords
keywords
BUT
We have many many keywords already in existance. What we want to do is
simply remove all the Destination urls / Final urls (if auto upgraded) from
the Keywords and default through to the Ad FinalUrl / trackinUrlTemplate -
all well and good, but how can we remove
,
Just looking at the possibilities for Final Urls and the migration from
Destination Url and i have a couple of questions
1. I would like to add the Google generated CriterionImmutableId for the
keyword used, as a custom parameter to my ad's Final Url. I see that i can
add
Hi all,
Just looking at the possibilities for Final Urls and the migration from
Destination Url and i have a couple of questions
1. I would like to add the Google generated CriterionImmutableId for the
keyword used, as a custom parameter to my ad's Final Url. I see that i can
add
, 2015 at 9:10:05 AM UTC-4, Logan Ice wrote:
Hi,
I was wondering if there was an easy way to update all sitelink
destination URLs to Final URLs? We have updated all ad destination URLs,
but would like to push for everything to be on Final URLs soon.
In Editor, I can copy and paste each sitelink
for the current attribute.
I'll raise this with the reporting team to see if we can improve on this,
but in the meantime if you have customers with multiple final URLs or
multiple final mobile URLs you may have to use the *FeedItemService*-based
approach I mentioned.
Thanks,
Josh, AdWords API
of multiple final
URLs to be somewhat confusing.
Just to make sure I understand correctly, if I get the following line in a
PLACEHOLDER_FEED_ITEM_REPORT:
Campaign,Attribute Values
Campaign Name,This is the link text; ; This is Line 2; This is Line 3;
http://example.com/url1; http://example.com/url2
on this,
but in the meantime if you have customers with multiple final URLs or
multiple final mobile URLs you may have to use the *FeedItemService*-based
approach I mentioned.
Thanks,
Josh, AdWords API Team
On Wednesday, April 29, 2015 at 3:54:38 AM UTC-4, Dorian Kind wrote:
Hi Josh,
thanks
extension, the 5th attribute
would contain the final URLs for this sitelink. Apparently they are either
of data type URL_LIST (according to
https://developers.google.com/adwords/api/docs/appendix/placeholders#sitelinks)
or REPEATED_URL (according to
https://developers.google.com/adwords/api/docs
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 your
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
which
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
101 - 115 of 115 matches
Mail list logo