6. Feeds Are a Pain
● Formerly, Feeds were too much work
○ 4 API Services
■ Feed
■ FeedMapping
■ FeedItem
■ [Customer/Campaign/AdGroup]Feed
● Needed to understand matching
functions, feed attribute mapping, etc.
6
11. We Need Something Easier
● New Extension Setting Services simplify
the most common use cases
○ Sitelinks
○ Call
○ App
○ Reviews
○ Callouts
○ Customizers
11
13. What’s New?
● New classes for ad extensions
[Sitelink/Call/App/Review/Callout]FeedItem
● New classes for associating them
[Customer/Campaign/AdGroup]ExtensionSetting
● New services to manage them
[Customer/Campaign/AdGroup]ExtensionSettingService
● Matching functions are created
automatically
13
14. New Steps (Campaign Sitelinks)
● Create and populate the sitelinks feed
SitelinkFeedItem, ExtensionFeedItem,
ExtensionSetting
● Associate the feed to the campaign
CampaignExtensionSetting,
CampaignExtensionSettingOperation
14
15. That’s it!
● No need for mapping attributes
● No need for matching functions
● No need to manage the feed schema
● Call 1 service instead of 4
● Guide
15
17. But I Already did it the Old Way :(
● FeedItems from Feeds created by the
AdWords UI only?
○ No migration needed!
● FeedItems from Custom Feeds using
FeedService?
○ Migration optional, but recommended
○ Migration Guide
○ Each client library has a migration example
○ Java Migration Utility coming soon
17
18. The Old Way Isn’t Going Anywhere
● Your legacy code will continue to work
● Extension Setting Services still use the
same underlying logic
internally
● Just a simplification
18
20. What’s the Catch?
● No support yet for location extensions
● No custom fields or matching functions
● Only one feed per extension type
● Backend feeds created for you have
origin=ADWORDS, so you can’t change the
schema
20
21. So...
● What are Feeds?
● Why Change?
● The New Way: Extension Setting Services
● Migrating to Extension Setting Services
● Limitations
21