Google Ads Developer Blog: AdWords API: Upgrading your Ad Extensions - a remi...: As previously announced, starting on September 23, 2013, call, app and sitelink
extensions will automatically upgrade to their new formats. If you
haven’t done so already, we encourage you to upgrade your extensions
ahead of the September 23 deadline so you can take early advantage of
the new features, accrue statistics on the upgraded extensions sooner, and ensure that your extensions continue to show.
Starting on the upgrade date, the following changes will take place:
If you allow your legacy extensions be auto-upgraded, the system will do its best to detect and avoid creating duplicate extensions. We recommend that you check all your extensions after the upgrade is finished to ensure they’re configured as you’d like.
Resources
To learn more about managing upgraded extensions with the AdWords API, make sure to consult the Feed Services guide. For a code example on how to upgrade extensions on your own, look in the migration folder in all client libraries.
See more from source
Starting on the upgrade date, the following changes will take place:
- You won’t be able to use CampaignAdExtensionService.mutate to update your legacy extensions.
- The 25 characters limit will take effect. Make sure you adjust your sitelink text to 25 characters or less so your extensions continue to show.
The use of CampaignAdExtensionService.get
for legacy call, app and sitelink extensions, will be available through
October 23. You can use it to consult and compare your legacy
extensions data with their upgraded counterparts.
If you allow your legacy extensions be auto-upgraded, the system will do its best to detect and avoid creating duplicate extensions. We recommend that you check all your extensions after the upgrade is finished to ensure they’re configured as you’d like.
To learn more about managing upgraded extensions with the AdWords API, make sure to consult the Feed Services guide. For a code example on how to upgrade extensions on your own, look in the migration folder in all client libraries.
See more from source
No comments:
Post a Comment
Note: only a member of this blog may post a comment.