9 Best Email Tools With RevenueCat Integration (2026)

RevenueCat knows exactly when a trial starts, a renewal fails or a subscriber cancels. It does not send the email. For that you need a messaging tool connected to it, and the connection matters more than the logo: which events arrive, how users are matched, and whether you can act before a trial converts.

This list covers every email and messaging tool I could verify with a RevenueCat connection in October 2026: RevenueCat's own native integrations, plus tools that connect from their side or by webhook. Integration details come from RevenueCat's docs and the vendors' docs; prices come from each vendor's pricing page.

Disclosure: I build Sequenzy, which is one of the 9. Tools are listed alphabetically, not ranked.

Quick comparison table

How RevenueCat integrations work

There are three ways to connect RevenueCat to an email tool:

1. A RevenueCat-built integration. You enter the tool's credentials in RevenueCat's dashboard, and RevenueCat sends events in the tool's format. Setup is quick, but you get whatever RevenueCat decided to send, matched by whatever identifier you set as a subscriber attribute.
2. A tool-built integration. The email tool receives RevenueCat's webhook and maps it itself. The tool can add things RevenueCat does not send, such as tags, revenue attributes and scheduled events.
3. A webhook or relay you build. Point a RevenueCat webhook at your server or route events through Segment or mParticle. This works with any tool but leaves retries, deduplication and identity matching to you.

Whichever you use, two things decide whether it works:

• Identity. RevenueCat identifies people by app user ID. Every integration needs a way to find the right contact, usually a subscriber attribute such as $email or the tool's own ID. Set it right after sign-in, or events land on nobody.
• The trial reminder. RevenueCat has no event before a trial converts, because Apple and Google send none. You either schedule it yourself from expiration_at_ms or use a tool that does. Our guide to RevenueCat webhooks for lifecycle emails explains every event.

The 9 best email tools with RevenueCat integration

1. Airship

Best for: Apps already on Airship for push that want RevenueCat events in the same journeys.

Setup: In RevenueCat, add the Airship integration with your Airship app credentials. In the app, call Purchases.shared.attribution.setAirshipChannelID() with the Airship channel ID, or use an Airship Named User, so events attach to the right device or person.

RevenueCat sends events such as rc_initial_purchase_event, trials, renewals, cancellations and billing issues as Airship custom events, with revenue and customer attributes. Airship's own docs list two requirements: the RevenueCat Pro plan and an Airship plan that includes messaging.

• Pros: Events arrive as named custom events you can trigger journeys from, revenue included.
• Cons: Matching depends on a channel ID or Named User you must set, no event before a trial converts, price only by quote.

Verdict: A clean fit if Airship is already your push vendor.

2. Braze

Best for: Teams on Braze that want RevenueCat purchases to show up as real orders in Braze analytics.

Setup: Add the Braze integration in RevenueCat with your REST API key and endpoint, then choose the event format. Set $brazeAliasName and $brazeAliasLabel subscriber attributes if your Braze users are identified by alias rather than external ID.

RevenueCat maintains this integration and Braze lists it in its partner docs. It is the most flexible on format: custom events, legacy purchase objects, or Braze eCommerce ecommerce.order_placed events, which RevenueCat recommends because Braze's revenue reporting understands them. Attributes arrive as rc_customer_attribute_*, plus rc_subscription_status for segmenting.

• Pros: Choice of event format, purchases count in Braze revenue reporting, subscription status attribute.
• Cons: Format choice needs planning up front, no trial-ending event, Braze itself is sales-led.

Verdict: The richest RevenueCat integration for teams that already run Braze.

3. CleverTap

Best for: CleverTap users who want subscription revenue next to their engagement analytics.

Setup: Add the CleverTap integration in RevenueCat with your account ID, passcode and region. Set the $cleverTapId attribute from the CleverTap SDK; if you skip it, RevenueCat falls back to the app user ID.

Events, revenue and customer attributes arrive in CleverTap. One gotcha: CleverTap cannot receive negative revenue, so refunds do not reduce revenue totals there. Track refunds as their own event if your reports depend on net revenue.

• Pros: Falls back to app user ID when no CleverTap ID is set, revenue alongside analytics.
• Cons: Refunds do not subtract revenue, email is a paid CleverTap add-on, no trial-ending event.

Verdict: Good for analytics-heavy push programs on CleverTap.

4. Customer.io

Best for: Self-serve lifecycle teams that want RevenueCat events to create and update people without extra code.

Setup: Add the Customer.io integration in RevenueCat with your Customer.io API credentials. Set $customerioId if your Customer.io people use a different ID than your RevenueCat app user ID.

RevenueCat sends events, revenue and attributes, and creates the person in Customer.io if they do not exist yet, which avoids silently dropped events for users who bought before they were synced. Customer.io also has a live native Superwall integration, so the same workspace keeps working if you move platforms.

• Pros: Automatic person creation, falls back to app user ID, also supported by Superwall.
• Cons: Auto-created people still need an email before they can receive email, no trial-ending event.

Verdict: The most forgiving setup among RevenueCat's own integrations.

5. Intercom

Best for: Support teams that want subscription status inside Intercom conversations.

Setup: Add the Intercom integration in RevenueCat for events, and install RevenueCat's Customer Profiles app from the Intercom App Store for the inbox sidebar.

The messaging integration sends events and a subscription_status attribute, but no revenue and no customer attributes. The more useful piece for most teams is the sidebar app, which shows a user's purchase history while you answer their ticket.

• Pros: Subscription history in the support inbox, simple setup.
• Cons: No revenue, no customer attributes, Intercom messaging is priced per seat plus add-ons.

Verdict: Install it for support, not as your lifecycle email engine.

6. Iterable

Best for: Teams on Iterable that already identify users by email.

Setup: Add the Iterable integration in RevenueCat with an Iterable API key. Set the $email subscriber attribute, which Iterable uses for matching, or $iterableUserId if your project is user-ID based.

RevenueCat sends Iterable purchase events for initial purchases, trials and renewals, custom events for the rest, plus revenue and attributes. Because matching uses $email, apps that already call setEmail on sign-in need no extra identifier.

• Pros: Email-based matching is the simplest identity setup, purchases land as Iterable purchases.
• Cons: Users without $email set cannot be matched, no trial-ending event, sales-led pricing.

Verdict: The easiest identity story among the enterprise options.

7. MoEngage

Best for: MoEngage customers, or teams that might switch subscription platforms.

Setup: Ask MoEngage support for a RevenueCat webhook endpoint, then add it as a webhook in RevenueCat. MoEngage documents the same pattern for Superwall and Adapty.

This is a webhook connection documented by MoEngage, not one of RevenueCat's built-in integrations, so the event mapping is defined on MoEngage's side. Confirm with MoEngage which RevenueCat events and fields it maps before you build journeys on them.

• Pros: One pattern across RevenueCat, Superwall and Adapty.
• Cons: Setup runs through MoEngage support, mapping details are not public, no trial-ending event.

Verdict: Reasonable if MoEngage is already your platform.

8. OneSignal

Best for: Push-first apps that only need subscription state for targeting.

Setup: Add the OneSignal integration in RevenueCat with your OneSignal app ID and API key, and set $onesignalUserId from the OneSignal SDK.

RevenueCat does not send events here. It keeps user tags up to date (subscription_status, active_subscription, product_id, expiration_at, entitlement_ids and similar), and only for auto-renewing subscriptions, so non-renewing purchases never appear. You can build a segment of expired subscribers, but not an email that fires the moment a billing issue happens.

• Pros: Subscription state on every profile, quick to connect.
• Cons: Tags only, no events, no revenue, no non-renewing purchases.

Verdict: Enough for push targeting, too thin to run lifecycle email on.

9. Sequenzy

Best for: Apps that want every RevenueCat event turned into tags, revenue attributes and triggers, including a trial reminder, without writing a webhook server.

Setup: In Sequenzy, paste a read-only RevenueCat API v2 key. In RevenueCat, add a webhook with the Sequenzy URL and the generated Authorization header (or HMAC signing), set to the Production environment. Set $email after sign-in, or use your login email as the app user ID.

Disclosure: I build Sequenzy, so this section describes the product. It does not rank it.

Unlike RevenueCat's own integrations, this one is built on Sequenzy's side, which lets it add things RevenueCat does not send. Each event becomes a Sequenzy event (saas.trial_started, saas.purchase, saas.payment_failed, saas.cancelled, saas.churn, saas.refund), a tag change (trial, customer, past-due, cancelled, churned) and updated mrr, ltv, plan and renewal-date attributes. A saas.trial_will_end event is scheduled 3 days before each trial ends. Matching tries the app user ID, original ID and aliases, then $email, then a lookup through the RevenueCat API. Retried deliveries are deduplicated.

• Pros: Trial-ending event, tags and revenue attributes, three-step identity fallback, email plus push and in-app in one sequence.
• Cons: No bulk import of existing subscribers, sandbox purchases count unless the webhook is set to Production, no upgrade or downgrade event, revenue is gross of store fees.

Verdict: The most complete RevenueCat mapping for apps under enterprise scale. Details on the RevenueCat integration page.

Tools without a RevenueCat integration

Klaviyo, Loops, Mailchimp, Brevo, Kit, Encharge, Userlist and Bento have no native RevenueCat integration and do not document one. To use them, route RevenueCat events through Segment or mParticle (both are native RevenueCat integrations) or write a webhook handler that calls their APIs. Budget for retries, deduplication on the event id, identity matching and your own trial reminder.

Which one to pick

• Indie or growing app, self-serve, flat pricing, trial reminders built in: Sequenzy.
• Self-serve journeys, may move between RevenueCat and Superwall: Customer.io.
• Push is the product: OneSignal for targeting, Airship or CleverTap for full journeys.
• Enterprise budget: Braze or Iterable.
• Unsure of your subscription platform, one enterprise vendor: MoEngage.
• Support context, not lifecycle email: Intercom.

Before you send, read RevenueCat vs Superwall if you are still choosing a subscription platform, and email marketing for subscription apps for the flows to build first.

Frequently asked questions

Which email tools integrate with RevenueCat?

RevenueCat's native customer engagement integrations are Airship, Braze, CleverTap, Customer.io, Intercom, Iterable and OneSignal. Sequenzy connects natively from its own side using a RevenueCat API key and webhook. MoEngage documents a webhook connection. Tools without an integration, such as Klaviyo, Loops and Mailchimp, need a relay through Segment, mParticle or your own code.

Does RevenueCat send emails?

No. RevenueCat tracks subscriptions and sends events to webhooks and integrations. You need an email or messaging tool connected to it to send trial reminders, billing issue emails and win-back campaigns.

Do RevenueCat integrations need a paid plan?

RevenueCat's current Pro plan includes every feature, integrations and webhooks included, and is free until $2,500 in monthly tracked revenue, then 1% of tracked revenue. Some legacy plans without integration access need to migrate.

How do I send a trial ending email with RevenueCat?

RevenueCat sends no event before a trial converts, because the app stores do not. Either schedule your own reminder from the trial's expiration date, or use a tool that does it for you. Sequenzy fires a trial-ending event 3 days before each trial ends.

How does RevenueCat match users in my email tool?

Each integration uses its own identifier: Braze an alias, CleverTap a CleverTap ID, Customer.io a Customer.io ID or the app user ID, Iterable the $email attribute or an Iterable user ID, OneSignal a OneSignal user ID. Set the matching subscriber attribute in RevenueCat, usually right after sign-in, or events cannot be attached to the right person.

Can I use Klaviyo or Mailchimp with RevenueCat?

Not natively. Neither appears in RevenueCat's integration list and neither documents a RevenueCat integration. You can forward RevenueCat events through a CDP such as Segment or mParticle, or point a RevenueCat webhook at your own server that calls their APIs.