US Online Casino (iGaming) Revenue by Operator & State

US Online Casino (iGaming) Revenue by Operator & State

Monthly online casino revenue from state regulators in one schema, with each operator share of the state online casino GGR. Pennsylvania splits online slots, banking tables and poker.

Here is one real record from this actor.

{
  "state": "CT",
  "section": "Online casino",
  "operator": "Mohegan Digital, LLC",
  "brand": null,
  "month": "2026-09",
  "wagers_usd": 929253183,
  "ggr_usd": 35854935,
  "taxable_revenue_usd": 30476694,
  "tax_usd": 5485805,
  "ggr_share_pct": 53.49,
  "source": "State gaming regulators (CT, MI, PA)",
  "source_url": null,
  "observed_at": "2026-10-30T22:38:03.327Z"
}

Input | Output | Pricing

Table of contents

• What you get
• Input and filters
• Use cases
• Coverage and freshness
• Pricing
• Comparison with other Apify actors
• Related JackpotLedger actors
• FAQ
• Run it through the Apify API

What you get

One record per state, section, operator and month with wagers when reported, gross gaming revenue, taxable revenue, state tax and share of state GGR.

Each record can carry these 14 fields. A field the source does not publish for a record comes back as null.

Field	Type	Description
state	string	US state
section	string	Report section: Online casino (CT, MI) or Interactive Slots, Banking Tables, Poker (PA)
operator	string	Licensed operator or casino as reported
brand	string	Platform or brand when reported (Michigan)
month	string	Month (YYYY-MM)
wagers_usd	integer	Wagers when reported (CT, PA)
ggr_usd	integer	Gross gaming revenue
taxable_revenue_usd	integer	Taxable or adjusted revenue
tax_usd	integer	State tax or payment
ggr_share_pct	number	Share of the state online casino GGR for that month (computed)
source	string	Publisher of the official data
source_url	string	Public page where the publisher shows this data
observed_at	string	Time this record was collected (ISO 8601, UTC)
error	string	Only present on the single no-data or failure record. That record is never charged.

Input and filters

All inputs are optional.

Field	Type	Required	Default	Description
states	array	no	(none)	States to include. Leave empty for Connecticut, Michigan and Pennsylvania. Values: CT, MI, PA.
monthFrom	string	no	(none)	First month to include, as YYYY-MM. Leave empty for everything in the latest reports.
monthTo	string	no	(none)	Last month to include, as YYYY-MM. Leave empty for the latest month.
operators	array	no	(none)	Optional name filters, for example FanDuel, DraftKings, BetMGM, Mohegan, PARX.
years	array	no	(none)	Optional calendar years for Michigan history, for example 2024. Leave empty for the latest Michigan report.
maxRecords	integer	no	500	Maximum number of monthly records. Newest month first.

A working example to paste into the Input tab:

{
  "monthFrom": "2026-07",
  "maxRecords": 25
}

Use cases

• Compare online casino revenue across Connecticut, Michigan and Pennsylvania.
• See GGR market share per operator with ggr_share_pct.
• Follow taxable revenue and tax for sector research.

Coverage and freshness

Connecticut (monthly, open data), Michigan (monthly workbooks, current and previous year by default) and Pennsylvania (current fiscal year, July to June). More states will be added.

Pricing

This actor uses pay-per-event pricing. These are the current Apify prices, read on 2026-11-06.

Event	Price	When it is charged
result	$0.015	Each record delivered to your dataset
apify-actor-start	$0.003	When a run starts, once per GB of run memory with a minimum of one

At the default 512 MB, a run that delivers 100 records costs $1.503.

• Apify asks for a maximum spend of at least $0.018 per run on this actor.
• Accounts on the free Apify plan receive up to 10 results per run.
• If nothing matches or the source fails, you get one row with an error field and no result charge. The start event still applies to the run.
• Set a maximum cost per run and the actor stops delivering results when it reaches that limit.

Comparison with other Apify actors

No dedicated actor for this source on the Apify Store as of November 2026. We searched the public Store on 2026-11-06 with queries including "online casino revenue", and we reviewed the listings for this source and data type. Store listings change, so run the same search before you rely on this.

Related JackpotLedger actors

Other public JackpotLedger actors for the same buyer:

• US Sports Betting Market Share by Operator & State: gaming revenue data across states
• Foxwoods & Mohegan Sun Slot Revenue: Payout % & Hold: gaming revenue data for Connecticut
• Connecticut Online Casino Revenue: iGaming GGR & Hold: gaming revenue data for Connecticut
• Connecticut Sports Betting Revenue: Handle, GGR & Hold: gaming revenue data for Connecticut

FAQ

What can I filter by?

The input accepts states, monthFrom, monthTo, operators and years. The Input and filters section explains each one.

Can I run it on a schedule?

Yes. Create an Apify schedule for the actor, then send the dataset to your database, a spreadsheet or a webhook.

Run it through the Apify API

Replace <TOKEN> with your Apify API token.

curl -X POST "https://api.apify.com/v2/acts/jackpotledger~us-igaming-revenue-multistate/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"monthFrom": "2026-07", "maxRecords": 25}'

With the Apify CLI:

$apify call jackpotledger/us-igaming-revenue-multistate --input '{"monthFrom": "2026-07", "maxRecords": 25}'

Every run writes to a dataset that you can export as JSON, CSV or Excel from the Storage tab or through the Apify API.

---

JackpotLedger is an independent data provider and is not affiliated with any lottery, regulator or operator named on this page. Always confirm winning numbers and prize details with the official source.