Connect Adapty to Adapty Mail
Adapty is one of Adapty Mail’s entry points — use it when your app already runs the Adapty SDK. Adapty passes profiles, email addresses, and subscription events to Adapty Mail, which uses them to pick recipients, place each person in a flow, and attribute revenue to the email that drove the purchase.
If your app doesn’t run the Adapty SDK, send the same data from your server instead — see Send emails and transactions via the Adapty Mail API.
Adapty Mail is a standalone product. You can use it even if your paywalls, subscriptions, or analytics aren’t handled by Adapty — migrating your entire stack is not required.
To get accurate revenue data, the minimum setup is to install the Adapty SDK in observer mode and enable App Store server notifications.
Adapty Mail needs three things from your app: purchase data (so it can attribute revenue back to the email that drove each conversion), a stable user identifier, and user emails. Set up all three, then turn on sending.
1. Let Adapty track your revenue
The first step depends on whether you already have in-app purchases implemented:
- If you already have in-app purchases implemented with Adapty, you don’t need to do anything else at this stage.
- If you already have in-app purchases implemented without Adapty and don’t plan to migrate to Adapty, install the Adapty SDK for your platform in observer mode. At this stage you only need to add the SDK to your project, activate it with observer mode enabled, and report transactions. Platform guides: iOS, Android, React Native, Flutter, Unity, Kotlin Multiplatform, Capacitor.
- If you don’t have in-app purchases implemented yet and want to use Adapty, complete the steps from the quickstart guide to delegate handling purchases to Adapty.
Then enable App Store server notifications in Adapty to receive revenue-related updates directly from the App Store.
2. Identify your users
Pass a stable ID — your backend user ID, Firebase UID, or similar — either by passing it as customerUserId to .activate() at SDK startup, or by calling Adapty.identify() later (for example, at login). Either way, set the ID before any paywall is shown. The customer_user_id is how Adapty Mail matches campaigns, clicks, and purchases back to the right profile.
Platform guides: iOS, Android, React Native, Flutter, Unity, Kotlin Multiplatform, Capacitor.
3. Collect user emails
Once a user provides their email in your app (for example, at sign-up or checkout), pass it to Adapty by calling updateProfile with the email attribute. Every recipient of a campaign needs this value.
Platform guides: iOS, Android, React Native, Flutter, Unity, Kotlin Multiplatform, Capacitor.
- Always pass a stable
customer_user_id, never an anonymous identifier. If a user uninstalls and reinstalls your app, Adapty uses this ID to link the reinstall to the existing profile and attribute purchases back to the correct user. - Get explicit user consent before collecting and sending emails to Adapty. You are responsible for compliance with GDPR, CAN-SPAM, and similar regulations in your target markets.
Verify your email coverage
After implementing collection, check coverage in Adapty:
- Go to Customers → Profiles.
- Filter by profiles that have an email set.
Target at least 30–50% email coverage among your active users before launching your first campaign. You don’t need to wait for 100% — launch as soon as you reach 30%. Users who provide their email later are automatically enrolled in active campaigns when they qualify.
Email collection strategies
Most apps don’t collect emails by default. Pick the approach that matches your app’s current state.
| Strategy | Best for | How it works |
|---|---|---|
| Existing authentication | Apps with any form of login | You already have the email — pass it to Adapty after the user authenticates. |
| Email gate before the paywall | Apps without auth — health, wellness, astrology, photo editors | Add a single email input screen between onboarding and the paywall. Conversion typically runs 70–90% because users have already invested time. |
| Web paywall builder checkout | Minimal SDK work; email captured on web | The first screen of the web paywall builder collects the email and passes it to Adapty — useful for users who click a campaign before an in-app gate is live. |
| Onboarding step | Quiz-based onboarding (fitness, nutrition, education) | Place an email input 2–3 steps into onboarding. Frame it as value delivery (“We’ll email your personalized plan”) and avoid making the step skippable. |
| Adapty Mail API | Sending emails from your server, without the Adapty SDK | Send profiles to the Save profile endpoint of the Adapty Mail API. See Send emails and transactions via the Adapty Mail API. |
4. Enable sending
Come back to this step once the rest of your setup is ready. Adapty Mail disables the Enable button until you have at least one flow, with the tooltip “Set up at least one flow before enabling Adapty integration” — so finish your sending domain, checkout, campaign, and flow first. See Get started with Adapty Mail.
Turning on the integration is the final switch: events start flowing, segments start matching, and emails start sending.
- In Adapty Mail, go to Settings → Project and find the Adapty Integration section.
- Click Enable Adapty integration (or Enable if the integration already exists from a previous setup).
When enabled, Adapty sends every subscription event — new subscriptions, renewals, trials, conversions, refunds, billing issues — into Adapty Mail. These events drive segment membership, campaign routing, and stop-conditions that pause a sequence when a user converts.
The Adapty Integration section appears only for projects linked to an Adapty workspace. If you signed up to Adapty Mail directly and your project isn’t linked, the section isn’t there — send your data through the Adapty Mail API instead.
The Adapty integration toggle in Settings is not the same as the Adapty partner workspace that signed you into Adapty Mail. The partner workspace is what created your account and (if you signed up via Adapty) your brand. The integration toggle here controls event syncing — it has to be turned on per project.
Limitations
- Anonymous users: Users without a stable
customer_user_idcan’t receive campaigns. Identify them when they create an account or log in — from that point, any email they provide is matched to their Adapty profile. - Users without an email: Profiles with no email are excluded from campaign delivery and don’t appear in campaign analytics. As soon as they provide an email, they become eligible for future campaigns.