For the complete documentation index, see llms.txt. This page is also available as Markdown.

Interstitial (required)

You are reading the documentation for Bridge SDK v2. If you need the obsolete v1 documentation, see Documentation (v1).

Interstitials are full-screen ads shown at natural pauses: between levels, on game over, or when returning to the menu.

Configuration

Interstitial settings live in the config under the advertisement key.

{
    "advertisement": {
        "minimumDelayBetweenInterstitial": 60, // minimum delay between interstitials in seconds, default 60
        "initialInterstitialDelay": 0, // delay in seconds after game start during which showInterstitial() calls fail
        "interstitial": {
            "disable": false, // disable interstitials entirely
            "preloadOnStart": "level_completed", // placement to preload automatically right after SDK initialization
            "placementFallback": "level_completed", // placement used when showInterstitial() is called without one
            "placements": [ // map a game-level placement id to native placement ids, keyed by platform id
                { "id": "level_completed", "yandex": "native_placement_id" }
            ]
        }
    }
}

Is Interstitial Supported

Check this before showing interstitial-related UI or running interstitial logic.

Platform support · 24 of 26 platforms

Supports: crazy_games, dlightek, facebook, game_distribution, gamepush, gamesnacks, huawei, jio_games, lagged, microsoft_store, msn, ok, playdeck, playgama, poki, portal, samsung, telegram, tiktok, vk, xiaomi, y8, yandex, youtube

Does not support: discord, reddit

Minimum Interval Between Displays

Set the minimum delay between interstitial attempts. The SDK uses this delay to prevent ads from appearing too often.

The SDK tracks the delay internally. Set the required interval once; if you call showInterstitial() too early, Bridge waits or skips according to platform behavior instead of showing ads too frequently.

Interstitial State

Track state changes to drive ad-specific logic. For muting and pausing, prefer the universal platform events described below instead of reacting to each ad state separately.

Possible values: loading, opened, closed, failed.

While the interstitial is open, the game must be muted and paused. The recommended way to handle this is once, in a single place, by subscribing to the platform AUDIO_STATE_CHANGED and PAUSE_STATE_CHANGED events instead of duplicating the logic per ad type. Bridge raises those events whenever the host requests it — interstitials, rewarded ads, browser tab switches, system pauses — so a single universal handler covers every case.

Show Interstitial

Request an interstitial at a natural pause, such as a level transition, game over screen, or return to menu.

Last updated