mcpField
I
ima-sdk-basics

ima-sdk-basics

github.com/googleDevelopment21.6k1.2k installsUpdated today
Repository

About ima-sdk-basics

A practical introduction to the Google IMA SDK for developers integrating interactive ads across platforms. It outlines the general ad request and playback lifecycle, with platform-specific guides for implementation details.

Key features

  1. 01Request ads from VAST-compliant servers
  2. 02Initialize the SDK and ad UI
  3. 03Handle ad loading and playback events
  4. 04Destroy AdsManager and release resources

Use cases

  1. 01Integrate video or audio ads into websites
  2. 02Manage in-stream ad playback in apps
  3. 03Follow platform guides during SDK integration

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/google/skills --skill ima-sdk-basics

After installing, type/ima-sdk-basicsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
ima-sdk-android-guide.md
ima-sdk-ios-guide.md
ima-sdk-tvos-guide.md
ima-sdk-web-guide.md
ima-sdk-web-iframe-mode.md
ima-sdk-web-mobile-safari.md

Details

From the project README

IMA SDK basics

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:


Quick start (general workflow)

  1. Import the SDK: Prerequisites, dependencies.
  2. Initialization: Early setup, Warmup, Settings Configuration, and Ad UI Setup.
  3. Ad Request: Creating and triggering the request, User gesture compliance.
  4. Ad Load Success/Failure: Handling the load event to get the AdsManager, or handling early fatal errors.
  5. 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.
  6. 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.

Comments

Markdown supported