When to collect ATT Consent

Hi ​@ole_berlin,

Thanks for reaching out. I’m happy to help.

You don’t need ATT / IDFA consent for RevenueCat to complete a purchase. RevenueCat subscriptions work the same either way.

Where it matters is attribution quality (AppsFlyer in your case):

• Purchases.collectDeviceIdentifiers() sends whatever identifiers are available at that moment (including IDFA only if the user has granted ATT) to our backend, so they can be stored on the customer profile.

• RevenueCat will then forward those identifiers to your attribution integration when a purchase event happens. So, if you want the very first purchase to be attributed using IDFA, you should request ATT before the first purchase can occur (often this means before/around the first paywall the user can buy from). If you request it later, the first purchase may be sent without IDFA (AppsFlyer may still attribute via other mechanisms, but not via IDFA).

What you’re doing now (calling collectDeviceIdentifiers() again after ATT consent) is correct and recommended.

If IDFA-based attribution for early conversions is important, request ATT at a natural moment before the first possible purchase (eg. during onboarding, or before a Paywall is shown) and then call collectDeviceIdentifiers() in the completion handler. If you’d rather avoid the prompt early, it won’t break purchases, you’ll just be accepting that some early purchases may not include IDFA for attribution.

Hope this helps, let me know if you have any other questions.

Best,

Hussain