Skip to main content
If your subscriptions are billed through the App Store or Play Store (or RevenueCat-managed web billing), Revenue Recovery connects through RevenueCat instead of Stripe. The recovery calls work the same way; what differs is how a save is funded — Apple and Google don’t let anyone apply a discount to a subscription directly, so RevenueCat saves are redeemed by the customer through App Store offer codes from a pool you provide.

​
Connecting

  1. Go to Integrations in the sidebar (under General)
  2. Find the RevenueCat card and start the connection, or use the New workflow wizard on the Revenue Recovery Workflows page, which walks you through connecting as its first step
  3. Once connected, your RevenueCat recovery workflow appears on Workflows, alongside any Stripe workflow — each provider gets its own workflow with its own offer, triggers, and results

​
Offer codes

RevenueCat saves are funded from your Apple offer-code pool rather than a percentage discount you set in Atllas. The offer-code setup lives on the Workflows page behind Manage codes:
  • Your App Store Connect key, so Atllas can work with your offers
  • Your code batches — the offer codes you’ve generated in App Store Connect
  • Your remaining inventory, so you can see when the pool is running low
When a customer accepts on a call, Atllas texts them a redemption code right after — see Offer Texts. If your code pool runs empty, calls that would waste a member’s yes pause automatically and a banner on Analytics tells you what happened; calling resumes on its own the moment you upload more codes.
Annual-plan offers for RevenueCat campaigns are configured in App Store Connect, not in Atllas — the AI just describes that same offer on the call. See Win-back Offers.

​
Phone numbers

Atllas reads the customer’s phone number from the reserved $phoneNumber subscriber attribute in RevenueCat. See Phone Numbers for how to set it and check your coverage.