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 April Product Bulletin podcast for the latest on Gemini API features, changes and product enhancements released this month by the Gemini product development team.
New Bidding Strategy: Maximize Conversions¶
- New bidding strategy, Maximize Conversions, introduced. It’s ideal for advertisers looking to spend their budget in full, getting the most conversions at the lowest CPA possible.
- Note: With this update, setting bidding strategies has moved from the ad group level to the campaign level, and campaign-level bidding strategies override ad group bidding strategies. Bidding strategies set at the ad group level via the Gemini API or Bulk are now deprecated as of v3. As a best practice, we recommend setting bid strategies at the campaign level, which has been exposed for v3 and above. For descriptions of bidding strategies described in API objects, see Campaigns and Ad Group documentation. For updated information on Bulk, refer to Bulk Campaign Fields. For more details on how each bidding strategy works, see Use New Bidding Strategies For Greater Control & Flexibility in the Gemini Advertiser Guide.
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:
- Please visit the v1 deprecation note.
- Note: Action may be required to migrate from the Deprecated v1 Reporting Endpoint.
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¶
- Native ads combine various brand assets to produce rich, compelling ad experiences and display them alongside content, providing interaction and engagement superior to traditional display advertising. See Gemini Native Ads for details on native ads, including key benefits, where native ads appear, and detailed information about various Yahoo Gemini native ad types.
Gemini API Video Tutorials¶
- In this series of introductory videos, the Gemini Development Team will walk you through some of the basic steps you’ll need to follow before you first begin making API calls and leveraging the Gemini platform for programmatic ad buying.
- Get Started with Programmatic Gemini API - Episode 1
- Working with RESTful Objects in Programmatic Gemini API - Episode 2
- How to set up your Sandbox Environment in the Programmatic Gemini API - Episode 3
Getting Started Guide: OAuth 2.0 Authentication Steps¶
- New, detailed explanation of steps to follow before you begin OAuth 2.0 authentication. If you’re new to the Gemini API, you should read the section and follow the steps listed. Note also in the section on OAuth refresh tokens that access tokens will expire after 60 minutes.
Check Out What’s New¶
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.
- 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.