Entry points for Adapty Mail

An entry point is how user data reaches Adapty Mail. Whichever one you use, it carries the same three things:

• Their email address (mandatory): The destination for your emails. Without one, Adapty Mail creates no profile.
• Their customer user ID (optional, but recommended): Your own stable identifier. Adapty keeps one profile per person across reinstalls and logins, so a purchase made before they gave you an email still reaches them.
• Their subscription events feed (optional, but recommended): Trials, renewals, cancellations, and refunds, as they happen. Without it, the only sequence anyone can receive is the one for people who never purchased.

Pick the entry point that matches your app:

• Adapty: Use this if your app already runs the Adapty SDK. Adapty forwards profiles, emails, and subscription events for you, so you need no server of your own. In your app, add user identification and email collection. See Connect Adapty to Adapty Mail.
• Adapty Mail API: Use this if you already run a backend that holds this data, if your app has no Adapty SDK, or if you import subscribers from somewhere else. You post profiles and transaction events yourself. The secret key on Settings > Project authenticates the requests. See Send emails and transactions via the Adapty Mail API.
• FunnelFox: Use this if you acquire and charge users through FunnelFox web funnels. FunnelFox already holds their emails, purchases, and subscription events, and forwards them to Adapty Mail on its own — no SDK work, and no requests to write. See Connect FunnelFox to Adapty Mail.
• A combination: You can use more than one entry point at once. Adapty Mail matches people by email address. Two sources reporting the same address land on one profile; two different addresses create separate profiles, even when customer_user_id is identical.