Customer.io Journeys
Visual lifecycle automations using player events and attributes, with branching, subscription preferences and message experiments.
Supplier popularity85%Customer.io
Event-based lifecycle messaging with configurable journeys, branching and subscription preferences.
Popularity85%Explore the offering
Products & services
Open a product to explore its capabilities, delivery and sources, or browse its type to compare alternatives.
About Customer.io
Customer.io, operated by Peaberry Software, Inc., provides a customer engagement platform. Its current iGaming guide discusses player onboarding, lifecycle messaging and re-engagement using customer activity. Journeys is the marketed automation offering, with visual workflows, event and segment triggers, branching, subscription preferences and testing.
Feed the platform with the player events and permissions needed for each campaign. Keep the operator’s eligibility and account restrictions current, then test audience selection, exclusions and downstream responses. Channel policy affects procurement: Customer.io’s current Feature Terms prohibit gambling SMS traffic in the United States and Canada on all number types, with narrow bingo exceptions. Other channels, providers and countries require their own permissions and agreed scope.
Where this supplier fits
Gambling lifecycle teams seeking data-driven messaging in channels permitted by the supplier’s policy and their operating markets.
Company-level capabilities
- Event and segment-triggered journeys
- Visual branching and message orchestration
- Subscription preferences
- A/B tests and conversion measurement
These reflect the supplier's public descriptions. Check individual products for scope; a company capability does not automatically apply to every offering.
Questions for your evaluation
Use these to confirm the details for your business and market.
- Which channels are permitted for our gambling activity and countries?
- How will consent and player-account restrictions update the audience?
- What profiles, message volumes and add-ons are priced?
Commercial-reach estimate
Customer.io popularity
An estimated index of documented commercial footprint and geographic reach. It is not market share, customer satisfaction or a product recommendation.
Commercial footprint 80% weight9,000+ brands
The current homepage and pricing material state trusted by 9,000+ brands; no reporting date is supplied.
Scope: Global all-industry brand footprint. Brands may share an organisation; this is not an iGaming-only operator census or Journeys product-adoption count.
View sourceGeographic reach 20% weightNot publicly confirmed
No numerical aggregate of customer-linked operating countries was established in the reviewed current material.
Scope: Customer-linked geographic activity; supported markets, rails, datasets, local offices and legal entities are not converted into countries with clients.
View sourceSource review confirms the recorded declaration, not an independent audit of every customer. Brands, customer groups and merchants are different units. Employee and follower counts do not affect this score.
Global all-industry brand footprint. Brands may share an organisation; this is not an iGaming-only operator census or Journeys product-adoption count. Missing numerical inputs remain null and undated asOf values remain null. Workforce is context only.
Popularity methodologyBuyer questions, answered
Is there documented iGaming applicability?
The supplier’s current iGaming lifecycle guide discusses operator/player engagement, onboarding and later customer journeys. Product scope still needs to be agreed for the business and channels.
SourceCan US or Canadian gambling SMS campaigns use Customer.io?
The current Feature Terms prohibit gambling traffic in the United States and Canada across Toll Free, Short Code and Long Code numbers. The policy lists narrow bingo exceptions; do not assume ordinary casino or betting traffic qualifies.
SourceWhich records count toward profile pricing?
The current pricing page counts people and objects in the profile allocation. Message volume and plan-specific functionality also affect cost, so size the proposal around the actual data model.
Source