🔔 Turn notification permission into a player-return strategy.
LizardHouse Notifications: Permission and Re-Engagement helps Unity developers ask for notification access at the right moment, bring players back with relevant local reminders, and understand the complete journey from first prompt to notification open.
Instead of building permission logic, reminder scheduling, player-return cleanup, notification routing, localization, and analytics separately, you get one connected workflow for Android and iOS.
You define the strategy and content. LizardHouse handles the lifecycle.
🎯 Ask when players understand the value
The native permission prompt gives you a limited opportunity. Make that opportunity count by asking after the player has experienced enough of your game to understand why reminders could be useful.
You can build a thoughtful permission journey without locking your game into a fixed prompt design or asking every player at the same arbitrary moment.
⏰ Create a complete re-engagement sequence
Schedule one reminder after a few hours or build a full journey that continues across days, weeks, or months.
Every reminder can have its own:
Reminders are scheduled automatically around player inactivity, giving your game more opportunities to bring players back without requiring a campaign server.
No notification backend. No dashboard account. No MAU fees. No internet connection required for the local re-engagement flow.
🌙 Stay relevant and respect the player
A reminder loses its value when it arrives after the player has already returned.
LizardHouse automatically removes reminders from the previous inactivity cycle when the player comes back, then creates a fresh schedule the next time they leave.
It also cancels only the notifications it owns, allowing it to work alongside other notification systems in the same project.
Use three per-notification Quiet Hours policies to decide whether a reminder should:
This gives each message the timing policy it deserves instead of treating every reminder the same.
📲 Turn notification opens into useful actions
Know which reminder brought the player back and decide what should happen next.
The notification open callback provides the optional Notification Key and Custom Payload attached to that reminder. Use them to:
Notification opens are handled during both warm and cold starts, with duplicate-open protection built in.
You can also keep an in-game notification toggle synchronized with the player’s effective permission state and provide direct access to the operating system’s notification settings when needed.
📊 Measure the complete journey
See where players accept, decline, return, or drop out through a consistent eight-event analytics funnel covering:
Choose Firebase Analytics, connect your own analytics system through a generated integration script, or use the asset without analytics.
The data stays in the analytics platform you choose. LizardHouse does not require an external account or send your notification analytics to its own servers.
🌍 Fit every reminder to your game
Reach players with content that belongs naturally inside your product.
LizardHouse provides the system without forcing its own branding, language, analytics platform, or prompt design into your game.
🛠️ Built to save development time
Configure the permission journey, notification sequence, Quiet Hours, localization, analytics, notification keys, and payloads from one dedicated Unity Window.
The asset initializes automatically, keeps its state across scenes and app restarts, and validates the setup before saving. A focused public API keeps custom integration small.
🎮 Test the experience before shipping
The included demo scene lets you:
📚 Documentation, setup guides, integrations, and support
LizardHouse Notifications Documentation
Your game worked hard to earn the install. Give it a smarter way to earn the next session.