Product Bulletin

Welcome to the Yahoo Gemini API Product Bulletin. This update includes a quick snapshot of recent and upcoming releases and is focused on features supported by the API. A summary of supported functionality is also included.

Product Bulletins are updated on a monthly cadence for Gemini API partners, account managers and developers.

Podcast

Tune into the February Product Bulletin podcast for the latest on Gemini API features, changes and product enhancements released this month by the Gemini product development team.

Note

The date of the Gemini API Webinar described in the podcast has been changed to (Wednesday) March 21st.

Gemini API Webinar on March 21st - Sign up Now!

The Gemini Solutions Engineering team is planning to host a one-hour Gemini API webinar on March 21st at 10:00am PDT.

February, 2018

New Sponsored Mail Ad

New Tumblr Native Campaign

  • Tumblr Native Campaign introduced, which uses the new the SOCIAL_ENGAGEMENT campaign objective. It is important to note that Tumblr campaigns are currently only available for whitelisted clients and reserved for Image Sponsored Posts. Contact your account representative or Solutions Engineer to take advantage of this new campaign objective. For setup how-tos, specs and more details, see Campaigns and Adgroups API documentation.

For additional reference, see the Matrix View of Required Fields When Serving Different Ad Types in Objects, as well as the the updated Matrix View of Required Fields in Ads.

Reminder: Migration Path Guide for Upgraded URLs

  • We’ve added a new guide with detailed steps on the migration path that you need to follow to upgrade the current Gemini Ad, Keyword and Sitelink entities to Upgraded URLs (UUs). For more details, see Migration Path For Upgraded URLs.

Reminder: Dynamic Product Ads (DPA) Resources

  • As a reminder, Dynamic Product Ads (DPA) became available in the Gemini API in May 2017. DPA are feed-based ads that can be shown on a native Gemini platform. Use DPAs as retargeting ads from your product feed that scale to promote your products to users who have visited your product websites. To get started, see Dynamic Product Ads for integration steps, product feed operations, creation of product sets and Dot Tag Instrumentation. For additional guidance, see the FAQs.
  • Also, Dynamic Products Ads became available in the Gemini UI in December 2017. Check out the new Dynamic Product Ads video and overview in the Gemini Advertiser Guide for quickstart on how you can take advantage of Dynamic Product Ads in Gemini.

Reminder: Gemini v3 API Roadmap

  • To stay current on the latest version of the Gemini API, check out details of the Gemini v3 API Roadmap. Taking advantage of the Gemini v3 API is straightforward and easy to navigate.

Reminder: Glossary of Gemini Terms

Reminder: Updated Postman to v3 Endpoint

  • Updated the Postman collection to the v3 endpoint for all Gemini API calls. Using Postman, you can test and verify the calls you make in the Gemini API. See Postman API Toolkit.

Reminder: Guide: How To Utilize Dot Pixel & Conversion Rules

  • Step-by-step guide available on how to effectively utilize dot pixel and conversion rules, based on your particular needs and setup, i.e., whether your advertiser account contains either a single website or multiple websites. The API workflow described in this document involves, essentially, no more than five basic steps to set up your Dot Pixel tags and Conversion Rules.

Reminder: Bulk Downloads Performance

Important

If you have a large account and notice your bulk downloads are taking longer over time, please consider deleting dormant or orphaned objects (Campaigns, Keywords, Ads, Ad Groups). See the Gemini Guide for more details on Bulk operations.

Reminder: Migration to Gemini v2 API or v3 API - Action May Be Required

Please be aware that starting on September 1, 2017, the Gemini v1 API was relegated to End of Life (EOL) status; the Gemini v3 API was released on July 25, 2017. The Gemini v2 API is still supported post-release. Official deprecation for the v2 API has not yet occurred. Partners and developers will be notified once this has been officially determined, and a schedule provided. Please note that new features will not be added to v1, and v1 will not be supported. For details on the v3 release schedule, as well as dates for the v1 deprecation, see the Release Schedule and Gemini API Versioning.

Important

Action may be required: Gemini API users may choose to migrate to either v2 API or v3 API.

To migrate to v2 API:

To migrate to v3 API:

  • Users are encouraged to migrate to the new Gemini v3 API directly. v3 is backward compatible with v2, and users may continue using the current landing/display URL structure on v3 without Upgraded URLs migration for the time being. The new Gemini v3 API has been released as of July 25, 2017. This release provides partners and developers with multiple new features and capabilities. For details, see Versioning.

Gemini Native Ads Specs and Resources

Gemini API Video Tutorials

Getting Started Guide: OAuth 2.0 Authentication Steps

Check Out What’s New

  • To stay current with changes, updates and new features in the v2 Gemini API, you’ll want to read this section. What’s New is updated on a weekly cadence for Gemini API partners and developers. Resources includes a link to archived Gemini Release Notes.

Using the Gemini Sandbox Environment

  • The Gemini API lets you work with a sandbox environment to test campaigns you’ve created and managed. You use the same consumer key and consumer secret you obtained when you set up your OAuth to access the sandbox.

Resource URI

https://sandbox-api.gemini.yahoo.com/v2/rest/{resource}
  • The Gemini sandbox serves as a modified version of the production environment. While all operations are designed to function the same in the sandbox as in the production environment, the campaigns and ads you create in this environment do not actually serve. The sandbox environment is completely separate from your production environment.
  • All campaigns, ads, and keywords you create in the sandbox are available in the sandbox environment only. There is no possibility that the ads you create in the sandbox will be accidentally served. Nor will your production accounts be charged for any mock transactions in the sandbox environment.
  • You will need to create a sandbox account in order to test in this environment. You can do this by making a POST call to the sandbox signup endpoint and passing in the name you wish to call your test advertiser. The response will be a test advertiser object that will only be available in the sandbox environment. For more details, see Testing - Sandbox.
  • Be sure to check out the video tutorial describing How to set up your Sandbox Environment in the Programmatic Gemini API - Episode 3.

Required Fields by Ad Type Matrix

  • A matrix is available which details the required fields when serving different ad types. For more information, see Ad documentation > Matrix view of required fields.