Skip to main content

Ads

If your game shows ads, use the QS Play SDK's ad and banner modules — don't include your own ad code or any third-party ad SDK in the build. The portal alone decides which ads are shown, when, and how often; the rules below describe what your game must do around that, not something you implement yourself.

Where banners may appear​

A banner must never cover or crowd anything the player needs — the playable area itself, or any button or control, even partially. Within that rule, a banner may be shown at any time, including during active gameplay — it doesn't have to wait for a menu or a pause.

The safest placements:

  • Menus, pause screens, between-level/end-of-level screens, and loading screens — there's no playable area to cover there.
  • The empty margins around the game when its own aspect ratio is narrower than the frame it's shown in — for example a portrait game inside a wider desktop viewport, with a banner in each side margin outside the game itself. These can stay up through active gameplay, since they never overlap it.

Never place a banner:

  • Over the playable area, even partially — including during active gameplay, where this matters most.
  • Close enough to a button or control that an accidental tap is likely — a misclick on an ad instead of a game control is a common source of player complaints.

When to request a video ad​

  • Midgame interstitials only in a natural pause — after game.gameplayStop(), never during active gameplay (the portal rejects the request otherwise — see ad.requestAd()).
  • Rewarded ads only on an explicit player action (for example, a "Watch ad for reward" button), with the reward named before the ad starts.

Pausing around an ad​

Pause gameplay and mute audio in adStarted, and resume in both adFinished and adError — the game must behave the same way whether the ad played or failed to show.

The game must work without ads​

No ad showing — unfilled, adsDisabled, an ad blocker, or any other error — must never block the player's progress. Treat a failed ad request exactly like a successful one that simply had nothing to show.

Fullscreen​

Request fullscreen only through game.requestFullscreen(). Ads render inside your game's own document, alongside the rest of the game — putting only a <canvas> or another single element into fullscreen through the Fullscreen API directly hides everything else in the document, ads included. See Technical Requirements · Iframe Compatibility and Gameplay & Content · Fullscreen Experience for the general fullscreen rules this extends.

Review checklist​

Before submitting a game that shows ads, confirm that:

  • No custom ad code or third-party ad SDK is included in the build.
  • Banners never cover the playable area or crowd a button/control, at any time — including ones shown during active gameplay (e.g. in the side margins around a narrower game).
  • "midgame" is requested only after game.gameplayStop().
  • "rewarded" is requested only after an explicit player action, with the reward named beforehand.
  • The reward is granted only from adRewarded, never earlier.
  • Gameplay and audio pause on adStarted and resume on both adFinished and adError.
  • The game remains fully playable when no ad is available.
  • Fullscreen is requested only through game.requestFullscreen().