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 October Product Bulletin podcast for the latest on Gemini API features, changes and product enhancements released this month by the Gemini product development team.

October, 2017

New Gemini Audience Forecaster Tool Introduced (UI)

  • Gemini provides users with a new Audience Forecaster tool in the Gemini UI that lets you forecast estimates of weekly performance for your campaigns. The tool is available for native-only campaigns, and displays the estimated size of your campaign audience based on Locations, Age, Gender, Interests, Custom Audiences and Devices. For more information, see the Gemini Advertiser Guide.

New Gemini Power Editor Preview Version Introduced (UI)

  • Gemini now provides users with a Preview version of a new Power Editor, in the Gemini UI, that lets you manage your accounts more efficiently for greater control over your advertising campaigns. The core value proposition for the Gemini Power Editor is to provide advertisers with greater operational efficiency for monitoring and managing items across multiple entities, like accounts, campaigns, adgroups and ads. Capabilities introduced in this Preview release include filtering, bulk edit, edit before commit, and edit across multiple accounts. For more details, see the Gemini Advertiser Guide.

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.

Ad Site Setting in the Gemini v3 API and BULK UI

  • Ad Site Setting is a new RESTful object, available in the v3 Gemini API, that provides methods for creating, updating, and retrieving settings for site-specific ads, including pagination. A site-specific ad is a native ad that has been tagged by the advertiser to be shown to a user when that user visits a specific website. For example use cases, fields, and more details, see Ad Site Setting.

  • Also see new fields for creating and deleting ad site settings in BULK. For more details, see Ad Site Settings in BULK Field Objects documentation.

  • Also note a new v3 API filter option includeAdSiteSettings for BULK download. When set to true, this indicates whether ad site settings will be downloaded. Default value is false. For more details, see Bulk Operations.

New Guide: How To Utilize Dot Pixel & Conversion Rules

  • New step-by-step guide 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.

Updated Cube Field Definitions

  • See Cubes to review updated cube field definitions.

New BiddingStrategy Fields - API and BULK UI

  • Introducing new biddingStrategy fields for campaigns to optimize eCPC conversions. For details, see Campaigns and Campaigns BULK Field Objects documentation.

How to Use Call Extensions in BULK (Search Campaigns)

  • You can take advantage of Call extensions, or Click-to-Call, as it is typically known, if you wish to display a phone number in the format of a Call button for text ads on smartphones. Call extensions are available for Gemini search campaigns, using Bulk, and can be set at the campaign level. Please note that only one Call extension is allowed per campaign.


Call extensions are not currently available in the Gemini UI. You’ll need to download a sample bulk file in order to take advantage of this feature. Be sure to check out the section Call Extensions in Bulk for more information. In that section, you’ll also find a link to download a sample bulk file with Call extensions in .csv format.

Bulk Downloads Performance Reminder


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: New Reporting Cubes and Resources: Gemini V3 API and Upgraded URLs (UUs)

The new Gemini v3 API has been released as of July 25, 2017. We’ve introduced new Reporting cubes this month, for querying at the ad group level. For more information, refer to Cubes.

  • Use site_performance_stats when querying for native ads campaign data.

  • Use campaign_bid_performance_stats when evaluating group-level bid modifiers.

  • New reporting dimensions available for querying at the advertiser, ad, campaign, ad group and keyword levels. For more information, refer to Dimensions.

  • Postman examples added for Upgraded URLs (v3) and Bid by Site (v2). For more information, refer to Postman API Toolkit.

In addition to the above new resources, the Gemini v3 API release provides partners and developers with following advantages:

  • Support for Upgraded URLs (UUs), which enable you to better define and control the landing page and tracking of your URLs. For more information on Upgraded URLs (UUs) in the new Gemini v3 API, refer to Upgraded URLs. Note the Migration Path and Upgrade Account to Work as UU sections.

  • Greater API object stability, as well as improved management of API changes, building on the enhancements in the Gemini v2 API.

  • Support for Site X Device Targeting with new available targeting attributes. For more information about Site X Device Targeting, refer to v3 Site X Device Targeting.

  • Additional bug and error fixes for improved performance and stability.

  • See the What’s New section and Navigating the API for more information about the new Gemini v3 API. Developers are encouraged to migrate to the v3 Gemini API in order to maintain access to the latest features and functionality. Please note that new features are only added to the current version. For reference, see details on v2 Objects.

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.

Reminder: v1 API Deprecation

  • Reminder: The Gemini v1 API was deprecated on June 1, 2016. Starting on September 1, 2017, the Gemini v1 API was relegated to End of Life (EOL) status. In addition, new features will not be added to v1.

Reminder: Deprecated v1 Reporting Endpoint

  • Please be aware that action may be required for the following deprecated reporting endpoint.

  • If you currently make calls only to /v2/rest/reports/custom for both POST and GET, there is no action required.

  • If you currently make POST calls to /v1/rest/reports then you need to migrate to the /v2/rest/reports/custom endpoint ASAP.

  • If you currently make POST calls to /v1/rest/reports/custom and GET calls to /v1/rest/reports, then you need to migrate to v2 before v1 EOL THIS year Sept 1, 2017.

Gemini Native Ads Specs and Resources

Gemini API Video Tutorials

Getting Started Guide: OAuth 2.0 Authentication Steps

Glossary of Gemini Terms

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

  • We’ve added a new matrix which details the required fields when serving different ad types. For more information, see Ad documentation > Matrix view of required fields.