Pre-Roll Desktop

See Demos

Amplify your message with direct social sharing functionality across Twitter.

See demos

Data points

• Hour
• Minute
• Second
• AM/PM
• Day of Week

Layout

• Countdown placement & formatting are customizable

Copy Options

• Customizable

Required Deliverables

• Start and end dates of countdown
• Start and end time of countdown (including timezone)
• Backup logic for instances when location/time data is not available.

Notes

• Supported across all time zones.
• Leverages the user's clock (with IP-lookup as backup) to determine time.
• Countdown clocks should only auto-animate the “seconds” for up to :15, per standard ad spec guideline. Can request an ad policy exception to have countdown animate indefinitely, as long as it is not too flashy or distracting.
• DSP and Reserved Ad Server support any time of day/countdown functionality.

See Available Data specifications below:

Weather, Pollen, Air Quality & UV Index

Personalize messaging based on current weather conditions, temperature, pollen counts, air quality, humidity index and/or UV index.

See demos

Temperature data points

• Support Celsius or Fahrenheit
• Can be specific temperature (i.e. 75°F or i.e. 24°C) or temperature range (i.e. 75°F - 90°F)

Weather condition data points

• Snowy
• Rainy
• Windy
• Cloudy
• Sunny
• Stormy

Pollen data points

• Very Low
• Low
• Moderate
• High
• Very High

UV index data points

• Low
• Moderate
• High
• Very High
• Extreme

Air quality data points

• Poor
• Low
• Moderate
• Good
• Excellent

Humidity data points

• Defined as a percentage range (i.e. 32% - 55%)
• Minimum value is 0% and maximum value is 100%

Notes

• Data sourced from Yahoo’s Weather Service, which leverages AccuWeather data.
• Leverages the user's IP address to determine location.
• Data is updated every 30 minutes.
• Available in DSP and Reserved Ad Server. Not supported in Native.

Audience Segments

Serve hyper-relevant creative based on audience segments. All fueled by Yahoo’s future-proof Connect ID and NextGen Audience data.

Data points

• Advertiser 1st Party Segments
• 3rd Party Segments
• Yahoo Standard Segments

Notes

• If leveraging CRM data, segments must first be uploaded into the ad server. Note that additional time may be required for the segments to populate.
• All segments must be targeted on the media line to use in Dynamic Creative.
• Can include or exclude segments for creative decisioning.
• Available in DSP and limited support in Reserved Ad Server. Not supported in Native.

Location

Serve relevant offers to users, no matter where they are in the world. You can also drive foot traffic to physical locations via an interactive map and/or geo fencing.

See demos

Data points

• Country
• State
• City
• DMA
• Zip
• Geo-fencing (based on lat/long and predetermined radius)

Notes

• For geo fencing, radius can be miles, feet or meters away from lat/long.
• Location data can be pulled in for most ad formats. This data can be displayed or used to power other features and functionalities, like an interactive map.
• If the user has opted out of data personalization, we can only leverage down to their zip code level. Lat/Long and IP can only be used for people who have not opted out of data usage.
• Native only supports contextual personalization for city, state, and county. Personalized post-tap Tiles can also be used as the landing page for Native units.
• DSP and Reserved Ad Server support any location personalization, including interactive map integration.

Interactive Map Required Deliverables

• Spreadsheet of locations with addresses, including zip code and/or lat/long. Lat/long is required for geo fencing.
• Any additional store-level information that will be used for decisioning and/or displayed in the ad unit (i.e. store name, website link, etc).
• Geographic radius for creative decisioning based on zip code or lat/long.
• Backup logic for instances when location data is not available.

Time of Day & Countdown

Highlight upcoming events and flash sales to promote consumer actions.

See demos

Data points

• Hour
• Minute
• Second
• AM/PM
• Day of Week

Notes

• Supported across all time zones.
• Leverages the user's clock (with IP-lookup as backup) to determine local time.
• Countdown clocks should only auto-animate the “seconds” for up to :15, per standard ad spec guideline. Can request an ad policy exception to have countdown animate indefinitely, as long as it is not deemed 'flashy' or 'distracting'.
• Native only supports specific countdown functionality. See Moments spec page for details.
• DSP and Reserved Ad Server support any time of day/countdown functionality.

Time of Day Required Deliverables

• List of times or days-of-week and their and corresponding personalized messaging/creative.
• Backup logic for instances when location/time data is not available.

Countdown Required Deliverables

• Start and end date of countdown.
• Start and end time of countdown, down to the second (including timezone).
• Backup logic for instances when location/time data is not available.

Contextual

Personalize creative based on page-level contextual data.

See demos: Desktop Fantasy Football | In-App Fantasy Football) | Finance Buttons

Data points

• Yahoo Fantasy Sports variables
• Yahoo Finance Data (limited data)
• DSP Contextual Segments

Notes

• DSP contextual segments must be targeted on the media line to use for decisioning.
• Finance data is only available on the Yahoo Finance quote results pages.
• Fantasy Sports data is only available on the Yahoo Fantasy Sports pages.
• Only in-app availability is within the Yahoo Fantasy Sports app via Native Pencil unit. Variables are limited to Team Name, Opponent Team Name, and Team Rank.
• Reserved Ad Server supports Yahoo Fantasy Sports and Yahoo Finance contextual data only.
• DSP supports all contextual data points.

Demographics

Personalize and/or optimize creative based on user demographic data.

See demos

Data Points

• Age Buckets (18-20, 21-24, 25-34, 35-44, 45-54, 55-64, 65+)
• Exact Age (i.e. 44)
• Gender (Male or Female)

Notes

• Proprietary age/gender data built from unique, validated data from across Yahoo.
• Only supported in DSP and Reserved Ad Server, not available in Native in-stream (only via Display Tiles).

Feeds

Yahoo can intake external feeds and display them in any number of ways. Interested advertisers should discuss implementing this feature with their Yahoo Creative Studios contact. Feeds can include things like products, store locations, social media content, etc.

See demos

Supported Feed formats

• CSV
• Google Sheet
• JSON
• XML
• Text

Notes

• Feeds can include up to 10,000 rows.
• External feeds hosted by the Advertiser can refresh every 5 minutes. If Yahoo is hosting the feed, we only support pre-determined, manual refreshes. Work with your post-sales contact to determine refresh rate on a per-campaign basis.
• If implementing a retargeting strategy, Dynamic Product Ads should be used.

Option 1: Client’s API Services (recommended)

What is it? Connects the creative directly to the client’s database. The client will hold the data.

What do we need from the client? Documentation on how to access and use their API. Each API is unique and we need a key on how to access it and which endpoints we’ll be referencing for our creative specifically.

Can PII information be used? Yes

Option 2: HTTP POST Method

What is it? Appends the form-data inside the body of the HTTP request and sends it to the client’s endpoint/server.

What do we need from the client? 1)The endpoint url 2) An example of the data that should be sent to that endpoint (i.e., a sample object). 3) Confirmation that this endpoint is able to accept data from client-side communication (no server-server authorization tokens)

Can PII information be used? Yes

Option 3: HTTP GET Method

What is it? Appends the form-data to the URL query string and sends it to the client’s server upon submission.

What do we need from the client? The parameters that go into the url and what their expected values should be.

Can PII information be used? No

NOTE: A disclaimer on all creative is required. Additionally, creative must be approved by Yahoo Ad Policy prior to launch.

Image

• File Types: JPG, GIF, PNG (Equirectangular)
• 2:1 aspect ratio (2048x1024 minimum)
• Up to 2MB

Auto-initiated Video

• A 15-second autoplay video: 1280x720 Equirectangular MP4 Video up to 2MB (Polite Load)
• Audio on user click

User Initiated Video

• Unlimited video play ** User-Initiated Video: 1280x720 Equirectangular MP4 Video up to 10MB.
• Audio on user click

• Up to 2-6 touchpoints
• Include CTA
• Avoid putting price or inventory that could change

Ad Bar size is customizable

• Ad Bar Overlay displays over video asset
• Not recommended for mobile due to the size of the screen
• Keep the crucial elements of the ad bar to only 1/4 of the 16:9 video real estate
• Creative should support the video content and not interfere with crucial elements like messaging or logo in the video space
• Relevant messaging/CTA should not interfere with video player controls
• Should include a clear CTA
• Get creative with the space and break out of the typical rectangular shape
• Use animation time-mapping to support the video content

• Not recommended for mobile due to the size of the screen
• The video frame will reduce in size to allow for the canvas to display at a larger, more prominent size.
• The Canvas Overlay asset will display at full dimensions of the video ad space (1920 x 1080 or 960x540) while the video asset will resize within the video player.

• Maps
• Carousel
• Leads
• Dynamic
• Social Share
• Touchpoints

• Carousel size is customizable
• Up to 5 cards is recommended
• Static or video allowed
• Toggle functionality (< >) is required