320x50 Mobile Banner
Build your brand with premium display banners on mobile. These ads deliver a richer experience to the user than traditional standard banners. They can include video, interactive content, dynamic data and expansion to offer more real estate.
Deliverables
Ad components | File type | Dimensions | Max file size |
---|---|---|---|
Initial File Load | HTML, CSS, JS, JPG, PNG, SVG | 320 x 50 | 50 KB |
Host-Initiated Subload | HTML, CSS, JS, JPG, PNG, SVG | 320 x 50 | 100 KB |
Host-Initiated Video | MP4 and WebM | 320 x 50 | 1.1 MB |
User-Initiated File Load | HTML, CSS, JS, JPG, PNG, SVG and/or MP4 and WebM | 320 x 50 | 2.2 MB |
Expandable File Load - Portrait | HTML, CSS, JS, JPG, PNG, SVG and/or MP4 and WebM | 320 x 568 | 2.2 MB |
Backup/Static Image | JPG or PNG | 320 x 50 | 150 KB |
Available Features
Customizable. Reach out to the internal creative team to learn more about capabilities.
- 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.
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.
Required Elements
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
The following companies have been approved to verify and/or attribute App Install Campaigns:
- Adjust

- AppsFlyer

- Apsalar (Singular)

- Kochava (Native campaigns only)
- Up to 2-6 touchpoints
- Include CTA
- Avoid putting price or inventory that could change
NOTE: Expand feature is currently disabled for the following right rail ad sizes serving via DSP across Yahoo O&O publishers: 300x250, 300x600 and 160x600.
Functionality
- Expansion is optional
- Only permitted upon user interaction with the ad via click or tap (rollover expansion not allowed)
Call-To-Action
- Must be clearly defined
- Carousel size is customizable
- Up to 5 cards is recommended
- Static or video allowed
- Toggle functionality (< >) is required
General
Served via 320x50 ad call
Screen Support
- Mobile
Animation
Autoplay: 15 seconds max
Back-up Static
- Required for instances when the user's browser does not support creative functionality (e.g., HTML5, JavaScript).
- 3rd Party served ad tags are responsible for delivering the back-up image experience.
Retina Assets
Recommended
Ad Vendor
Ads must be site served or served by an approved vendor.
3rd Party Ad Tags & Trackers
Approved 3rd party vendors are allowed to serve select ads. To find out which ad formats are approved to serve via 3rd party, reach out to your Sales POC.
Approved 3rd party vendor trackers (e.g. click, impression, etc.) are allowed across ad formats.
For a list of approved 3rd party vendors, please visit the 3rd Party Vendor List.
Ad Choices
Display Ads have an Ad Choices linkable icon or graphic with "AdChoices" label. Read about AdChoices for more information.
Ad Policies & Guidelines
Ads must comply with Global Yahoo Advertising Policies.
HTML5 Guidelines
HTML5 ad specifications must follow HTML5 Guidelines.
SSL Compliance
Ads & 3rd party vendors must be secure and SSL compliant.
Creative Submission Timelines
Refer to Creative Submission Guidelines for ad design & build SLAs.
Yahoo News - SG
Yahoo Finance - SG
Yahoo Style - SG
Yahoo News - MY
Yahoo News - ID
Yahoo News - PH
DSP