Lifecycle messaging for Web3 and Web2
Reach every user, by wallet or email
Identify people by wallet or email, reach them by in-app and email, automate from what they do, and measure whether it worked. Web3 or Web2, one loop.
Start where you are
Two paths through these docs, whether you run on email, on wallets, or both.
Run campaigns
Set up a workspace, build an audience, and send your first campaign.
Build an integration
Send events, push in-app notifications, and query your data.
The core loop
Every part of the platform is one stage of the same loop. Each stage feeds the next.
Detect
Capture product events (signups, purchases) and on-chain activity as they happen.
Resolve
Tie a wallet, an email, or your own user id to one contact record.
Segment
Build cohorts with rules or SQL across your product, email, and on-chain data.
Reach
Send email and in-app from one workflow.
Automate
Trigger flows the moment someone signs up, buys, or does something on-chain.
Measure
Track opens, clicks, and delivery across channels.
Popular guides
Welcome email on signup
Someone signs up, send a welcome email and start onboarding.
Welcome a new wallet
A wallet connects or mints in, greet them in-app.
Send your first campaign
From a fresh workspace to a live send.
Custom events
Send product events and trigger automations from them.
In-app notifications
Wallet-addressed push in your dApp, two lines with the SDK.
Automation triggers
The full trigger catalog, from signups to swaps.
Wallet-first or email-first, your call
Identify people however you have them: a wallet, an email, your own user id, or all three on one record. Web3 teams reach people by wallet and in-app where there’s no email. Web2 teams run the whole platform on email. Either way, it’s one audience, one set of tools, and one measure of what worked.