Skip to content
USD · EUR Crypto rails

Catalog intake

List with W3Gamble

Propose an operator for the catalog, or buy a labeled Sponsored pin / AdSlot creative. We review public payment sources the same way for every submission - declared vs checked facts only.

Packages

Pricing is quoted by email. Sponsored placements are never stealth-ranked as editorial “best”.

  • Catalog listing

    Standard intake into the static catalog: declared vs checked payment facts, network/coin slices, and /go/ affiliate CTA when a partner link is live.

    • Operator card under the matching vertical
    • Inclusion in eligible network and coin slices
    • Affiliate exit via /go/{slug} when configured
    Request catalog listing
  • Sponsored pin

    Paid placement at the top of agreed catalog scopes. Always labeled Sponsored - never sold as an editorial “Best” rank.

    • Pin order in selected scopes (casino, betting, esports, home)
    • Visible Sponsored badge on list rows and the operator card
    • Optional Featured module on hub pages (home, slots, No-KYC, …)
    Request sponsored pin
  • Ad creative

    Banner creative in reserved AdSlot positions (home, catalog, intent, operator mid). Empty slots stay invisible until sold.

    • Leaderboard or panel format by slot
    • Your landing URL and short pitch copy
    • Shipped in the next static build after approval
    Request ad creative

What we look for

  • Clear public sources for fees, KYC policy, and withdrawal terms - not marketing claims alone.
  • Networks and coins that match what the cashier actually labels.
  • Enough source detail to keep declared and checked columns honest.

How to suggest a listing

Use Contact (topic: Catalog listing) or email hello@w3gamble.com with subject "Listing suggestion". Include:

  • Live site URL and brand name
  • Operator type: casino, sportsbook, or esports
  • Supported networks and coins
  • Public KYC policy URL
  • Public withdrawal / cashout terms URL
  • Editorial contact email
  1. Suggestion enters the editorial intake queue (not auto-published).
  2. We review sources against methodology - declared stays declared until checked.
  3. Approved facts enter the operator data files used by the static build.
  4. You get the live page URLs for the card, slices, and compare pairs when published.

Read methodology first. Empty catalog slices are never generated without a verified rail and at least one active listing.