Lunor Engage
Player data and marketing automation for iGaming operators.
An operator workspace that turns player data into segments and campaigns — for licensed iGaming businesses, not for this website.
- product
- Lunor Engage
- surface
- Engage
- category
- Engage
- backend
- Not attached
- status
- Coming Soon
This page describes the intended product. Nothing here accepts a payment, sells a ticket, opens a workspace, sends a campaign, or answers a support conversation.
The problem
The player record and the campaign live in different systems.
An operator already has player activity. The marketing tools that send the campaign usually see a list, not the behavior that made the list. Segments are rebuilt by hand, and nobody can say which campaign a returning player actually came from.
The result is activity without a record: messages sent, and no reliable view of who was targeted, why, and what happened next.
The approach
Player data in. A campaign the operator can explain out.
Lunor Engage is the intended CRM and marketing automation product for iGaming operators. It connects player data to segments, and segments to campaigns, so an action is tied to a defined audience rather than a blast.
It does not acquire players, retain players, or promise either. It is the system an operator would use to do that work themselves. This site runs no campaigns and holds no player data. It is not an offer of gambling.
Capabilities
What the module does.
Player record
The operator's view of a player, built from the data the operator already has.
Segments
Audiences defined by behavior, not by a one-off export.
Campaigns
A message sent to a segment, with the audience stored on the campaign.
Automation
Rules that run when a player matches a condition the operator set.
Acquisition view
Where a player came from, when the operator records it.
Retention view
Who is active, who went quiet, and which campaign touched them.
Operator controls
A person approves what is automated. The product does not invent a campaign.
Not live
No player data and no sends from this site.
How it works
The workflow, step by step.
- 01Bring the player data
The operator connects the record they already keep.
- 02Define a segment
Behavior and attributes, saved so the audience can be inspected.
- 03Build the campaign
Message, segment, and the condition that sends it.
- 04Review before it runs
Automation is a rule the operator can see, not a hidden sequence.
- 05Read the result
Who was targeted and what the campaign record says happened.
Specification
At a glance.
- Audience
- Licensed iGaming operators
- Unit
- Player, segment, campaign
- Automation
- Operator-defined rules
- Data on this site
- None
- Not offered
- Gambling, player acquisition guarantees, or retention guarantees
- Status
- Coming soon — no published date
Security
Player data is the operator's. This marketing site does not hold it.
- No player records, segments, or campaigns exist on this site
- Lunor Engage is a product for operators. It is not a gambling service and not an invitation to play
- Availability for a real operator depends on that operator's licence and jurisdiction
- The intended product keeps campaign rules visible to the operator who set them
- No outcome — acquisition, retention, or revenue — is promised
Full posture, including what we deliberately do not claim, is on the security page.
Use cases
Where it gets used.
A defined segment
Build an audience from behavior and keep that definition on the record.
A lifecycle campaign
Send to players who match a condition, and store who was included.
An operator review
See which campaigns touched a player before someone changes the next one.
FAQ
Questions asked before adopting this module.
Is Lunor Engage a gambling product?
No. It is a CRM and marketing automation workspace for iGaming operators. It does not take bets, hold a player balance, or offer a game. This page is not an invitation to gamble.
Can I upload players or send a campaign here?
No. The product is coming soon. This site stores no player data and sends nothing.
Will it improve acquisition or retention?
Those are the jobs an operator uses it for. The product does not guarantee either. Results depend on the operator's data, offer, and licence.
When does it ship?
No date is published. A first operator would need to be a licensed business, and the work is sequenced around that.
Other modules
Same Console, same project record.
Next step
Tell us if you need this one.
Modules move up the sequence when a real project needs them. If this is the one blocking you, that is useful information.