Skip to main content
Solved

Webhook Doc > Questions about presented_offering_id

  • November 12, 2021
  • 1 reply
  • 138 views
K
Forum|alt.badge.img+7
  • Kev
  • Active Member
  • 12 replies

Regarding to the official doc ( https://docs.revenuecat.com/docs/webhooks ), I have 2 questions would like to clarify.

1/ The description of presented_offering_id mentioned:

“Not available for apps using legacy entitlements.”

However I could not find the definition of “legacy entitlement”. 


2/ The presented_offering_id is listed under “Subscription Lifecycle Events Fields”. But I can create offering for NON_RENEWING_PURCHASE ​​​​​​, and I can receive this field from the webhook as well. Our application have a logic based on presented_offering_id, so is it ok to use it for NON_RENEWING_PURCHASE ? 

 

Thank you.

Best answer by tina

Hey @Kev 

Legacy Entitlements was what RevenueCat customers used before we migrated to the Offering system that you see today. This is relative to those using an SDK version before 3.x major was released. Apps will not see Legacy Entitlements unless they had this set up previously on an older version of our platform. 

 

Yes, the presented_offering_id field can also be used for non renewing subscriptions. This just lets you know what Offering identifier the customer saw when you presented your paywall. 

View original
Did this post help you find an answer to your question?

1 reply

tina
RevenueCat Staff
Forum|alt.badge.img+10
  • tina
  • RevenueCat Staff
  • 338 replies
  • Answer
  • November 19, 2021

Hey @Kev 

Legacy Entitlements was what RevenueCat customers used before we migrated to the Offering system that you see today. This is relative to those using an SDK version before 3.x major was released. Apps will not see Legacy Entitlements unless they had this set up previously on an older version of our platform. 

 

Yes, the presented_offering_id field can also be used for non renewing subscriptions. This just lets you know what Offering identifier the customer saw when you presented your paywall. 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings