FTD Boost · field note archive
Field Note Archive
Every earlier FTD Boost field note lives here so the homepage stays fast and the current week stays readable. Notes are kept as published, oldest first. The newest notes stay on the homepage, and the wider acquisition stack is at TrafficPopcorn.
Daily field note · 13 October 2026 · FTD Boost
FTD Benchmarking: Five Account Signals That Explain Deposit Gaps
Most FTD programs benchmark the wrong end of the funnel. Before optimising creatives, read five player-account signals that already exist in your data: KYC drop-off points, deposit method coverage by market, bonus term clarity, first-deposit timing, and repeat-deposit depth by acquisition source.
Profile KYC drop-off by step
Instrument every verification stage. A spike at document upload or address verification is a product fix, not a traffic fix, and it silently caps every downstream metric.
Check deposit method coverage per GEO
A qualified player without a familiar deposit method is not a conversion problem, it is a coverage problem. Review method availability against your top three markets monthly.
Benchmark repeat deposits, not just the first
Segment players by source and creative, then compare deposit depth at 30 days. Cheap first deposits with no repeat activity are usually a mix giveaway, not a win.
Next step: Fold account signals into the TrafficPopcorn measurement stack, then read them beside PWA cohort data, pre-lander quality, and consented re-engagement.
Daily field note · 14 October 2026 · FTD Boost
Bonus Term Clarity: The Cheapest FTD Lift You Have Not Tested
Teams spend on new creatives while the deposit page quietly loses players to unanswered questions. This field note frames bonus term clarity as a conversion lever: state the three terms hesitant players look for, keep the promise consistent from creative to cashier, and track first-deposit remorse alongside FTD count.
Show the three terms that matter before the cashier
Bonus cap, wagering requirement, and eligible games, written in one plain sentence near the deposit form. Every term found late becomes a support ticket or an abandoned session.
Keep the promise consistent from creative to lobby
If the ad says a 100% match, the pre-lander, the operator page, and the cashier must all confirm it before the player has to ask. Mismatch at any step converts intent into doubt.
Track first-deposit remorse, not just FTD count
Watch repeat-deposit rate by variant: clarity may slightly slow the first deposit and still win at 30 days, because the player who deposited informed stays longer.
Next step: Add term-clarity tests to the TrafficPopcorn measurement stack, then read them beside PWA cohort data, pre-lander quality, and consented re-engagement.
Daily field note · 15 October 2026 · FTD Boost
Casino FTD Friction: Three Cashier Fixes Before Touching Creative
Committed players still abandon at the cashier. Before spending another budget dollar on creative, audit the deposit flow itself: local method coverage, amount friction, and mid-flow verification surprises.
Audit deposit methods per GEO monthly
A qualified player without a familiar method does not convert, they leave. Match coverage to the top devices and markets in your acquisition mix, not to whatever the PSP bundle happens to include.
Remove amount friction
Pre-fill sensible amounts, show minimums and limits before card entry, and never let a player discover a limit after typing payment details. Every rejected attempt is a deposit you already paid traffic for.
Front-load verification
Move KYC steps to registration where regulation allows, so the cashier is only the cashier. Surprises mid-deposit convert intent into support tickets and abandoned baskets.
Next step: Instrument the cashier funnel in the TrafficPopcorn measurement stack, then read drop-off beside PWA cohort data, pre-lander quality, and consented re-engagement.
Daily field note · 16 October 2026 · FTD Boost
KYC Timing: Where Ready Depositors Quietly Walk Away
The player made it through the ad, the pre-lander, and the sign-up. Then the cashier asks for a passport photo before the first deposit lands. This field note covers where verification belongs in the funnel, and where it silently kills conversions already paid for.
Verify silently at registration
Electronic checks against registration data clear most players before they ever reach the cashier. Asking for documents only from the exceptions keeps the funnel wide for everyone who would have deposited.
Tier checks by deposit amount
A small first deposit rarely justifies a full document request, and regulation in most markets allows thresholds. Segmenting KYC by amount and risk keeps small FTDs frictionless while routing genuine review cases to a dedicated flow.
Never block the first credited wager
Every hour between a successful deposit and a playable balance invites a chargeback request and a lost player. When manual review is unavoidable, clear the balance and restrict the withdrawal, not the game.
Next step: Audit your KYC placement against deposit funnels on the TrafficPopcorn acquisition stack, then compare against PWA journeys, pre-lander variants, and push re-engagement.
Daily field note · 17 October 2026 · FTD Boost
First Deposit Sizing: Small Deposits Are Still FTDs
Cautious players do not convert because of bigger bonuses; they convert when the first deposit feels safe. This field note covers deposit sizing at the cashier, where casino FTDs quietly leak.
Preselect the smallest safe tier
A preselected low tier with a clear bonus match lets a nervous player complete a transaction they feel in control of. High minimums bounce exactly the traffic that a small deposit would have converted once trust was established.
Show the withdrawal terms before the money moves
The moment players fear they cannot withdraw, deposits stall. Stating the terms, the verification steps, and any fees before the cashier converts better than any bonus banner tested after it.
Treat the first deposit as onboarding, not revenue
A small first deposit sizes the second one. Operators that optimize the first transaction for completion rather than amount see repeat deposit rates carry FTD numbers upward within the first month.
Next step: A/B first-deposit tiers on the TrafficPopcorn conversion stack, then track cohort quality against installed PWA players, push re-engagement, and pre-lander journeys.
Daily field note · 18 October 2026 · FTD Boost
Post-FTD Onboarding: Own the First 24 Hours
Celebrating the FTD is the mistake; the metric that funds the program is the second deposit. This field note covers the first day after the first deposit.
Confirm, clarify, do not bury
When the deposit lands, the welcome flow should confirm it plainly and show the bonus state without fine print archaeology. Wagering confusion in hour one becomes support tickets in hour two and chargebacks in week four.
Match games to the first session
What the player actually opened in session one is the strongest game-match signal available. Surface one or two similar titles in the first-day flow: discovery by suggestion feels like service, while a generic lobby dump feels like abandonment.
Time the deposit-two trigger
Pace the second-deposit offer against volume fatigue: one well-timed reminder, quiet hours respected, over the first day. Pair it with push where consent exists, and let the offer reference the bonus they used, because familiar terms convert faster than novel ones.
Next step: Map the first-day journey on the TrafficPopcorn conversion stack, then align it with installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 19 October 2026 · FTD Boost
Deposit Retry Flows: Rescue the FTD
Acquisition hands the funnel a player mid-deposit, and the payment page drops them on a generic decline. This field note covers the recovery flow that keeps won FTDs from evaporating.
Offer the alternative inside the failure
The failed-deposit screen is the most valuable error page in the funnel. Replace fatal copy with a same-method retry plus the two next-best payment options, pre-qualified for the player region. Same-session method switches recover deposits that tomorrow never will.
Say what actually went wrong
Insufficient balance, issuer declined, verification needed: name the failure where the message allows it. Vague error copy forces the player to guess, guessing becomes a support ticket, and tickets decay into abandoned players.
Nudge with a schedule, not a spam loop
Follow the abandoned method with one immediate prompt, an in-the-hour nudge, and a next-day reminder referencing the exact amount attempted. Every extra unstructured retry teaches the player that depositing here is work.
Next step: Chart the failed-deposit journey on the TrafficPopcorn conversion stack, then connect recovered FTDs to installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 20 October 2026 · FTD Boost
Abuse Screening: Stop the Fraud, Not the FTD
Every anti-fraud rule written in anger costs a quiet tax of real deposits. This field note covers calibrating bonus-abuse screening so it filters the abusers and waves the players through.
Score in the background
Device, payment, and behavioural checks should run invisibly for the vast majority, flagging only patterns that genuinely resemble multi-accounting or promo farming. The honest player with a shared household device or a new e-wallet should never learn a rule exists.
Step up instead of stopping
A flagged deposit deserves verification, not extermination. Route it to a quick additional check, hold the bonus rather than the session, and measure how many flagged players clear. A rule nobody legitimately passes is a conversion leak with a security badge on it.
Price the false positive
Give every rule a monthly review against two numbers: fraud saved and FTDs denied to honest players. Retune anything that blocks more real revenue than abuse, and let the paid traffic quality decide how tight the net needs to be.
Next step: Calibrate screening thresholds on the TrafficPopcorn conversion stack, then read approved FTD quality against installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 21 October 2026 · FTD Boost
FTD Speed: Engineer the First-Deposit Gap
Two operators with identical FTD rates can hold very different books, if one converts players in two hours and the other in two days. This field note covers the clock between sign-up and salvo, and how to engineer it shorter.
Segment the gap, then attack the longest stretch
Chart the median hours from registration to deposit. Most of the gap concentrates in one or two stretches: between landing and registration, or between registration and the cashier arriving in front of the player. Fix the biggest stretch first, not the most visible one.
Intent decays on a curve
Conversion probability falls steeply in the first hours after sign-up. Time the first push, the welcome flow, and the first email to the point where the intent is still warm, and bring the cashier prompt forward instead of hiding it behind onboarding tours.
Measure the intent halo
Fast FTDs usually predict retention, so read speed cohorts as a quality signal for media buyers and affiliates too. Traffic sources that convert fast tend to be doing honest message-matching upstream.
Next step: Instrument the gap on the TrafficPopcorn funnel stack, then close the loop with installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 22 October 2026 · FTD Boost
FTD Payments: Match Rails to the Geo
Two identical funnels can post FTD rates ten points apart for one reason: the first payment option on the cashier. This field note covers tuning the method mix so the geo you bought is the geo that can actually fund.
Serve the rail the player already trusts
UPI-first for India, wallets and cash vouchers for LATAM, cards plus familiar e-wallets for the UK, Germany, and Canada. Defaulting every market to the same card form quietly taxes conversion in exactly the geos where growth is cheapest.
Order by conversion, not by margin
Processing deals are real but they are downstream of the FTD. Rank visible options by measured funding success per geo and revisit the order monthly, because rail trust shifts faster than procurement does.
Recover the cashier-shy
Instrument abandonment at the payment step separately from sign-up abandonment, and trigger push or email with the right rail surfaced the second time. A funding attempt is the warmest lead in the funnel.
Next step: Reorder the rails on the TrafficPopcorn funnel stack, then measure the lift alongside installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 23 October 2026 · FTD Boost
FTD KYC: Friction Is Local
Verification is where compliance and conversion negotiate, and every geo negotiates differently. This field note covers the KYC friction points that quietly tax first-time deposits in the UK, Germany, LATAM, and India.
Time the wall, do not just lower it
Where the licence allows it, take the deposit first and verify at the withdrawal gate or shortly after, with limits applied rather than hope. A document wall directly in front of funding kills intent at its peak; the same wall a step later kills far less and satisfies the same rules.
Instrument each geo's leak separately
UK drops cluster at automated address verification, German drops at source-of-funds questions, LATAM drops at statement formats automated checks reject, Indian drops when heavy upfront checks stall a UPI flow that otherwise completes in seconds. One blended KYC completion rate averages four different problems into one blind spot.
Fix formats before interfaces
Most KYC friction is document mismatch, not player unwillingness. Accept the formats each geo actually produces, pre-fill what the regulator permits, and keep the first funding step under ninety seconds in every market.
Next step: Map the per-geo KYC funnel on the TrafficPopcorn funnel stack, then measure the lift alongside installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 24 October 2026 · FTD Boost
FTDs Live in the First 90 Seconds
Acquisition hands over a registered player and everyone assumes the hard part is done. This field note covers the lobby-to-cashier moments where the first-time deposit is actually won or lost.
Orient before you monetise
A new player who cannot find a game in the first 30 seconds never reaches a deposit moment at all. One clear orientation path, a single obvious first game, and a persistent deposit CTA beat a feature-dense lobby that hides the cashier behind exploration.
Prompt at honest moments
The end of a first free session, a first win, and a dwindling bonus balance are natural deposit prompts. Interrupting on arrival trains dismissal. Measure time-to-first-prompt per cohort against FTD rate and let the data pick the moment.
Shorten the cashier path relentlessly
Every screen between deposit intent and confirmation leaks FTDs. Pre-fill amounts where rules allow, remember the payment method from the first success, and treat the cashier path as a funnel step with its own QA, because it is one.
Next step: Build the first-90-seconds funnel on the TrafficPopcorn acquisition stack, then connect it with installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 25 October 2026 · FTD Boost
Deposit Two Is Won in Session One
Everyone celebrates the FTD; almost nobody engineers the 48 hours after it. This field note covers the first-session retention work that turns a first-time depositor into a second-time one.
Make the balance real immediately
Confirm the deposit on screen with a visible balance, then respect it. A first session that guzzles a new depositor's balance with confusing mechanics before they have felt one honest win is the fastest way to teach them the product was not worth the money.
Steer, do not smother
Next-best-game prompts that echo the theme which converted them, win-adjacent suggestions, and a single well-timed push all help deposit two arrive. Back-to-back promo modals aimed at more deposits before the player has played do the opposite, and most casinos ship them anyway.
Measure the gap, not just the event
Track time-from-deposit-one-to-deposit-two as a first-class metric beside FTD rate, segmented by promo type. When bonus-driven FTDs reload badly, the finding changes traffic buying, not just CRM, which is why acquisition teams should own this number too.
Next step: Build the second-deposit funnel on the TrafficPopcorn acquisition stack, then connect it with installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 26 October 2026 · FTD Boost
Q4 FTDs: Pace the Season
Q4 is the most expensive acquisition season of the casino year, and most teams enter it reacting week to week. This field note covers planning the promo calendar before it plans you.
Bonus inflation sets the price of everything
Everyone inflates offers at once, so cost per FTD falls while reload quality falls with it. The November cohort that looks like a bargain becomes January churn, which is why quality metrics, not unit cost, survive a February review.
Front-load before the peak, hold budget after it
Map the operator promo calendar against your traffic peaks now. Spend on evergreen offers before December inflation peaks, and keep premium budget for the post-holiday window when competitors thin out and attention gets cheaper.
Judge cohorts weekly, not monthly
Second-deposit behaviour per weekly cohort tells you which buys aged well while the season is still running. Relaunch windows deserve their own line item: the first week of a relaunch buys attention cheaper than any bonus can.
Next step: Build the Q4 pacing plan on the TrafficPopcorn acquisition stack, then connect it with installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 27 October 2026 · FTD Boost
FTDs: Grade Them in January
Q4 FTD reports flatter every acquisition program. This field note covers the January detox, the check that tells you which deposits were players and which were the season.
Q4 is a season, not a market
Bonus inflation drags in depositors who came for December, not for you. A Q4 number full of holiday players reads like growth right up until it stops reading like anything at all.
Let January audit the cohorts
Wallets are lighter and the festive excuse is gone, so tag Q4 deposits by acquisition week and promo, then track second-month deposit rate and time-to-second-deposit through January and February. The players who still deposit are the ones acquisition actually won.
Hold back your best offer
Releasing the strongest bonus mid-January rather than at the December peak filters for genuine intent, because a player who returns for a normal offer is worth ten who only reappear at maximum bonus.
Next step: Wire January-graded cohorts into the TrafficPopcorn acquisition stack, next to PWA installs, push re-engagement, and pre-lander journeys.
Daily field note · 28 October 2026 · FTD Boost
FTDs: Read the Rail, Not the Count
Two campaigns can report identical FTD counts and still be different businesses. This field note covers payment rail as the fastest honest signal of FTD quality.
The rail is a behaviour signal
E-wallet depositors repeat-deposit fast and small, card users attempt larger deposits but meet declines, and crypto depositors are self-custodial, bonus-sensitive, and quickest to vanish with the volatility. Same count, three different players, so segment before optimising anything.
Report the mix, not just the total
Put rail-mix, second-deposit rate, and average deposit by rail beside every cohort count, per geo, and read the shift before celebrating the total. A month where one rail jumps can inflate FTDs while quietly diluting lifetime value, and a card-decline spike is a product fix, not a marketing failure.
Align offers to the rail
E-wallet-first journeys where wallets dominate, decline-recovery paths where cards struggle, and clear terms where crypto players hunt. Read the rail before celebrating the count.
Next step: Build rail-segmented cohorts into the TrafficPopcorn acquisition stack, alongside installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 29 October 2026 · FTD Boost
FTDs: The First Amount Is the Tell
A EUR 10 first deposit and a EUR 100 first deposit are one line in the FTD count and two different players. This field note covers entry-deposit tiers as the fastest honest quality read.
The first amount is a disclosed budget
The player who chose 100 over the 10 minimum has told you their bankroll expectations before a single spin. Tier-level repeat-deposit rates confirm the signal, and minimum-tier depositors carry the heaviest bonus-abuse overlap, since the minimum is exactly the price of a promo hunt.
Report the tier mix beside the count
A spike in minimum-deposit FTDs inflates the headline while diluting value, and it happens quietly because plain FTD counting rewards it. Put tier mix, repeat rate by tier, and average first deposit beside every cohort count, per geo.
Price the ladder per market
Anchor the entry tier to local entertainment spending, align it with the dominant payment rail, and let the bonus ladder do the upsell rather than discounting first deposits into acquired promotions. Re-test quarterly.
Next step: Add tier-mix reporting to the TrafficPopcorn acquisition stack, alongside installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 30 October 2026 · FTD Boost
FTDs: Time the KYC Barrier, Do Not Multiply It
Every verification field between the click and the cashier converts like a toll booth. Where your licence allows deposit-first flows, KYC timing decides how much FTD friction you actually pay. This field note covers verification placement.
Place checks where compliance and momentum agree
The licence decides the floor, since some regimes mandate checks before play and others allow thresholds, so this is a compliance conversation first. Inside that, basic identity up front, full checks at the natural pause around the first deposit, keeps the momentum your media spend already bought.
Speed of verification predicts the second deposit
Automate the straightforward majority so they clear in minutes, and let humans review only edge cases. Make status visible throughout, since silence reads as suspicion. Track verified-within-one-hour beside the FTD count.
Verify once, reuse everywhere
Never make a returning player re-upload what they already proved. A first deposit that never converts into a playable balance was never really an FTD, so treat verification speed as a conversion metric with a target.
Next step: Add KYC-timing checks to the TrafficPopcorn conversion stack, alongside installed PWA sessions, push re-engagement, and pre-lander journeys.
Daily field note · 31 October 2026 · FTD Boost
FTDs: Screen for Quality, Not Just Volume
A flagged first deposit already cost you the media spend and maybe the bonus, so it should not sit in your FTD count forever. This field note covers screening economics for deposit quality.
Price a flagged FTD honestly
Media cost plus bonus cost plus review time, weighed against the genuine players your checks slow down. Multi-accounting and velocity patterns fund themselves from budgets meant for real acquisition, so a fraudulent FTD costs money twice.
Run silent checks, escalate rarely
Behavioural analysis on every deposit, automatic clearing for the straightforward majority, human review for genuine edge cases. Too loose funds abusers; too tight churns legitimate players whose first session stalls behind a fraud queue.
Report net revenue per FTD, not gross count
Subtract refunds, clawbacks and bonus costs from deposit revenue and trend the result per traffic source. Watch day-thirty retention and flagged-but-cleared rates, since the latter rising says your thresholds are set too paranoid.
Next step: Add deposit-quality metrics to the TrafficPopcorn conversion stack, alongside installed PWA sessions, push re-engagement, and pre-lander journeys.
Back to the current FTD Boost notes · FTD Boost QA guide