Skip to main content
Question

Inquiry about IDFA availability in Stripe purchases

  • September 24, 2025
  • 1 reply
  • 43 views
R
Forum|alt.badge.img+2

Dear RevenueCat Community,

I am using the RevenueCat SDK in my Flutter application and have implemented App Tracking Transparency (ATT) permission on iOS. When the user grants permission, I call the method Purchases.collectDeviceIdentifiers() to obtain the device's IDFA. This value is correctly set and included in the events sent through the webhooks.

In my Flutter app, users can purchase subscriptions using Stripe. For this, a web view is opened for the user to complete the payment. Once the purchase is completed and the user returns to the app, the app submit to this endpoint https://api.revenuecat.com/v1/receipts the subscription ids to upload the purchase to RevenueCat. This is how the user gains access to the app features after the purchase.

To receive purchase events centrally in my backend, I have added a webhook in RevenueCat that reports Initial Purchase and Renewal events to my endpoint.

I have observed the following:

  • For purchases made within the app (IAP), the IDFA is correctly included in the event payload.

  • For purchases made through Stripe, the IDFA arrives as 000-000-000.

  • However, properties such as IDFV or FBAnonID are sent correctly, even for Stripe purchases.

I understand that the IDFA is automatically obtained from the device during IAP transactions, but I would like to confirm if there are any limitations or specific configurations I should be aware of to have the IDFA also available for Stripe purchases through the webhook.

Thank you in advance for your assistance and guidance.

Best regards,
Roberto Cruz

This post has been closed for comments

1 reply

chris_perriam
RevenueCat Staff
Forum|alt.badge.img+6
  • chris_perriam
  • RevenueCat Staff
  • September 26, 2025

Hi ​@roberto-cruz-ae4360, the key factor here is that RevenueCat webhooks will include whichever customer attributes are present for the associated customer at the time the event is processed. There isn’t anything special about the Stripe transaction flow that includes or excludes IDFA - this is purely based on whether the attribute has been successfully collected and set.

This means that if you set the $idfa attribute for the customer (for example, via Purchases.collectDeviceIdentifiers()) prior to the Stripe transaction, the resulting webhooks will include the $idfa attribute.

However, be mindful that attributes are only synced with RevenueCat servers when Purchases.configure() is called, app backgrounded, and when purchases are made or restored. The syncAttributesAndOfferingsIfNeeded() method should be used if you wish to immediately send the attribute(s) to RevenueCat.

Terms & ConditionsCookie settingsAccessibility statement