We are pleased to announce the release of Bing Ads Editor version 11.2 , with support for Callout Extensions, Custom Ads for Native, and some efficiency upgrades to help you manage your campaigns faster. Each new release of Editor is a response to your feedback on what is needed most, so keep it coming, and read on for more details.
We announced Callout Extensions back in April, which enrich your ads by highlighting the best of your business. With this release, we added support for Callout Extensions to help you efficiently manage them in bulk. Each campaign and ad group can have up to 20 Callout Extensions associated.
Bing Ads Editor has Shared Callout Extensions, enabling you to create one Shared Callout Extension, and then associate it with multiple campaigns and ad groups.
Custom Ads for Native
Custom ads for Native give advertisers the ability to provide ad copy for Bing Native Ads that is different from their search ad copy. Native ads perform better when they explain benefits and entice users to read more about a product and service, as opposed to a typical call to action in a search ad. This feature gives advertisers the power to create separate ad text for native and search; and native ads will serve only for native placements as long as there is at least one search ad in the ad group.
In order to create Custom ads for native, simply select “Native” as “Ad format preference” for your text ads in Bing Ads Editor. Learn more about Bing Native Ads.
Automatic removal of duplicate items during import
We heard your feedback that manually removing duplicate items after importing is time consuming and cumbersome. That’s why we take care of de-duplicating items for you in Editor 11.2. While importing, any duplicate items except one will be skipped, eliminating the need for you to manually delete them.
Feel free to ping us on Twitter, ask questions at the Bing Ads Answers forum, submit and vote on your top-priority features at the Bing Ads Feature Suggestion forum, or send us your feedback directly at BingAdsemail@example.com.