Final and Destination URLs - how to proceed

[veseo]

Hello, 

I'm currently trying to figure out how to proceed with the migration of Destination URLs to Final URLs (yeah, I know it's a bit late to think of it, but my previous plan had a major flaw that was only discovered a few days ago, so a rewrite is now needed). The problem is that we have quite a few clients and manually migrating them to the new format (with final URLs) will take lots of credits, so that's only a worst case solution. Here's what's not really clear to me:

- Starting from July 1st, destination URLs will not be mutable (even though I can still create keywords with destination URLs, how's that possible?) via the API and we need to set final URLs instead. Okay, but if I just set final URL instead of destination URL, I get the dreaded CANNOT_SET_BOTH_DESTINATION_URL_AND_FINAL_URLS error. Let's say that I have to keep in my database whether the current criterion/ad has a destination url or a final url (even though it sounds quite an ugly solution) and send the correct one, based on that logic. However, what happens when the automatic upgrade migrates the criterion/ad to the new format? Do I need to sync periodically, just to see which entities have already been migrated and which ones are yet to be migrated?

[Danial Klimkin]

Hello,

As per the blog post, the destination will become read only any time after July 1st. This guarantees that is it not read only before July 1st.

It is not allowed to send both final urls and destination url at the same time. If you prefer to wait until after migration, you'll need to check if the ad was migrated, or, handle this error. You can also use validateOnly flag for your updates to see if an error occurs without actually making any changes to the object.

-Danial, AdWords API Team.