◉The Wins Feed Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the bands beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. That matters on this desk in particular: the subject is how much a wins display leaves out, and this site carries commercial marks of its own. No operator, game, studio, streamer or regulator is named, rated or recommended anywhere on this site.
The Wins Feed / The notification
Desk 65 - the wins you are shown

The message that says you won

The wins display that reaches a reader away from the site is the notification, and it is triggered far lower than any lobby feed. Its bar is set so that it fires often, which is exactly what makes it a poor summary of a week.

Feed stub
Fires at
5x or more
Rate
1 in 26 spins
Per session
15.4 messages
Lottery language
never used by name
the barThe multiple a win must reach to be eligible for the display - on the sample, 250 times the stake
the poolThe players and spins the rows were drawn from - on the sample, 4,750 players placing 1,900,000 spins in the hour
the intervalThe hours between one player's own qualifying wins - on the sample, 10.4 hours at 400 spins an hour
Direct answerA win notification fires on a win above a low bar - on the sample, five times the stake, which happens once in 26 spins - so a 400-spin session generates about 15.4 of them. The messages are individually true and collectively misleading, because they carry only the winning rounds out of a session that may still have ended lower.

The bar behind the message

A notification has to fire often enough to be worth sending, which pushes its bar well below a feed’s. The same session that produces one celebration at 25-times produces fifteen messages at five times.

Two bars on one sessionspins in the session                    400
notification bar                          5x   -> 1 in 26 spins
  messages expected         400 / 26 = 15.4
celebration bar                          25x   -> 1 in 380 spins
  celebrations expected    400 / 380 = 1.05
feed bar                                250x   -> 1 in 4,155 spins
  feed rows about the reader      400 / 4,155 = 9.6%
  of which the feed shows                2.6%
  so 400 / 4,155 x 2.6% = 0.010 rows per session

Three displays, three bars, three entirely different pictures of one session. That is the mechanism of this desk in a single table: the display fixes the bar, and the bar fixes what a reader is told.

The message against the week

A player who reads fifteen win messages and a balance that is down has not been misinformed about any individual round. They have been shown one side of a ledger, repeatedly, in a channel that never sends the other side.

What the message measures

One round, above a low bar, and nothing else. It has no field for the session, the week or the account, and it cannot have one, because its trigger is a round.

What it costs to send

Almost nothing, which is why the bar can be low. A notification has no column inches to fill and no reader to hold, so it can be sent on a signal a feed would never bother to show.

How it reaches you

By push, e-mail or an in-app banner. The channel itself - what an app may prompt for and what a refusal routes to - is another desk’s subject; the message’s bar is this one’s.

Practical responses