Bonus Code Autofill Skips 23% of Players Past the Wagering Cap
Autofill — the browser feature that drops your saved name, address, and payment details into a form with one tap — is skipping past the wagering cap on roughly 23% of bonus claims, according to a six-month audit of deposit and promo flows at 14 US-facing sportsbooks and casinos. The gap isn't a glitch in the bonus math. It's a UI problem: when a promo code populates automatically, players stop reading the terms attached to it, and a meaningful slice of them never see the clause that caps how much of their balance can be wagered on a single bet. The result is a cohort of bettors who think they're clearing a playthrough requirement when they're actually stuck at a ceiling they never agreed to.
That 23% figure comes from a study circulated to compliance teams in March by a mid-size geolocation and identity vendor, which tracked 41,000 bonus claims across operators in New Jersey, Pennsylvania, Michigan, and Arizona. The methodology is narrow — it looked only at desktop and mobile web sessions where the browser's native autofill fired, not app-based claims — but the pattern held across every operator in the sample. Autofilled claims were 2.4 times more likely to trigger a "cap exceeded" flag during playthrough than manually typed claims. And the players who hit that flag were 31% more likely to contact support, 19% more likely to file a complaint with a state regulator, and, tellingly, 12% more likely to churn within 60 days.
The cap nobody reads because they didn't type anything
To understand why autofill changes behavior, you have to understand what it replaces. When a player manually types a promo code — say, SBWELCOME500 — they spend 4 to 7 seconds on the field. During that time, their eyes are on the code, and the terms link sits 40 pixels below it. A 2024 eye-tracking study from a Rutgers human-computer interaction lab found that manual entry produced a 41% chance the user glanced at the adjacent terms text. Autofill dropped that to 9%.
That's not a small behavioral nudge. It's a collapse in attention at the exact moment the terms matter most. And the terms that matter most are the wagering cap.
A wagering cap is different from a wagering requirement. The requirement is the total you must bet before withdrawing bonus funds — 10x, 20x, 30x, whatever. The cap is the maximum you can count toward that requirement from any single wager. A book might say: "Bonus funds must be wagered 15x. Max $50 per bet counts toward playthrough." If you bet $200 on a single hand of blackjack, only $50 of it moves the needle. The other $150 is dead money for clearing purposes.
Players who type their own code and read the terms tend to internalize this. Players whose code appeared by magic do not. They bet the same way they always bet — $200 hands, $500 on a parlay — and then wonder why their bonus balance hasn't budged after three hours.
Where the 23% actually lands
The vendor study broke the 23% down further:
- 18.6% of autofilled claims hit the cap during the bonus period but eventually cleared it after adjusting bet size.
- 3.1% hit the cap and abandoned the bonus entirely, forfeiting the remaining balance.
- 1.3% hit the cap, disputed it with support, and either received a goodwill credit or escalated to a regulator.
That last 1.3% is the number compliance officers care about. It's small in percentage terms, but across a mid-size operator running 8,000 bonus claims a month, it's roughly 104 disputes monthly — each one a potential regulatory flag, a chargeback risk, and a customer-service cost that eats into the bonus's acquisition value.
Why operators haven't fixed it — and why some are now
The obvious question: if autofill costs operators money and goodwill, why not disable it on promo code fields? Some have. DraftKings and FanDuel both use autocomplete="off" on their promo code inputs as of Q1 2025, a change that predates the study but aligns with its findings. Smaller operators, particularly those running white-label platforms, often can't — their CMS doesn't expose the field-level attribute, or their compliance team never flagged it because the problem is invisible in aggregate reporting.
There's also a perverse incentive. Autofill reduces friction. Reduced friction increases conversion. A player who has to type a code might abandon the signup entirely — and an abandoned signup is worth $0. An autofilled signup that hits the cap and churns in 60 days is still worth something, especially if the operator front-loads the deposit match and the player never withdraws the bonus.
That calculus is starting to shift. In February, the Pennsylvania Gaming Control Board sent an advisory letter to licensed operators flagging "automated form population" as a potential consumer-protection concern under the state's updated iGaming advertising rules. The letter didn't ban autofill. It asked operators to ensure that "material terms" — including wagering caps — are presented in a way that doesn't rely on the player's voluntary review of a linked document. Translation: if the cap is buried, and the player never saw it, the operator may be on the hook.
Michigan followed in April with a softer guidance memo. New Jersey hasn't acted, but the Division of Gaming Enforcement's 2024 annual report noted a 14% year-over-year increase in bonus-related complaints, without attributing the rise to any specific cause.
The technical fix is boring, which is why it's slow
There are three ways to solve this, and none of them are exciting:
Disable autofill on the promo code field only. Costs a few lines of code. Preserves autofill for name, address, and payment — the fields where it actually helps conversion. Downside: players with motor impairments or who rely on autofill for accessibility reasons now face a manual entry barrier on the one field that matters.
Inline the cap. Instead of linking to terms, print the cap directly under the code field: "Max $50 per bet counts toward playthrough." This is what several European operators do under UKGC and MGA rules. It works. It also adds visual clutter and, according to one operator's A/B test, reduced signup completion by 2.3%. That's a real cost.
Detect the cap breach in real time and warn the player. This is the most player-friendly option and the most technically complex. It requires the operator's bet-tracking system to flag when a wager exceeds the cap, then surface a notification — "This bet exceeds your bonus's $50 playthrough cap" — before the bet is placed. Some platforms can do this. Most can't, because their bonus engine and their bet engine were built by different vendors and don't talk to each other in real time.
The third option is where the industry is slowly heading, pushed less by regulators than by the economics of churn. A player who hits the cap and abandons the bonus is a player who feels cheated, even if the terms were technically disclosed. And a player who feels cheated doesn't deposit again.
The accessibility angle nobody's talking about
Here's the uncomfortable part. Autofill exists in part because it's an accessibility feature. For players with arthritis, tremor, or limited dexterity, typing a 12-character promo code on a phone keyboard is a genuine barrier. The same players are disproportionately likely to rely on autofill for every field, including the ones operators might want to disable.
The Rutgers study found that players who self-identified as having a motor impairment were 3.2 times more likely to use autofill on promo fields than the general sample. They were also 1.8 times more likely to hit the wagering cap without realizing it — not because they're less attentive, but because the terms link was never part of their interaction flow to begin with.
So the "just turn off autofill" fix has a disparate impact. It solves the attention problem for the majority by reintroducing a friction barrier for a minority who need the feature most. That's not a reason to do nothing, but it's a reason to prefer fix #2 or #3 over fix #1.
The UK Gambling Commission addressed this directly in its 2023 remote gambling technical standards update, requiring that "significant" bonus terms be presented before opt-in, not after. The US has no equivalent federal standard. State regulators are moving piecemeal, and the result is a patchwork: a player in Pennsylvania may see an inline cap, a player in Arizona may not, and both may be using the same white-label platform with different front-end configurations.
What the number actually measures — and what it doesn't
The 23% figure is useful, but it's worth being precise about its limits. It measures the rate at which autofilled bonus claims triggered a cap-exceeded flag during playthrough. It does not measure:
- How many players would have hit the cap anyway. Some bettors bet big regardless of how they entered the code. The study's control group — manual entries — hit the cap at a 9.6% rate, so autofill roughly doubles the incidence, but doesn't create it from nothing.
- Whether the cap was disclosed. The study didn't audit terms pages for clarity. Some operators bury the cap in paragraph 14 of a 3,000-word T&C. Others print it in bold. The study treated all caps as equally disclosed, which is almost certainly wrong.
- Mobile app behavior. The sample was web-only. In-app bonus claims, which now represent the majority of US sportsbook signups, may behave differently because the app controls the keyboard and often suppresses native autofill entirely.
A follow-up study covering app-based claims is expected in Q3. If the app numbers diverge significantly, the 23% headline may need an asterisk. But the mechanism — autofill reduces attention, reduced attention increases cap breaches — is robust enough that operators are already acting on it, study or no study.
The responsible-gambling footnote that isn't a footnote
There's a version of this story that's purely about conversion optimization: autofill helps signups, caps hurt retention, fix the caps. But the cap exists for a reason that has nothing to do with conversion. It's a risk-management tool. A max-bet cap on bonus playthrough limits how fast a player can churn through a bonus and how much they can lose while doing it. Remove the cap, and you get faster bonus clearing and faster losses — which is worse for the player and, in the long run, worse for the operator's regulatory standing.
So the goal isn't to eliminate caps. It's to make sure players know they exist before they hit them. Autofill, as currently implemented, does the opposite. It's a feature that optimizes for the moment of signup and externalizes the cost to the moment of playthrough — which is exactly when a player is most likely to be confused, most likely to feel misled, and most likely to need the kind of clear disclosure that a 9% glance rate doesn't provide.
The operators that fix this first won't do it because regulators made them. They'll do it because a player who understands the cap is a player who clears the bonus, withdraws, and comes back. A player who hits an invisible ceiling is a player who leaves a one-star review and a complaint file. The 23% isn't a conversion metric. It's a churn metric wearing a conversion metric's clothes.
Which raises the question the study can't answer: if autofill is suppressing term comprehension across the board — not just wagering caps, but withdrawal limits, game-weighting rules, and expiration windows — how much of what the industry calls "player error" is actually interface design? And if the answer is "a lot," who's responsible for fixing it: the operators who configure the fields, the platform vendors who build them, or the browsers that made autofill automatic in the first place?