iGaming Push · field note archive
Field Note Archive
Every earlier iGaming Push 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 · iGaming Push
iGaming Push Frequency: Four Tests Before Your Next Campaign
Frequency is where iGaming push programs either build habit or burn consent. Before scaling your next casino push campaign, run four controlled tests: a hard cap test, a segment-based cap test, a timing and quiet-hours test, and a relevance swap test that changes message content while holding volume constant.
Test a hard cap against a segmented cap
Split consented players into two Arms: one global daily cap, one cap set by recency and declared interest. Compare return sessions and opt-outs after a full week, not a single send.
Respect time zones and quiet hours
Local-time delivery with defined quiet hours protects sleep-mode players and reduces accidental opt-outs. Measure delivery-adjusted engagement, not raw click counts.
Change the message before you change the volume
If frequency caps do not move return sessions, the problem is usually relevance. Swap one message theme per cohort and re-measure before adding more sends.
Next step: Run frequency tests alongside the TrafficPopcorn re-engagement stack, then connect results to PWA install behaviour, pre-lander message match, and FTD quality.
Daily field note · 14 October 2026 · iGaming Push
iGaming Push Opt-Ins: Where You Ask Matters More Than What You Say
Opt-in rate is set mostly by placement, not copy. This field note walks three placements that outperform a first-visit prompt: post-session, post-offer-claim, and the return-visit soft ask, each with the consent copy that keeps accepted players subscribed past 30 days.
Ask after the second session, not the first
A player who returned once has seen the product. Prompting then roughly doubles meaningful accept rates versus a first-landing prompt, because the permission request follows demonstrated interest rather than a cold open.
Promise the message, not the bonus
Consent copy should describe relevance: game updates, offer windows, session reminders. Bonus-led prompts raise accepts from players who unsubscribe the moment the next promotion disappoints.
Re-ask with a soft prompt, never a hard block
If a player dismisses the browser prompt, gate nothing. Use an in-page prompt triggered by later value moments; hard gates breed resentment and gut every other engagement metric.
Next step: Build opt-in placement tests on the TrafficPopcorn re-engagement stack, then read accept rates beside PWA install behaviour, pre-lander message match, and FTD quality.
Daily field note · 15 October 2026 · iGaming Push
Casino Push Win-Back: Lifecycle Segments That Bring Players Back
Win-back campaigns fail when every lapsed player gets the same blast. This field note segments lapses by recency and value, then matches message, timing, and cap to each segment so return sessions rise without consent burn.
Segment by recency, then by value
A 14-day casual needs a gentle nudge about a new game; a 60-day high-value player needs a specific, honest reason to return. One message for both converts neither and opts out both.
Lead with relevance, not escalation
Win-back copy should describe what changed: new games, a feature, a finished tournament. Escalating bonuses across a sequence trains players to lapse on purpose to earn the bigger offer.
Cap the sequence and fall back gracefully
Two or three sends with declining value, then stop pushing and use a channel the player still engages with. Every send after that trades long-term consent for a short-term click.
Next step: Build lifecycle win-back segments on the TrafficPopcorn re-engagement stack, then read results beside PWA install behaviour, pre-lander message match, and FTD quality.
Daily field note · 16 October 2026 · iGaming Push
iGaming Push Copy: Short, Specific, and Deep-Linked
Segmentation decides who gets the message; copy decides whether it earns the tap. This field note covers the copy rules that separate casino push campaigns that re-open sessions from campaigns that quietly burn consent.
Write for the lock screen cut-off
Assume the player reads a truncated sentence. Put the game or event in the first few words, the action right after, and cut everything that survives only in the full notification nobody opens. Hype words are the first thing to delete, not the last.
One notification, one destination
A push about tonight's tournament links to that tournament, not to a lobby. Every tap between the notification and the promised screen leaks returning players, and the leak shows up in analytics as push CTR that never becomes sessions.
Make silence part of the copy strategy
Campaigns that always send teach players to swipe notifications away unconsciously. Sending only when there is something worth saying keeps the next message readable at all.
Next step: A/B copy lengths and deep-link targets on the TrafficPopcorn re-engagement stack, then compare behaviour with installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 17 October 2026 · iGaming Push
Push Opt-In Timing: Ask After the Value Moment
Consent is the scarcest asset in iGaming push, and most casino sites spend it in the first five seconds. This field note covers when to ask for notification permission so the answer is yes.
Never ask on first load
A cold permission prompt converts a first-time visitor into a lifetime block, because most platforms remember a dismissal as a permanent no. The one-shot system prompt is the most expensive pixel on the page; treat it like a checkout button.
Anchor the ask to a value moment
Right after a first win, a claimed bonus, or a tournament registration, the player has a reason to want the follow-up. Frame the prompt around that reason, free-spin reminders or live tournament alerts, and the tap reads as a service.
Respect the no permanently
A player who declines never sees the system prompt again. Respect that in-app too: offer value in exchange for consent, and keep the opted-out segment reachable through the channels that remain, such as email or in-lobby messaging.
Next step: Run opt-in prompt timing tests on the TrafficPopcorn re-engagement stack, then compare consent rates against installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 18 October 2026 · iGaming Push
Push Frequency Caps: Earn Every Home-Screen Slot
Opt-in is not a license; it is a lease renewed per send. This field note covers capping casino push frequency so every notification keeps its welcome.
Cap by segment, not by campaign
Depositors, bonus hunters, and never-depositors tolerate different volumes. Set weekly caps per segment, two to five sends is the usual band, and let campaign urgency queue behind the cap instead of jumping it.
Score value per send
Before any notification ships, ask what the player gains by opening it: a free-spin expiry, a tournament start, a balance-back offer. No gain, no send. Promotional filler that gets swiped away trains the home screen to ignore the brand.
Respect quiet hours and muting
Hold sends during local quiet hours, and treat a mute as a signal to slow down, not to reroute to a different channel. Muted opt-ins still see the lobby; burned opt-ins uninstall and never come back.
Next step: Apply frequency caps across the TrafficPopcorn re-engagement stack, then measure retention against installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 19 October 2026 · iGaming Push
Push A/B Tests: Let Opens Pick the Words
Most casino push copy is chosen by opinion in a kickoff call. This field note covers replacing that with a simple testing loop that lets open rates choose the words.
One variable per test
Change the title, or the preview, or the send hour, never two at once. Test two arms on a single send, hold everything else constant, and record open rate against the segment. Stacked variables produce wins nobody can explain or repeat.
Write arm B to beat arm A
Arm B must be a real rival, not a decoy: concrete number versus vague promise, player-relevant verb versus operator jargon, quiet-hour-respecting send versus default blast. Decoys inflate the champion and teach nothing about the next send.
Read results by segment
A copy win among depositors can be a loss among never-depositors. Log the champion per segment, feed it back into frequency caps, and route the next test at the next variable. The compounding asset is the evidence log, not any single winning line.
Next step: Wire copy tests into the TrafficPopcorn re-engagement stack, then compare tested copy against installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 20 October 2026 · iGaming Push
Push Deep Links: Land the Open Where the Promise Lives
The open is the most expensive event a push earns, and most programs waste it on the generic lobby. This field note covers routing every open to the page the message actually promised.
Match destination to message
Free-spins push opens the free-spins area. New-game push opens that game, not the category. Deposit nudge opens the cashier, amount pre-filled where the market allows. Message match after the tap is the same discipline as the pre-lander, one hop later.
Design for the late open
Notifications sit unopened for hours or days, and offers expire. Route each deep link through a live campaign record, and when the original offer died, land the late opener on the nearest live equivalent instead of a 404 with a logo on it.
Instrument the post-open journey
Track opened to session, session to action, action to FTD, per destination. The data quickly shows which message types deserve richer destinations and which were always wallpaper.
Next step: Map destinations per message type on the TrafficPopcorn re-engagement stack, then trace open quality into installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 21 October 2026 · iGaming Push
Push Rich Media: Design for the Weakest Renderer
The same casino push can arrive as a full-width banner with art or a two-line text card, depending on where it lands. This field note covers designing creative that survives every renderer.
Text first, art second
Write every message so the plain text version converts: offer, game, and urgency inside the first 40 characters of the title. Hero images lift opens where they render, but the copy has to carry the message everywhere else.
Test emoji, do not assume
Emojis render differently across Windows, macOS, Android, and iOS, and a sparkle in your brand palette can arrive as a grey box elsewhere. Test the set you intend to use per environment, then keep a two-tier list: safe everywhere, and enhancement-grade where verified.
Truncation is a design constraint
Never let a platform cut the amount, the code, or the expiry. Keep bonus codes short, put expiry early, and preview all variants against long-locale and large-font devices before shipping to the full segment.
Next step: Build a render matrix per platform on the TrafficPopcorn re-engagement stack, then trace rendered-variant performance into installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 22 October 2026 · iGaming Push
Push Quiet Hours: Orchestrate by Geo
A campaign scheduled in one office timezone lands at 3am somewhere, and that somewhere is usually your quietest unsubscribe spike. This field note covers orchestrating sends across the geos that matter: UK, Germany, Canada, LATAM, and India.
Segment by stored local time
Keep the player's timezone on the profile, not the campaign. Schedule per segment, evaluate the window at send time, and hold any send that would land inside quiet hours until the next legal slot instead of shipping it and hoping.
Compliance and conversion share the dial
The same windows that satisfy regulators also protect conversion, because overnight pushes get swiped away unread and train opt-outs. Tune per geo: prime-time bonuses in the UK evening, festival-timed offers in India, weekend windows in LATAM.
Report per geo, not blended
One blended open rate hides a region being punished for another's schedule. Split quiet-hour performance out, and let the most compliance-constrained region prove whether the windows cost volume or merely delay it.
Next step: Build the timezone orchestration on the TrafficPopcorn re-engagement stack, then reconnect players into installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 23 October 2026 · iGaming Push
Push Drop-Off: Follow the Tap
A push click is a promise, and every step between the tap and the game is a place to break it. This field note covers measuring where casino push clicks actually die, per geo and message type.
Instrument the four-step funnel
Count tap, landing view, intended-content view, and session start as separate events with the campaign ID riding along. The gap between landing view and intended-content view is where most programs discover their push clicks were never real sessions.
Read drop-off per message type
Bonus pushes die at the promo expiry wall, jackpot alerts die at the game cold start, and reactivation nudges die at the login prompt. One blended drop-off rate merges three different problems, so keep the splits in the report the same way you keep geo splits.
Fix the biggest leak first, then remeasure
Usually that means preloading the destination content during the cold start, honouring the message promise on the landing screen, and deferring the login wall where compliance allows. Recover one step at a time and let the funnel prove each fix before the next.
Next step: Build the tap-to-session funnel on the TrafficPopcorn re-engagement stack, then close the loop with installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 24 October 2026 · iGaming Push
Push Lists: Prune What Doesn't Pay
Push lists decay by default, and most casino programs only notice when revenue per send slides. This field note covers list hygiene as an economics exercise, not a housekeeping one.
Count what decay actually costs
Dead tokens, quiet subscribers, and stale geo segments all still cost a send. Divide program spend by subscribers who opened something this month and the true cost of the dead weight becomes obvious; the blended number hides it, the active-only number does not.
Read unsubscribes as targeting data
An unsubscribe is a free answer to a question you were not asking. Split the rate by message type and segment, and a pattern appears: the content or the audience is mismatched. Fix the mismatch and the same list earns more without growing by a single subscriber.
Run hygiene on a fixed cadence
Monthly token validation, quarterly quiet-subscriber review, and a standing rule that every new segment gets a hygiene date at birth. Decay compounds in both directions, and so does discipline.
Next step: Apply the hygiene cadence on the TrafficPopcorn re-engagement stack, then close the loop with installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 25 October 2026 · iGaming Push
Push Pace: Fatigue Has a Curve
Most casino push programs set a frequency cap by feel, then defend it in meetings. This field note covers fatigue as a measurable curve, and why the peak of that curve is the only defensible send volume.
Plot the decay, not the total
Send volume up five percent and weekly engagement tells you almost nothing; the same experiment tracked over eight weeks shows the bend. Plot opens, opt-outs, and revenue per send against send frequency per segment, and the curve shows exactly where each extra notification starts buying less than it costs.
Cap by segment and message type
Event-driven messages such as a bonus expiring or a favourite table going live tolerate more sends than generic promotions, and dormant players tolerate the least. A single program-wide cap is the fastest way to over-send the players you most want to keep.
Re-read the curve quarterly
Fatigue thresholds move with seasonality, creative quality, and how used to push the audience has become. Re-plot quarterly and after every retention-drive campaign, because a cap that was right in January is usually optimistic by October.
Next step: Apply the fatigue-curve method on the TrafficPopcorn re-engagement stack, then close the loop with installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 26 October 2026 · iGaming Push
Push Creative: Test It Like Ads
Casino push programs obsess over send timing while running the same creative for months. This field note covers rich-media CTA testing, the lever most programs never pull.
Test in order of leverage
The CTA verb and preview text decide the open. The hero image decides the click. The deep-link destination decides the money. One variable per split, per segment, because a creative that wins with dormant players routinely loses with your actives.
Guard the test against fatigue
Run variants inside identical frequency caps and stop before fatigue bends the curve. A losing variant left running is not just wasted sends, it trains the audience to ignore you in general, which taxes every future campaign.
Keep a creative ledger
Log every variant with its window, segment, and outcome, then retest champions quarterly. Response to the same asset decays quietly, and a ledger is the only way to notice before the whole program takes the blame.
Next step: Wire creative tests into the TrafficPopcorn re-engagement stack, then close the loop with installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 27 October 2026 · iGaming Push
Push: Make the Button Do the Work
Most casino push sends are a headline and a hope. This field note covers interactive push: buttons and quick actions that let the notification itself close the next step.
Know what each platform actually renders
Web push actions work on Chromium and mostly on Android; iOS Safari shows plain text and nothing else, and every OS caps the number of buttons. Design for the lowest common denominator first, then enhance, never the reverse.
Put the action on the button, not behind it
One primary action, one verb-and-noun label: Claim Bonus, Play Now, Remind Me. A Remind Me beat is respect, not weakness, because a snooze keeps the subscriber where an unsubscribe removes them.
Fallback carries the offer
The plain-text version must land the same message, since on half your devices it is the only version that exists. Measure taps against body opens per segment and retire any action that decays below its own baseline.
Next step: Build interactive sends on the TrafficPopcorn re-engagement stack, paired with installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 28 October 2026 · iGaming Push
Push: Design for Every Lock Screen
Push creative gets two seconds on a locked screen. This field note covers the accessibility details that decide whether those two seconds end in a tap.
The lock screen is the real canvas
Dark mode, sunlight, one hand, half a second of attention. Creative that only works in the campaign dashboard is creative that mostly does not work, so design for the worst screen the message will ever land on.
Alt text and contrast are conversion work
Every image needs alt text that carries the offer, every icon needs contrast in both appearance modes, and no critical text belongs inside an image. The version for screen readers is often the only version a subset of your list will ever receive.
Test on devices, not dashboards
Preview on real devices, both light and dark, several OS versions, larger text scale, and confirm the plain-text fallback lands the full message. Retire creative that only survives ideal conditions.
Next step: Pair accessible creative with the TrafficPopcorn re-engagement stack, alongside installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 29 October 2026 · iGaming Push
Push: Optimize the Hour, Not Just the Copy
The identical push can double its engagement or destroy it depending on the hour it lands. This field note covers send-time discipline, the cheapest win in push re-engagement.
Blast at 09:00 HQ time, lose silently
A UK player and a Canada player are not awake in the same hour. Per-geo prime windows beat one global send, and player-level send windows based on past opens beat both, because the data finds the invitation hour opinion cannot.
Quiet hours are Opt-Out Time
Nothing lands between roughly 22:00 and 08:00 local. An offer that wakes a player up trains them to mute the channel, opted out of the whole programme by one careless 01:00 send, and local-time rules apply even when a global rule is easier to click.
Test with holdouts, guard the list
Run a 10 per cent split against the default window with identical creative, measure sessions and deposits rather than opens, and track opt-outs per window so a winning click rate that burns subscribers loses automatically.
Next step: Fold burned-in send windows into the TrafficPopcorn re-engagement stack, alongside installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 30 October 2026 · iGaming Push
Push: The Same Offer Is Three Different Messages
A deposit offer means one thing to a player twenty minutes after their first deposit and something else entirely to a subscriber dark for six weeks. This field note covers lifecycle segmentation for casino push.
New depositors need guidance, not more offers
Use the first 48 hours to guide, not to sell: games their cohort plays, where limits live, how often you message. Suppress the next bonus blast; it teaches that every notification wants money. Guided programmes extend time-to-second-deposit and lift lifetime value.
Lapsed players need a reason, not a discount
A lapse is a decision made weeks ago. Lead with what changed, new releases, faster cashier, better rails, and keep win-back cadence weekly, never daily. Acknowledge the absence instead of pretending it never happened. Rebuild segments nightly so subscribers drift buckets automatically.
VIPs want exclusivity signals
Early access, bespoke reloads, a named host. The mass blast a lapsed player needs reads like spam to a VIP and quietly erodes the status the segment depends on. Track opt-out rate per segment, not just per campaign.
Next step: Add lifecycle segmentation to the TrafficPopcorn re-engagement stack, alongside installed PWA sessions, pre-lander journeys, and FTD quality.
Daily field note · 31 October 2026 · iGaming Push
Push: The Ask Is the Campaign
The permission prompt is the first campaign your push programme ever runs, and most casino sites fire it at page load to a visitor with no reason to allow. This field note covers timing and copy for the ask itself.
Ask after a value moment, never on load
Prompt after the player perceives value: a finished first session, a home-screen install, a claim in progress. Let the pre-prompt state the benefit so the browser dialog confirms instead of surprising. On desktop a block is close to permanent for that profile.
Make a specific promise about content and frequency
Game drops, reload windows, session follow-ups, twice a week, silence when nothing is worth saying. Specific beats clever, and honesty about frequency is already differentiation in a vertical trained to expect spam. Never re-ask after a dismissal.
Treat the allow rate as the first campaign metric
Track prompt shown, allowed, dismissed and blocked per trigger, and optimise the trigger and moment before the wording. On iOS the ask only exists after install, which makes the PWA the top of the push funnel.
Next step: Add prompt-timing tests to the TrafficPopcorn re-engagement stack, alongside installed PWA sessions, pre-lander journeys, and FTD quality.
Back to the current iGaming Push notes · iGaming Push QA guide