← LeaderboardThe Skill Leaderboard

ima-sdk-client-side

Supports Interactive Media Ads (IMA) SDK. Use this skill for client-side ad insertion when you are requesting video ads for websites, apps, TVs or other platforms using VAST or VMAP. Do not use for Dynamic Ad Insertion (DAI), SSAI, or SGAI.

Published by google ↗google/skills

Try your first task

ima-sdk-client-side

Start a fresh conversation. Replace the highlighted placeholders.

Use ima-sdk-client-side to integrate client-side VAST or VMAP ads into [platform] video player using [ad tag URL], including ad lifecycle, content fallback, and cleanup.

Required inputs

[platform]
[ad tag URL]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: ima-sdk-client-sidedescription: >-  Supports Interactive Media Ads (IMA) SDK.  Use this skill for client-side ad insertion when you are requesting video ads  for websites, apps, TVs or other platforms using VAST or VMAP.  Do not use for Dynamic Ad Insertion (DAI), SSAI, or SGAI.license: Apache-2.0metadata:   author: Google LLC  version: "1.0.2"  category: GoogleAds

IMA SDK client-side

The Google IMA SDK (Interactive Media Ads) lets you load in-stream video and audio ads into websites, apps, TVs and other digital platforms. Use an IMA SDK to request ads from any VAST-compliant ad server and manage ad playback.

Prerequisites

Before integrating the IMA SDK, you must read the platform-specific guide below to support all platforms that your app can support:

Web/HTML5/ReactJs/NodeJs/Angular: Read all these guides ima-sdk-web-guide.md, ima-sdk-web-iframe-mode.md, ima-sdk-web-mobile-safari.md
Android/AndroidTV/ReactNative: Read ima-sdk-android-guide.md
iOS/tvOS/ReactNative: Read all these guides ima-sdk-ios-guide.md, ima-sdk-tvos-guide.md

Quick start (general workflow)

Import the SDK: Prerequisites, dependencies.
Initialization: Early setup, Warmup, Settings Configuration, and Ad UI Setup.
Ad Request: Creating and triggering the request, User gesture compliance.
Ad Load Success/Failure: Handling the load event to get the AdsManager, or handling early fatal errors.
Ad Playback Events: Listening to playback events via AdsManager to coordinate content play/pause, and handling non-fatal LOG events and fatal active playback errors.
Cleanup: Properly destroying the AdsManager to release resources and prevent memory leaks.

For detailed, platform-specific implementation details, always refer to the guides in the Prerequisites section.