By MoEngage

MoEngage Customer Engagement Platform

Segmentation, event-triggered journeys and coordinated guest messaging with experiments and delivery controls.

The offering

What MoEngage Customer Engagement Platform does

MoEngage Customer Engagement Platform connects customer profiles and events with segments, messages and visual Flows journeys. A flow can branch on customer attributes or actions, wait for a period or event and compare alternative paths. The plan comparison describes campaign/global control groups, A/B tests, message previews, preference management and delivery caps.

The current Foxwoods case provides a casino/resort application: connected guest data supports new-member, loyalty-tier and other communications across channels. Start with the operator’s identifiers, event quality and permitted message scope. Configure consent, exclusions and fallback before activating a journey, then inspect delivery and campaign records separately from commercial impact. Channel connections, transactional messaging, analytics and AI functions have plan or add-on boundaries; they are not all included simply because the platform lists them.

Who should explore it?

Casino guest CRM teams building coordinated lifecycle messaging with documented eligibility and experiment controls.

  • Coordinate a consented new-member guest journey
  • Test loyalty-tier communications while retaining a control group

Documented capabilities

  • Attribute and behavioural segments
  • Visual branching and waits
  • Event-triggered messages
  • A/B tests and control groups
  • Preferences, frequency caps and debugging

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Engagement role
Segments, journeys, coordinated messaging and campaign analysis within one platform.Source
Evidenced casino use
Casino/resort guest CRM is documented at Foxwoods; sportsbook, PAM and wallet connections need separate implementation evidence.Source
Enabled channels
Email, app/web push, in-app/on-site and other listed channels; connected channels and transactional messaging have package boundaries.Source
Flow logic
Event-triggered messages, conditional splits and waits for actions or time periods.Source
Tests and controls
A/B campaign/flow branches plus campaign and global control groups; assess configured outcomes.Source
Delivery controls
Preferences, message caps, do-not-disturb rules, flow error logs, debugging and versioning.Source
Commercial scope
MTUs, Growth/Enterprise plans, selected add-ons and a stated minimum one-year commitment.Source

Delivery & commercial details

Delivery & integration
Connect the selected guest profiles and source events, configure approved channels and build/test Flows. Map opt-outs and exclusions, inspect errors and release the journey under operator approval.Source
Pricing
Sales-led Growth and Enterprise proposals use Monthly Tracked User scope and selected add-ons. The current FAQ states a one-year minimum commitment; confirm message/provider, implementation and optional-feature costs.Source

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

How can message pressure and experiments be controlled?

The pricing comparison lists message caps, do-not-disturb settings, preference management, A/B tests and control groups. Configure these around the operator’s consent and player/guest eligibility rules.

Source
Does the Foxwoods case prove our gambling systems are connected?

It documents a casino/resort guest deployment with connected data and coordinated messaging. Your PAM, wallet, sportsbook or other backend connection needs its own mapping, permissions and implementation validation.

Source