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.
Introducing New Gemini v2 API¶
New Gemini v2 API has been released. Starting on June 1, 2016, Yahoo Gemini will migrate the programmatic Gemini API from v1 to v2; the current version of the Gemini API will be v2. Be sure to read the sections on Versioning and API v1 Deprecation, plus the FAQs for details.
Developers are encouraged to migrate to the new v2 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. In the event of a special situation that would require a fundamental change across all versions, a migration path will be provided. For any migration, you will have at least a 90-day window to migrate and integrate your app.
The Gemini v1 API will be supported for 90 days beyond the June 1, 2016 deprecation date. After that date, starting on September 1, 2016, the Gemini v1 API will be available for one year. After that time, it will be relegated to End of Life (EOL) status.
New Custom Audience Type: Audiences from Your Email Lists¶
Audiences from your email lists allow you to define and target audience segments of people who are on your mailing lists. Once created, these segments will be available for targeting, using the TargetingAttribute service. For more details, see Audiences from Email Lists.
API Support for Custom Audience in Search¶
Custom Audience targeting has been added for search advertising. This new capability allows advertisers to use their own data, in combination with Yahoo data, to effectively target their customers in search results across devices. The new APIs for Search Custom Audiences give advertisers the ability to modify bids on search campaigns when the ad is served against a Custom Audience user. Targeting fields for Search Custom Audience are CUSTOM_AUDIENCE and SEGMENT. For Bid Modifiers, CUSTOM_AUDIENCE is a valid targeting type with range 0.1 - 10.00. Also, SEGMENT is a valid targeting type with range 0.1 - 10.00. For more information, refer to Targeting and Bulk File Schema.
The audiences themselves are created the same way regardless of whether the advertiser wants to use them for Search or Native. See Custom Audience for information on setting up and managing Custom Audiences.
New Call Extension Stats Cube¶
A new call_extension_stats cube has been added to Custom Reporting. Use this cube to get detailed information about conversions on click 2 call ad extensions at the account, campaign and adgroup levels. For more information, see call_extension_stats.
Ad and Editorial Status Updates¶
Note the following: Any changes to either the landing urls or the text attributes of the following entities – Ad, Keywords and Sitelinks – will result in a state transition to ON_HOLD for the purposes of editorial review. Note that our SLA is 24 hours; however, in practice, most ads are re-activated in 1 to 2 hours. Please plan your edits and sync logic, accordingly.
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.
New Glossary of Gemini Terms¶
Latest Gemini API 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.
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.
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.