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.


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

June, 2018

Targeting 3rd Party Interest Segments

  • We’ve added the ability to target 3rd Party Interest Segments in Gemini. Use these to modify the existing targeting attribute endpoint using the new targeting type SEGMENT_3P. Targeting can be set at both the native campaign and ad group levels. See the how-to information in the Gemini Advertiser Guide for details on the fields and steps to create and manage these segments. Also see the 3rd Party Interest Segment section of the Data Dictionary for detailed information about the parameters as well as example calls.

How to Cancel API Job Processing

  • We’ve added the ability to cancel a job that is processing via the Gemini API. To do this, make a PUT call in Bulk via the API while it is processing by adding cancel in the body of your request. For more details and an example response, see the brief technical note in Bulk Operations documentation.

Reminder: New Dot DPA Setup Guides for Partners Using 3rd Party Tag Managers

  • We’ve added new Dot Setup guides for partners using 3rd Party Tag Managers for DPA Dot tags. The guides describe the steps required to set up and deploy Gemini Dot tags, if you work with Google, Signal or Sizmek for tag management. You can find links to these guides on the main Dynamic Product Ads page. Also see the Dot Tag Setup section of the Gemini Advertiser Guide to access these guides.

Video: Native Ad Formats

  • To view the different available types of Gemini ad formats and some of their key features, check out our 3-minute video on native ad formats, with examples that illustrate native ad types. (Note that there is no voice-over audio narration.)

Reminder: New Chrome extension to validate Dot tags for Dynamic Product Ads (DPA)

  • Gemini now provides you with a Chrome extension that you can use to inspect, validate and troubleshoot Dot tags that you’ve instrumented on your website. See the DPA Dot Instrumentation documentation for details on installing and using this new extension. Also, see the Dynamic Product Ads section of the Gemini Guide for more information including key benefits and other topics.
  • 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: New Guide: Integrate Tumblr with Gemini

  • This new guide describes how you can integrate Tumblr Sponsored Posts with your existing Gemini API account. The advantage for Gemini partners and developers is that you can create Tumblr posts programmatically via the Tumblr Ads API and then manage those post campaigns via the Gemini API. For prerequisites and more details, see Integrate Tumblr with 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


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.


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{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.