Aditude Custom Rewarded — test bench

Wrapper: gamersberg-wClcBNUC6z / gamersberg-longform  ·  API: tude.initCustomRewarded()

Reward demo

Gems0
Rewards earned0
Handle stateidle

Blox Fruits — Full Value List (September)

Leviathan Heart trades for roughly 2 Kitsune + 1 Dough right now, and the Gas permanent is trending up after the update. Dragon East is holding value while Dragon West keeps dropping...

Mirror Fruit demand spiked 40% this week. Sellers are asking 3 Leopards for a permanent Portal, which is well above the fair-trade line.

Value list locked Watch a short ad to unlock this page

Wrapper diagnostics

checking…

Reward receipt — the only signal that grants

Stays empty unless the ad is genuinely completed. No fill, or closing early, leaves this blank — that is the guarantee. Screenshot this for your devs.

reason: "gam" = Google's own rewardedSlotGranted verdict; its countdown, skip and close UI are Google's, and countdownTime / text / cssVars / closeButtonDelaySeconds are inert for that session (remainingTime: -1). reason: "timer" = the custom overlay's own countdown completed. Either way, grant on this one callback and nothing else.

no reward granted yet

Yield instrumentation

Prebid wins0
Prebid earnings (session)$0.000000
waiting for renders…

Prebid wins show exact CPM. Google (AdX/AdSense) wins show only line item and advertiser IDs — Google does not expose price in the browser, so those rows have no dollar figure by design.

Reading the results: demand partners bid against the page domain, so this only produces realistic fill on a gamersberg.com hostname — on pages.dev or localhost every bidder refuses and you'll get onNofillonClose(reason:'nofill'). No fill means no reward and the countdown never starts; that's the documented guarantee, not a bug. Keep showOn = immediately to always see the overlay chrome, and raise nofillTimeoutMs to give bidders longer.

Testing mobile: nothing to configure — the component picks its shell from viewport width alone (mobile < 728 ≤ desktop) and re-syncs on resize. Narrow the window, or use DevTools device emulation (F12 → Ctrl+Shift+M), and watch the shell line in diagnostics flip. Desktop lays video-rects side by side; mobile stacks them.

initCustomRewarded options

Both are ticked here because GAM-first with fallback is the intended production setup. Note the library default is enabled: false — Google native rewarded is not attempted unless you pass gamRewarded explicitly. Unticking both gives you the custom overlay only.

Event log