Ads & revenue · Demo 2 of 5

A full-screen ad between questions

The game pauses for one large ad. The next button only appears after three seconds, so the ad gets a real view before the reader moves on.

Riddle features: Ad block + next button delay

Setup: 5 minutes per Riddle

900×600 Ad Manager slot

Live Riddle

Guess-it game · 1 Ad block

[[dg-riddle ZB8YkRvn h=640]]

Guess the emperor (or give up) to reach the ad. Watch the next button appear after three seconds.

[[dg-inspector]]

What just happened

One block, one setting, a guaranteed view.

01

The reader finishes the game

The guess-it game runs as usual. The ad is the next block in the flow.

02

The Ad block takes over

A large 900×600 slot fills the Riddle, with a short line above it that says why the reader waits.

03

Next button after 3 seconds

The delay is a block setting. Readers can't skip the ad before it has been on screen.

Build it yourself

The block and the Riddle settings.

1 · The Ad block (Riddle Builder API)

Set it up in the Creator, or like this if you build Riddles by API:

{
  "type": "Ad",
  "title": "Thank you to our sponsor",
  "projectSlot": { "slotId": 1 },
  "isShowNextButtonAfterDelayEnabled": true,
  "showNextButtonDelay": 3
}

2 · In the Riddle Creator

Four settings on one block.

  1. Ad block: insert it after the question or game.
  2. Slot: choose the large 900×600 project slot.
  3. Next button: switch on “show after delay” and set 3 seconds.
  4. Title: a short line so readers know why they wait.

Reader experience

Delay, don't trap.

  • Keep the delay short: 3 to 5 seconds is enough for a viewable impression.
  • The next button still appears if the ad is blocked, so nobody gets stuck.
  • One large ad per Riddle works better than several small interruptions.

Next demo · 3 of 5

Video ad before the result

Open demo →
Scroll to Top