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.

October, 2015

Optimized CPC (oCPC) Pricing Support for API Partners - Native only

  • API users may now run Optimized CPC (oCPC) Gemini Native campaigns via the API, allowing optimization of delivery against a post-click objective. Your ad delivery will be optimized based on the CPA target that works for your business.
  • oCPC Pricing leverages insights from Dot, so adding a Dot tag to your site is essential.
  • Campaigns need to run on standard CPC pricing until 10+ conversions are captured, prior to oCPC launch.
  • For more details, see the Ad Group section: biddingStrategy and ecpaGoal fields.

Custom Audience: Targeting Users with 1st Party Data (Native)

  • We have introduced new Custom Audience, enabling you to better target your ads by creating audiences from your website, your customer lists, or your app. - Website actions: Define and manage audience segments of people who have visited or have taken certain actions on your website.
  • Audiences from customer lists: Target your ads to a specific set of people with whom you’ve already established a relationship.
  • New: Audiences from your mobile app: This new custom audience type lets you target people who have taken specific actions in your mobile app, like achieving a level in a game or placing an item in a shopping cart. See Audiences from your app for details.
  • See Custom Audience for details.

Pagination: New /count Method

  • New /count method now exposed for all endpoints. Use this method to get the total number of objects in the data set you are downloading. For more information, see Pagination.

New Hour Field: performance_stats cube

  • New Hour field added as a dimension to the performance_stats cube in Custom Reporting. The Hour dimension returns as an integer in the Advertiser timezone: for example, 2 = 2am, 18 = 6pm. Note that hourly data is available for up to 15 day ago. If you run a report that contains dates older than 15 days ago, your report will not return data for those dates. See Custom Reporting for details.

New CONNECTION and CUSTOM_AUDIENCE Targeting Types

  • New CONNECTION and CUSTOM_AUDIENCE targeting types added in Targeting Attribute. The CONNECTION type allows targeting of WIFI or any connection types and applies only to video ads with a CPV price type. Note that video ads run on all connection types by default.
  • For more information, see Targeting Attribute.

Broad Match Modifier (BMM) - API, UI and Bulk

  • BMM is enabled by utilizing a plus symbol (+) in front of one or more words of a broad match enabled keyword. This plus symbol indicates which word(s) must be part of the user query in order for an ad to be considered to serve for a query. For more details, see How to Use Match Types for Keywords.
  • The Gemini UI, API and Bulk will support BMM when a plus symbol (+) is added to the keyword.
  • You can add or modify your keywords to enable BMM by utilizing the same keyword fields available today.

Deprecation of V1 Reporting APIs - 9/30/15

  • The standard Reporting Endpoint, https://api.admanager.yahoo.com/v1/rest/reports, is no longer supported after September 30, 2015. Upon deprecation of standard Reports, there will be no additional features or support moving forward.
  • Please plan on moving to Custom Reporting using the custom endpoint, https://api.admanager.yahoo.com/v1/rest/reports/custom, before September 30, as we will be allocating resources there.
  • Important update: The https://api.admanager.yahoo.com/v1/rest/reports endpoint will continue to exist to support COB and POLL calls. Any report requests submitted after 9/30/2015 will fail. You should plan on moving to Custom Reporting because custom reports provide more flexibility to get the data you need.
  • To track changes, updates and enhancements to the Gemini API, please read our Release Notes.

Latest Gemini API Release Notes - October 2015

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.admanager.yahoo.com/v1/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 Getting Started.

Overview of Search Features Currently Available

  • Updated 9/17/15.

  • Keywords

    • MATCHING: Exact, Phrase, Broad, BMM. Entry Point: Bulk, API.
    • NEGATIVES: Exact, Phrase. Entry Point: Bulk, API.
    • KEYWORD URLS & PARAMS: Used to create dynamic text or for tracking. More info. Entry Point: Bulk, API.
  • Ad Settings

    • CHARACTER LIMITS: Title: 50; Description: 150; Display URL: 35; Destination URL: 2048. Entry Point: UI, Bulk, API.
  • Targeting

    • GEO: State, City, DMA, Zip, Radius. Entry Point: UI: State, City, DMA | Bulk, API: Zip, Radius, Bid Adjustments.
    • Bid Adjustments available via Bulk, API. Range is -90% - +900%.
    • Radius can be specified in increments of 1 mile. Range is 1-500 miles, specified by longitude and latitude.
    • Advanced Geo Targeting options available to support physical location or interest. Entry Point: Bulk, API. For more information, see Campaigns and Ad Groups.
    • TIME OF DAY: Ad scheduling in 15 minute increments. Entry Point: Bulk, API.
    • DEVICE: Bid modifiers are available for all 3 devices, with varying ranges. Desktop: 0% to +100%; Smartphone: -100, -90% to +300%; Tablet: -20% to +300%. Entry Point: Bulk, API.
  • Reporting

    • Performance Reports: Reporting is available at the following levels: Campaign; Ad Group; Ad; Keyword; Targeting (campaign level only); Ad Extensions; Product Ad. Entry Point: UI, API.
  • Ad Formats

    • SITELINK EXTENSIONS: Entry Point: Bulk, API.
    • CALL EXTENSIONS: Entry Point: Bulk, API.
    • PRODUCT ADS - Pilot: Currently available on smartphones and tablets. Testing soon on desktop. Entry Point: UI, Bulk, API
    • LONG AD TITLES: Will not exceed 55 characters on smartphones or 65 on tablets.