Skip to main content
Not every app-store subscriber is equally reachable. Some have Apple private relay addresses. Some use Google Sign-In. Some have anonymous or incomplete account records. Some have paid in the store without a clean owned-channel path.

​
Why this matters

Migration depends on being able to:
  • Identify the subscriber
  • Reach the subscriber
  • Connect web billing to app access
  • Provide cancellation and support guidance
If one of those breaks, the cohort may not be ready for migration.

​
How Recurr handles it

Recurr segments reachability during cohort selection. Subscribers with clean identity and contact paths are usually better first-cohort candidates. Harder cohorts can be held for later, handled with additional guidance, or excluded from the pilot until the path is clearer.

​
Apple private relay

Apple private relay addresses can be reachable, but only if the sending path is configured correctly. For subscribers using Sign in with Apple private relay, the outbound email domains or sender addresses used for migration must be registered and authenticated in the customer’s Apple Developer account. If a migration email is sent from an unregistered source, the relay path can fail. Recurr checks this during readiness when Apple private relay addresses are present in a target cohort.

​
Sender setup

Recurr sends migration email through its email provider, not through the customer’s mail server. The sender identity is still customer-owned and branded. Common patterns are:
  • team@customer.com or billing@customer.com when the customer is comfortable sending from the primary domain
  • team@billing.customer.com when the customer wants to isolate migration mail from the primary domain and protect the main sender reputation
The sending domain or subdomain still needs the right DNS authentication. If Apple private relay addresses are in scope, the same source domain or sender address also needs to be registered for Sign in with Apple email communication in the customer’s Apple Developer account. Recurr checks sender authentication, relay readiness, and deliverability before a live cohort is contacted.

​
Google identity and Play billing

Google does not work the same way as Apple’s private relay. If a subscriber signs in with Google and the app has the right consented identity scope, the app may already have a usable email address. Google Play Billing itself should not be treated as the source of subscriber email or contact reachability. For Google-originated subscribers, the question is practical: does the app have an account, email, push, or other owned-channel path that can safely reach and identify the subscriber?

​
Not all subscribers need to move

Nostos is not an all-or-nothing cutover. Subscribers who cannot be safely migrated can remain on store billing while better-fit cohorts move first.