Entry List Display

The entry list shows every entrant — name (or initials), ticket numbers, entry date — on each competition page. It’s pure transparency: customers can see who’s playing and that draws are filling up. Some operators love it; some prefer privacy.

The case for showing it

• Social proof. Seeing 200 names already entered drives FOMO and last-minute purchases. Quantified by Lucky Turbo A/B tests at +8–12% paid-order conversion.
• Trust signal.Hidden entrants “could be fake” in customer perception. Visible entrants prove the draw pool is real.
• Engagement. Customers refresh the page to see their own ticket number land — small dopamine loop.

The case for hiding it

• Privacy. Even with name redaction (initials only), some customers prefer their participation invisible. UKGDPR permits showing names but only if you disclose it at signup.
• Manipulation concerns. A visible entry list theoretically helps colluders. In practice, ticket-cap and per-user limits make this irrelevant for raffle-scale.

Setting the default

Raffle admin → Settings → Show the entry list on each competition page by default. On = the entry list is visible on every competition unless the admin disables it per-competition. Off = the entry list is hidden by default and an admin must opt in per-competition.

Most Turbo IT tenants leave it ON — the social proof gain outweighs the privacy concern, and we redact to first-name + last-initial by default (“Sarah K.”).

What renders

A scrollable list grouped by buyer:

• Display name (first name + last initial — “Sarah K.”)
• Ticket numbers — if a single buyer has multiple tickets they show on one line (“Tickets #14, #15, #16” or “12 tickets (#14, #15, #16 + 9 more)” for big orders).

Shows the 200 most recent entrants with a “Total entries above” note for the rest. Total entrant + total ticket counts always shown at the top.

Customer opt-out

Customers can hide their display from entry lists at /account/profile→ the “Show my name on entry lists” toggle. Opted-out customers render as “Anonymous entrant #N”(separate row per ticket so the user_id can’t be inferred), with their ticket numbers still visible — legal requirement for transparency.