SlotDeck Methodology

Slot Data Methodology

SlotDeck combines reviewed game facts with stored observations from connected sources. This page explains where those values come from, what they mean, and where their limits begin.

Methodology version 1.0 · Reviewed August 25, 2026

Data pipeline

From source to screen.

Each layer has a defined job. A source record never becomes public or index eligible simply because it exists.

01

Source

Approved catalog facts and observed activity originate in the connected source warehouse. SlotDeck does not alter its ingestion workers or raw records.

02

Select

Server-only adapters request narrow, allowlisted projections. Private identities, raw event payloads, credentials, and operational records stay outside the public product.

03

Validate

Types, identifiers, ranges, timestamps, image hosts, and source relationships are checked. Missing values remain missing instead of being estimated.

04

Present

SlotDeck labels the time window and shows descriptive observations. Publication and search eligibility remain separate review decisions.

Source ownership

One page, several distinct data jobs.

SlotDeck keeps demo delivery, game facts, activity measurements, and editorial decisions separate.

InformationApproved sourceExamplesPublic boundary
Game identity and specificationsApproved server-side catalog projectionName, provider, RTP, volatility, reels, paylines, maximum win, release dateOfficially verified source fields take priority. Otherwise SlotDeck uses the latest curated source-catalog snapshot, rejects out-of-policy values, and leaves missing specifications missing. Demo-supplier fields are excluded.
Tracked activityBounded server-side activity aggregates30-day plays, 7-day plays, daily activity, active days, largest observed multiplierThese are observations from connected sources, not the whole market and not a prediction of future results.
Recent resultsRestricted server-side live projectionGame, observed multiplier, permitted amount, source, timestampPlayer identifiers and raw event payloads are excluded. Unsupported or invalid monetary values are suppressed.
Demo availabilitySlotDeck mapping with SlotsLaunch deliveryApproved demo ID, active status, launch URLThe demo supplier delivers the demo session and artwork mapping only. It is never used for SlotDeck editorial copy, rankings, or displayed game specifications.

Reading the numbers

Useful only when the label is clear.

Observed activity and catalog game specifications are not interchangeable. The label beneath a value tells you which kind of information you are reading.

01Tracked plays
The count of qualifying play observations recorded for a game during the stated window. It is not a count of unique people.
02Largest multiplier
The largest result observed in the selected sample. It is different from a provider-published maximum win and does not indicate what will happen next.
03Tracked casinos
The number of connected source identities represented in the sample. It does not state that an operator is available or licensed in your location.
04EUR amounts
Shown only when the source value is genuinely in EUR or a supported value has been converted server-side using a documented official ECB reference rate.

Known limits

What the data cannot tell you.

The most important part of a methodology is the point where its claims stop.

Coverage is partial

Connected sources do not represent every casino, player, game session, or market.

Activity is historical

Recent popularity and large observed wins cannot forecast the next spin or improve the odds of a game.

Samples vary

Source coverage, game availability, and sample size can change from one game and day to another.

Facts have different owners

A provider-published specification and an observed SlotDeck metric answer different questions and are labeled separately.

Freshness and failure

A missing value is better than a false one.

Time-sensitive modules show their measurement window or update time. If a required connection fails, SlotDeck returns an unavailable or empty state instead of presenting stale fallback figures as current.

Material changes to a game fact, source relationship, methodology, or publication right require review. Sync activity cannot automatically promote a record into a public or indexable page.

How to use slot data responsibly