Verbolus advertising strategy¶
Status: product policy plus staged implementation and vendor-evaluation plan
Date: 2026-08-15
Last reconciled: 2026-08-23
Audience: product, design, privacy, and monetization reviewers
Lifecycle: accepted product policy with staged implementation proposals. Live vendor approval, feature state, and deployment state must be verified through the operational process.
Related plan: Engagement platform plan
Operational review checklist: AdSense site-review runbook
This document expands the advertising section of the broader engagement plan. It describes where advertising may appear, how experiments should be isolated behind feature flags, what must be tested before rollout, and which advertising providers are plausible at different stages of Verbolus's growth.
The premise is that the puzzle remains the product. Advertising is acceptable only when it funds the product without making the game feel cheaper, interrupting play, creating accidental clicks, or weakening completion and return behavior.
Executive recommendation¶
Use a staged approach:
- Build the content and policy foundation that is worthwhile even without ads: How to Play, About, Updates, an accurate Privacy Policy, contact information, and a real consent/preferences surface.
- Test the proposed physical spaces with inert Verbolus house ads. Do not load an advertising network during this stage.
- If the placements feel acceptable, use one manually placed AdSense unit as the revenue and UX baseline. Do not enable automatic placement.
- Keep active mobile gameplay ad-free. The first gameplay-adjacent experiment should be a single desktop side rail on sufficiently wide viewports.
- Test a post-completion placement only below the result and the player's primary next action. Never put an ad in the Victory overlay or delay the next puzzle for an impression.
- Discuss managed monetization with Nitro first as traffic grows. Evaluate Playwire and Venatus later, when the audience can support premium programmatic sales or direct sponsorships.
- Prefer tasteful direct sponsorship of themed rounds, courses, and tournaments over increasing commodity display-ad density.
AdSense is not presumed to be the permanent winner. It is the useful baseline because it is broadly self-service and can support a deliberately small experiment. At low traffic, differences between networks are unlikely to outweigh retention, performance, and brand damage from the wrong format.
Product guardrails¶
- Active play must remain the quietest surface in the product.
- Ads never obscure or displace the puzzle, controls, result, standings, or primary next action.
- No interstitial is required to start a Daily, continue a round, regenerate Practice, or view a result.
- No ad is styled like a game control, system message, group invitation, or editorial content.
- A third-party ad is always visibly labeled when the provider does not make its nature obvious.
- The layout reserves the slot's dimensions before requesting an ad. A filled or unfilled slot must not move nearby controls.
- Ads fail open: blocking, timeout, no-fill, consent denial, or provider failure leaves a complete and usable page without an error prompt.
- Paid ad removal, if introduced, removes third-party advertising everywhere the entitlement is active. It does not provide a competitive advantage.
- Advertising is never included in push notifications or private group communication.
- A server-controlled master kill switch can stop all third-party ad loading without a deployment.
Placement plan¶
Placement matrix¶
| Surface | Initial decision | Conditions and rationale |
|---|---|---|
| Active gameplay on phone | Prohibited | The board and controls already use the scarce viewport. Ads would compete with the puzzle and increase accidental-click risk. |
| Active gameplay on desktop | Candidate: one side rail | Only when the viewport leaves genuinely unused horizontal space. The unit stays outside the game column, is non-sticky, and never follows the player over controls. |
| Victory overlay | Prohibited | Winning, seeing the score, sharing, and choosing the next action form one product moment. An ad inside the modal would feel like an interstitial. |
| Completed-puzzle page | Candidate: below completion actions | Show the full result and primary next action first. The player must be able to leave, share, view standings, or start another puzzle without passing an ad. |
| Practice regeneration | No loading-placeholder ad | Regeneration must not be delayed for an impression. A stable desktop rail may remain visible, but it must not reload or refresh for every generated puzzle. |
| Home/game catalog | Candidate: below primary catalog | Suitable after the player can understand and enter the product without crossing an ad. Prefer a fixed, reserved slot. |
| How to Play | Preferred first live placement | Substantial original instructions and worked examples provide a natural contextual surface away from game controls. Place a unit only after a complete instructional section. |
| Substantial Updates articles | Good candidate | A feature story, release explanation, or event article may carry one unit after the article or in a desktop rail. Do not monetize a thin changelog merely because the route exists. |
| About | Normally ad-free | This is a brand-and-trust page with little likely revenue. Prefer a Support Verbolus link rather than third-party creative. |
| Privacy Policy | Prohibited | A legal and trust surface must not appear monetized or initiate advertising data processing while explaining or changing those choices. |
| Settings and account controls | Prohibited | Account, notification, consent, export, delete, payment, and other preference choices must not be monetized or visually confused with advertising. |
| Group creation and invitation | Prohibited | These are short, task-oriented trust surfaces. An ad would add clutter and could resemble an invitation action. |
| Private group detail and Clubhouse sharing | Prohibited initially | Group activity is private social context. Keep programmatic creative out of member standings, nudges, and shared words. |
| Public scorecard, archive, or event recap | Candidate later | Appropriate only when the page has enough durable content and the unit is clearly outside the result and navigation. |
| Round or tournament between holes | Prohibited | Do not interrupt competitive flow or make continuation appear conditional on an ad. |
| Themed event landing/results | Prefer sponsorship | A clearly disclosed event sponsor is more coherent than unrelated programmatic units and can remain outside the puzzle itself. |
Editorial, trust, and policy pages¶
Creating How to Play, About, Privacy, and Updates pages improves the product's usefulness, transparency, and readiness for publisher review. That does not make every page suitable ad inventory.
How to Play is the strongest initial content candidate. It should contain useful original rules, worked examples, scoring, Daily-versus-Practice behavior, strategy, and common questions. A first unit belongs after the player has already received a complete instructional section:
How to Play Letter Golf
Rules
Worked example
Common questions
[ Advertisement ]
Strategy tips
Scoring
Daily vs. Practice
Do not put the unit above the title, between a heading and its explanation, inside a worked example,
or beside a Play action. The page must still feel like documentation rather than a frame built to
hold an ad.
Updates is conditional on substance:
- an Updates index containing a few short release-note bullets remains ad-free;
- an individual feature announcement, design article, puzzle history, language discussion, themed event story, or detailed release explanation can carry one unit after the article;
- a desktop side rail is acceptable only when the article column remains comfortably readable;
- an ad must not be styled like an update card, product announcement, or navigation item.
Keep About ad-free. Its purpose is to explain who makes Verbolus, what the product values, and how to contact or support it. A Patreon, tip, or supporter-membership link is a coherent action there; unrelated programmatic creative is not.
Keep the Privacy Policy permanently ad-free. It may be opened specifically to understand or change data choices, and it must work without loading an advertising provider. The same rule applies to Settings, account, consent, export, delete, checkout, receipts, and payment management.
Start with one manually placed responsive unit per eligible content page. Do not enable automatic placement merely because these routes exist. Reserve the slot dimensions, separate it clearly from links and calls to action, and omit it when the page lacks enough original content. Future public strategy guides, dictionary/editorial features, archives, and tournament recaps may be stronger content candidates than About or policy pages.
Desktop gameplay rail¶
The desktop rail is the most defensible gameplay-adjacent experiment because it uses space that does not exist on a phone. The current inert rehearsal uses a shared layout at 1,600 CSS pixels or wider: a 300px balancing column, 150px gutter, 600px game column, 150px gutter, and 300px rail. The game column therefore retains its normal width and centered position when the rail appears. Browser zoom naturally removes the rail once the CSS viewport drops below the threshold.
Requirements:
- one unit only;
- non-sticky and outside the puzzle column;
- a reserved width and height before the provider script runs;
- no horizontal overflow at browser zoom up to at least 200%;
- at least 150 CSS pixels between the edge of the game column and the ad, following Google's game-content placement guidance;
- hide the entire reserved region when there is no fill, unless retaining the empty space produces less disruption than collapsing it;
- no refresh when the player shuffles, submits, changes a tile, regenerates Practice, or navigates between client-side game states;
- removal as soon as the responsive layout can no longer preserve those constraints.
For Reverse Cross, the entry bank is part of the active puzzle controls just as Letter Golf's keyboard is. Do not insert advertising between the grid and entry bank, beside entries inside the game column, or in space revealed by a short bank. The external desktop rail may remain while the player works, and post-completion inventory belongs below the result and the primary New Practice action. Active mobile and narrow-screen Reverse Cross remains ad-free.
The internal rail preview currently reserves 300×600 to expose the full cost of a tall unit rather than understating it. The eventual manual unit size must follow the provider's supported inventory and pass the same separation and reflow checks. Do not design the game around a specific ad size until fill and revenue justify it.
Post-completion placement¶
The order should remain:
- completion acknowledgement;
- score and meaningful result details;
- primary actions such as share, standings, next Practice puzzle, or return to the round;
- optional advertising slot;
- secondary content.
The ad does not appear inside the Victory overlay and must not cause the overlay to remain open.
Closing the overlay should never trigger an interstitial. For Practice, Play another starts
regeneration immediately; the ad is not a countdown, gate, or substitute for the loading state.
On wide gameplay layouts, a post-completion unit may appear below the completed board while the desktop rail remains visible. Keep the post-completion unit below the primary next action and maintain enough separation that the two placements remain visually distinct.
Sponsorship treatment¶
Rounds and tournaments provide a higher-quality future advertising surface:
Halloween Nine
Presented by Example Sponsor
Nine delightfully strange word ladders available through October 31.
[ Start the round ]
The sponsor may appear on the event landing page, compact event identity, and final recap. It does not choose accepted words, puzzle difficulty, scoring, or standings. Sponsorship is disclosed, and clicking a sponsor link is never necessary to play or claim an earned result.
This model can also support a sponsor-funded free themed course without inserting unrelated ads between holes. It requires sales and campaign operations, but offers much better control over creative quality and brand fit.
Feature-flag design¶
Use Azure App Configuration targeting already present in the product. Keep flags narrow enough to stop a problematic surface independently, but do not build a generic ad-rule engine before an experiment needs one.
| Flag | Purpose |
|---|---|
AdPreviewEnabled |
Renders inert house-ad placeholders at every implemented placement for internal or targeted users, except where that user is selected for a live ad. It does not control the account-level site-review script or request an ad unit. |
AdsEnabled |
Master live-ad kill switch. No ad unit request is allowed when false. The route-scoped account script used for AdSense site review is intentionally independent of this flag. |
AdsContentPages |
Selects approved How to Play, Updates, and similar public editorial units for live advertising. |
AdsDesktopGameplayRail |
Selects the wide-viewport gameplay rail for live advertising. Client eligibility checks still apply. |
AdsPostCompletion |
Selects a live unit below completed-result actions. It does not enable Victory-overlay advertising. |
AdsPublicResults |
Reserved for a later public scorecard/archive/event-recap experiment. |
Provider identity, publisher IDs, slot IDs, and breakpoint values are configuration, not independent experiments unless a genuine need to vary them emerges. No provider secret belongs in a client bundle; public publisher and slot identifiers are still configured centrally to prevent accidental production/test crossover.
Eligibility order¶
Before requesting or rendering any live ad unit, evaluate:
- Is this a production environment and is
AdsEnabledtrue? - Is the route's placement flag true for this stable experiment cohort?
- Is the player entitled to an ad-free experience?
- Is the surface eligible—for example, desktop width for the gameplay rail?
- Has the applicable consent flow completed, and may the requested ad mode be used in this region?
- Is the route outside prohibited privacy, account, payment, and private-social contexts?
Any negative answer stops before requesting an ad unit. The account-level review script may already
be present on routes with implemented placements, but it does not make a unit request and must not
be mistaken for live eligibility. AdPreviewEnabled is separate: for
its targeted internal cohort, it renders a local placeholder at every implemented placement that
is not live-eligible for that user. A live ad and its preview are mutually exclusive. In shorthand:
This lets one user retain previews at content and post-completion placements while joining a live desktop-rail cohort:
| Cohort | AdPreviewEnabled |
AdsEnabled |
AdsContentPages |
AdsDesktopGameplayRail |
AdsPostCompletion |
|---|---|---|---|---|---|
| All previews | On | Off | Any | Any | Any |
| Live desktop rail, previews elsewhere | On | On | Off | On | Off |
| Live desktop rail only, no previews | Off | On | Off | On | Off |
| Neither previews nor live ads | Off | Off | Any | Any | Any |
Before targeting AdsEnabled for a selective live rollout, ensure the placement flags are also
targeted as intended rather than left globally on. Feature flags do not replace consent,
entitlement, or policy checks.
Use stable player/installation assignment so one person does not alternate between experiment and control on each request. Anonymous players already have a stable signed identifier suitable for cohort targeting; do not expose that identifier to an ad provider unless the reviewed integration and consent model specifically require it.
Deferred live AdSense and CMP integration plan¶
Current boundary and implementation trigger¶
As of 2026-09-13, AdSense site ownership has been verified, but the first site review did not
approve the site. The dashboard returned the site to Requires review and separately displayed
ads.txt as Not found, while the Policy Center listed no issue and the correct seller record
was publicly reachable. Google supplied no specific rejection reason; do not treat crawler,
content, header, SPA, or cold-start theories as established fact without evidence. The factual
history, production checks, and resubmission procedure live in
doc/adsense-site-review-runbook.md.
The publisher meta tag, ads.txt record, and account-level AdSense script are review plumbing. The
script is rendered on the submitted homepage entry point and pages that own an implemented
placement: both launched game routes, both How-to-Play guides, and substantial Update articles. It
is independent of feature-flag targeting so Google's review crawler receives consistent markup. No ad unit markup, slot ID, or
adsbygoogle.push call exists, and Auto Ads must remain disabled in the AdSense account. Google's
CMP remains deferred while review and the inert house-ad layout trial continue.
The Privacy Policy identifies the account-level script as active review processing while stating that Verbolus does not request or display ad units. It also identifies possible cookies, web beacons, IP addresses, identifiers, purposes, the partner-data link, CMP boundary, and state-law sharing posture. Immediately before live advertising, that section must be reviewed against the configured CMP/provider behavior and updated to describe live processing accurately.
Do not begin this integration merely because AdSense approves the site. Start it only when Verbolus
is ready to test the first live Stage 2 placement. Before any AdSense request can be enabled for
real users, the CMP, consent coordinator, live-ad coordinator, manual unit, Settings integration, and
tests below must ship together behind AdsEnabled: false.
Consent ownership and user experience¶
Use Google's certified CMP initially rather than buying or integrating a second vendor. Configure
its European regulations message with three first-page choices—Consent, Do not consent, and
Manage options—and target the EEA, UK, and Switzerland. Use the Verbolus name and mark, link to
https://verbolus.com/privacy, keep consent-message optimization off for the first experiment, and
do not add custom vendors or purposes for Verbolus's own use without a concrete need and policy
review.
There must never be two consent dialogs competing for the same decision:
| Situation | Consent surface and behavior |
|---|---|
| EEA, UK, or Switzerland | Google's CMP owns advertising and Google-product consent. Suppress the existing Verbolus banner for the decisions the CMP covers. Start with no AdSense request unless the user affirmatively consents; reconsider limited/non-personalized ads only as a separate reviewed decision. |
| Outside the CMP-targeted region | Retain the Verbolus consent experience for analytics and other existing purposes. Evaluate additional regional advertising-message requirements separately before serving ads there. |
| CMP status unresolved or provider unavailable | Fail closed: keep Google consent defaults denied, do not request an ad unit, and leave the game fully usable. The account-level review script may still be present on an eligible route. Do not infer geography from the IP address or silently treat a timeout as consent. |
| User reopens Privacy settings | Open the authoritative surface for that user: Google's CMP choices when it governs the region, otherwise the existing Verbolus controls. Do not maintain two independent, conflicting copies of the same consent. |
Use the provider-supported CMP/TCF APIs to determine whether the Google message governs the user; do not add a home-grown GeoIP service. The exact Google callback and timeout behavior must be revalidated against the current integration documentation when implementation begins.
Frontend architecture¶
- Put consent defaults first. Refactor the existing Google tag setup so denied defaults are established before Analytics, CMP, or advertising code can run. Start with Basic Consent Mode: block Google advertising and analytics requests until the applicable user choice is known. Advanced Consent Mode and cookieless pings require a separate privacy/product decision.
- Add one consent coordinator. Model explicit states such as
checking,google-cmp,verbolus,consented,denied, andunavailable. It owns the bounded CMP-discovery period, prevents the existing banner from flashing before the CMP decision, and exposes a single result to Analytics, Settings, and advertising. A timeout producesunavailable, neverconsented. - Separate review/bootstrap code from live requests. The account-level AdSense script and the minimum certified-CMP bootstrap may load while advertising is blocked. The existing account script is route-scoped, centralized, and de-duplicated; keep the account meta tag global. Neither is evidence that a user or placement is live-ad eligible.
- Add one idempotent live-ad coordinator. Centralize manual slot IDs and allow a slot request only after consent and every eligibility gate pass. Reuse the existing account-script boundary; do not paste the snippet into individual pages, enable Auto Ads, or create repeated loads or requests during client navigation, back/forward navigation, or Practice regeneration.
- Keep slots declarative.
AdSlotshould request a manual unit only after the loader reports ready and that slot's eligibility remains true. It must handle no-fill, blocking, timeout, navigation, and React remounts without duplicate requests, layout movement, or an application error. Existing house-ad previews remain a separate local component. - Handle changes and revocation. A changed CMP choice updates Consent Mode and prevents future disallowed ad requests immediately. Code that has already executed cannot truly be unloaded; clear/hide eligible slots, stop further requests, and reload when the provider requires it. Settings must provide a tested way to reopen the CMP rather than only changing Verbolus's local consent cookie.
- Constrain the provider. Review and narrowly update Content Security Policy directives for only the documented Google endpoints. Do not pass the Verbolus user ID, group membership, puzzle words, scores, or other game state to the provider. Add structured diagnostics for CMP outcome category, loader failure, request/no-fill, and kill-switch activation without logging a consent string or other unnecessary personal data.
The master live-ad eligibility result is the conjunction of environment, AdsEnabled, placement
flag, ad-free entitlement, eligible route/surface/viewport, and consent. Evaluate it before every
slot request. The account-level review script is outside that result and cannot be erased after it
executes; the kill switch therefore guarantees no new ad unit requests, not removal of the review
script.
Implementation and rollout sequence¶
- Leave the dashboard on Remind me later while site review/re-review and inert Stage 1 layout
testing continue. Follow
doc/adsense-site-review-runbook.mdbefore requesting another review. - When a live experiment is scheduled, create the three-choice Google CMP message as a draft, configure the privacy URL, branding, languages, target regions, and consent-mode behavior, and review every screen. Do not publish it in isolation from the application coordination work.
- Implement the consent coordinator and region-authority behavior with
AdsEnabledstill false. Confirm the existing banner remains the sole surface outside the CMP region and never overlaps the Google message inside it. - Implement the live-ad coordinator and one manual content-page unit. Keep Auto Ads, gameplay rail, and post-completion units disabled.
- Test with provider previews/test facilities and controlled regional scenarios. Never click live ads or automate live impressions. Include consent, refusal, granular choices, revocation, timeout, blocked scripts, no-fill, client navigation, and ad-free entitlement.
- Publish the CMP message before allowing any targeted-region AdSense request. Verify the privacy
policy's active-processing language and Settings reopening path in production with
AdsEnabledstill false. - Enable one approved content-page unit for a small stable cohort. Measure the Stage 2 metrics and exercise the kill switch before considering a wider cohort or another placement.
Required regression coverage and acceptance criteria¶
- Unit-test the full eligibility matrix, including every individual negative gate.
- Mock CMP/TCF callbacks for covered, not-covered, consented, denied, granular, timeout, and error results; assert that no unresolved/error state can request an ad unit.
- Assert exactly one consent surface appears at a time and that it does not flash from one banner to another after hydration.
- Assert the account script appears at most once on implemented-placement routes and is absent from prohibited routes.
- Assert no unit request occurs until consent and all product gates pass; prohibited routes and ad-free users must never request a unit.
- Assert refusal and later revocation stop new requests and that Settings reopens the authoritative consent surface.
- Assert client navigation and repeated Practice puzzles cannot duplicate the script or an impression request.
- Verify CSP, accessibility, mobile/desktop layout, browser zoom, performance, blocking, no-fill, and failure behavior before production targeting.
- Verify
AdsEnabled: falserestores an ad-free, fully functional site without requiring a code deployment.
Experiment sequence¶
Stage 0 — content and compliance foundation¶
- Publish useful How to Play, About, Updates, contact, and support information.
- Correct the Privacy Policy so it describes stored player, analytics, consent, and advertising data accurately.
- Add a preferences surface that can reopen and change consent.
- Decide the audience/age posture.
- Select and configure an appropriate consent-management platform before serving ads where it is required.
- Establish
ads.txt, domain ownership, publisher metadata, and provider review requirements.
These are product-trust improvements even if advertising is never launched.
Current implementation status (2026-09-13): the site metadata identifies the current AdSense
account and the root ads.txt authorizes Google as a seller. Explicit robots and sitemap metadata,
static seller-record handling, crawlable homepage/game-guide links, public Terms, distinct public
page metadata, useful game loading/error states, and accurate Google advertising disclosures now
strengthen the review surface. The shared inert gameplay layout also rehearses a 150px game-to-rail
gutter only at viewports of at least 1,600 CSS pixels. The account-level AdSense script is included
on the homepage review entry point and implemented-placement routes; it is centralized, emitted
once in the document head, and does not create or request an ad unit. The first review was unsuccessful without a
specific policy reason; see doc/adsense-site-review-runbook.md before resubmission.
Before Stage 2 can begin, add a single, centrally managed live-ad coordinator. It must request a
manual unit only after AdsEnabled, the route-specific placement flag, ad-free entitlement,
surface eligibility, and applicable CMP/consent checks all pass. The integration must support the
manual placements described here, must not enable Auto Ads, and must preserve the master kill
switch so turning AdsEnabled off prevents every unit request.
Stage 1 — house-ad layout trial¶
Target a small internal cohort with AdPreviewEnabled. That cohort sees every implemented preview
unless a placement is live-eligible for the same user, in which case the live unit replaces only
that preview. Use neutral, non-interactive simulated creative without click encouragement. Clearly
mark it ADVERTISEMENT PREVIEW and say that it is a layout test so nobody mistakes it for a live
campaign.
Test one placement at a time:
- editorial/content page;
- desktop gameplay rail;
- post-completion placement.
The purpose is to answer whether the space feels intrusive and whether it damages the layout. This stage cannot predict fill or revenue, but it can reject bad placements without sending impressions or clicks to an ad network.
Stage 2 — one live content placement¶
Enable one manually placed unit on eligible public content pages for a small external cohort. Keep active gameplay and post-completion disabled. Validate consent, delivery, blocking, performance, creative quality, reporting, and emergency shutdown.
Stage 3 — desktop rail experiment¶
Compare a stable ad-exposed cohort with a control cohort. Run long enough to cover weekday/weekend and reasonable demand variation. Do not change the board layout or add a second unit during the test.
Stage 4 — post-completion experiment¶
Only proceed if the earlier stages meet their guardrails. Run this independently from the desktop
rail at first. Specifically measure whether Play another, share, standings visits, and session
depth decline.
Stage 5 — vendor or sponsorship comparison¶
Once traffic is sufficient for credible proposals, compare the baseline with Nitro or another managed partner. Evaluate a direct sponsored themed event separately from commodity display ads; they are different products with different success metrics.
Measurement and stop conditions¶
Revenue per thousand eligible sessions is more useful than raw page RPM for an app-like game. A single browser session can contain several Practice puzzles without conventional page loads, and manufacturing route reloads merely to create impressions would be bad product behavior.
Measure:
- eligible sessions, ad requests, filled slots, viewable impressions, and net revenue;
- puzzle start and completion rate;
- Practice
Play anotherrate and puzzles per session; - result sharing and standings visits;
- return rate and Daily streak continuation;
- Core Web Vitals, particularly layout shift and interaction latency;
- route-load and game-ready time with and without the provider script;
- accidental-click indicators, rapid back-navigation, and complaints;
- consent acceptance/withdrawal and ad-blocker/no-fill behavior;
- creative, policy, privacy, and malvertising incidents.
Define thresholds before the experiment. Stop or disable the affected placement when it causes a meaningful decline in completion or return behavior, exceeds the performance budget, creates layout shifts near controls, produces inappropriate creatives, or cannot reliably respect consent and ad-free entitlement. Increased short-term revenue does not override those guardrails.
Testing checklist¶
Product and responsive behavior¶
- Phone portrait/landscape, common tablets, narrow desktop, wide desktop, and ultrawide desktop.
- Browser zoom and text scaling through at least 200%.
- Light, dark, and system color schemes.
- Keyboard-only navigation and screen-reader landmarks/labels.
- Daily, Practice, Victory, group-launched play, future round context, and error/retry states.
- No-fill, slow-fill, oversized creative, provider timeout, offline navigation, and blocked script.
- Client-side navigation, back/forward cache, hydration, and repeated Practice regeneration.
- No movement of tiles, keyboard, buttons, score, or primary actions when the slot fills or collapses.
Safety and policy testing¶
- Use house ads or a provider-supported test mode during development.
- Developers and internal testers must never click live ads or encourage others to click them.
- Do not generate artificial impressions by repeatedly refreshing or automating live pages.
- Verify sufficient separation from game controls and eliminate any plausible accidental-click path.
- Verify ads do not appear on loading-only, empty, error-only, login, settings, export/delete, or other low-content/action-only surfaces.
- Verify personalized and non-personalized modes against the chosen CMP and region rules.
- Confirm withdrawal of consent prevents subsequent disallowed requests.
- Confirm an ad-free entitlement suppresses the script and request, not merely the visible box.
- Validate Content Security Policy changes narrowly; do not allow arbitrary script origins.
- Verify that ad-provider failures never enter the application error boundary or block play.
Google's policies and provider rules can change. Recheck them immediately before implementation and before adding a new format, especially auto-refresh, sticky units, video, interstitials, or rewarded ads.
Provider and market research¶
Research checked 2026-08-15. Entry requirements and commercial terms change, are often negotiated, and do not guarantee acceptance or higher earnings. Revenue depends heavily on audience geography, viewability, device mix, season, consent, content, retention, and format density.
Google AdSense¶
AdSense is the practical first baseline: broad self-service access, manual responsive units, and no
need to negotiate a managed sales contract. Sites must be added, ownership verified, and reviewed
to reach Ready status. Approval and meaningful revenue are not guaranteed.
Start with manual placements. Automatic ads would surrender too much control before Verbolus knows which surfaces are acceptable. Google also publishes specific game-content guidance, including separation between ads and interactive controls, and prohibits encouraging or manufacturing clicks.
Relevant sources:
- AdSense site review and readiness
- AdSense ads on game-play pages
- Ad placement policies
- Invalid traffic and publisher clicks
- Google consent-management requirements
Nitro¶
Nitro is the most promising managed-network conversation for Verbolus once there is real traffic. It focuses on gaming and gaming-adjacent publishers, emphasizes publisher control over placement and ad count, scans advertising, and supports a broader programmatic stack. Its application form includes traffic bands below 50,000 monthly pageviews, but that is not a promise of acceptance or a published minimum.
Nitro documents a vetting and supply-platform approval process and recommends allowing a roughly 90-day evaluation period after launch. Confirm that it will support Verbolus's desired density—one desktop unit or one post-result unit—before integrating.
Relevant sources:
Venatus¶
Venatus specializes in gaming and entertainment and is especially interesting for later direct campaigns, branded levels, rewarded concepts, and sponsored themed events. It does not publish a simple self-service traffic threshold, so it should be treated as a sales-led partnership rather than an immediate AdSense substitute.
Its strategic value is the possibility of higher-quality, contextually designed campaigns instead of adding more generic banners. Approach it when Verbolus can present meaningful audience, geography, engagement, and rounds/tournaments inventory.
Relevant source:
Playwire¶
Playwire offers managed monetization for gaming and entertainment publishers using Google Ad Exchange, Amazon, and additional supply and demand partners. Its public materials currently give inconsistent website thresholds: one qualification page says publishers typically apply around 100,000 monthly pageviews, while its FAQ cites 500,000. Confirm the current applicable program directly rather than planning around either number.
The FAQ also says its partners generally require at least three highly viewable ads on each device, although publishers retain placement input. That density may conflict with Verbolus's desired minimal layout. Playwire is therefore a later-stage candidate only if it agrees to an acceptable format and density.
Relevant sources:
Media.net¶
Media.net provides contextual advertising associated with Yahoo/Bing demand. It may be worth testing on How to Play, Updates, and other substantial editorial pages. Its fit is less obvious for an interactive game shell, and performance may depend strongly on English-language, high-value geographies and content context.
Relevant source:
Journey by Mediavine and Mediavine Official¶
Mediavine's current approval guidance says Journey begins at 1,000 sessions, while Mediavine Official uses annual advertising revenue as an entry criterion. Both emphasize original, audience-first content, clean traffic, good standing, and a site experience that supports advertising.
Journey could become relevant to a meaningful Verbolus editorial section, but an app-like game with sparse copy should not assume acceptance or good performance. Ask explicitly whether the interactive game inventory and intentionally low ad density fit the program.
Relevant source:
Raptive¶
Raptive currently requires at least 25,000 monthly pageviews and, for sites below 100,000 monthly pageviews, at least 50% traffic from the United States, United Kingdom, Canada, New Zealand, and Australia. It also expects the majority of content to be long-form and original. That makes it a poor current fit unless Verbolus develops into a substantial content publication alongside the games.
Relevant source:
Ezoic¶
Ezoic's published standard requirement, updated in February 2026, is generally 250,000 monthly active users. Smaller sites may apply to a limited Incubator program. This is not a near-term path and provides no reason to design the current UI around its formats.
Relevant sources:
Direct sponsorship¶
Direct sponsorship is not a drop-in ad network and requires an audience, sales work, contracts, creative review, invoicing, measurement, and campaign support. It nevertheless offers the best long-term fit for themed rounds and tournaments because Verbolus controls the sponsor, creative, density, timing, and surrounding experience.
Potential inventory includes:
- a sponsored seasonal Nine or Eighteen;
- a language- or culture-themed course;
- an event landing and final recap sponsor;
- a sponsor-funded free puzzle pack;
- a clearly labeled prize or badge sponsorship, subject to contest and platform rules.
Do not promise individual word choices, easier puzzles, scoring influence, user data, or access to private group activity.
Adjacent tools that are not direct substitutes¶
- Google Ad Manager is primarily an ad-serving and inventory-management layer. It can later combine direct sponsorship, AdSense/Ad Exchange, and other demand, but it does not automatically provide a better-paying audience.
- Google AdMob is intended for native mobile-app inventory. Reassess it only if Verbolus ships a genuine native or Store-packaged app with an eligible integration; it is not the normal browser PWA solution.
- A managed network may still use Google Ad Exchange underneath. Switching the publisher relationship does not necessarily remove Google demand.
Vendor evaluation questions¶
Obtain written answers before accepting a managed-network proposal:
- What traffic threshold, geography mix, and contract term apply to this property?
- Is there exclusivity, a minimum number of placements, or a minimum ad density?
- Can Verbolus use only one desktop rail or one post-result unit?
- Who controls sticky, video, interstitial, auto-refresh, and anchor formats?
- What is the publisher revenue share, reporting basis, payment threshold, and payment schedule?
- Which demand partners and reseller relationships are used?
- What controls exist for advertiser categories, sensitive content, malware, redirects, and poor creative quality?
- Can the network guarantee that private group, Settings, and active mobile gameplay routes remain excluded?
- How are consent, IAB TCF, regional privacy signals, and deletion requests handled?
- What scripts run, what data is collected, and what performance/availability commitments exist?
- Can Verbolus run house campaigns and direct sponsorship through the same ad server?
- What happens to tags, data, and unpaid revenue when the contract ends?
- Is policy support available when a creative or account issue requires immediate shutdown?
Compare proposals using net revenue per eligible session, UX constraints, latency, control, and operational risk—not a headline CPM alone. A higher page RPM achieved by adding three units, sticky video, or more refreshes is not an equivalent product.
Initial decisions¶
- First visual test: inert house ads behind
AdPreviewEnabled. - First real provider: AdSense as a manually placed baseline, subject to approval and compliance.
- First live surfaces: How to Play and substantial Updates articles; desktop gameplay rail only after the content integration is stable.
- About uses a supporter link rather than third-party ads; Privacy remains ad-free.
- Mobile gameplay: ad-free.
- Victory overlay and Practice loading state: ad-free.
- Private Groups, Settings, account, privacy, export/delete, and payment surfaces: ad-free.
- First managed-network conversation: Nitro.
- Later gaming partners: Venatus for sponsorship/direct campaigns and Playwire for scaled managed programmatic inventory.
- Preferred mature model: supporter membership plus restrained sponsorship, with commodity display ads remaining sparse and removable.
These are reversible product decisions. Revisit them using measured retention, performance, creative quality, audience geography, provider terms, and supporter/sponsorship demand rather than assuming display advertising must expand as traffic grows.