๐ฑPlan eligibility
Checking exceeded quotas can be useful when users fall back from a bigger plan to a smaller one. In this case, you may end up with an exceeded quota case where the users will have feature tracking values greater than the smaller plan values.
Before swapping, you might check the features from the lower plan and get the list of features that need to be handled:
Catching Mid-Exceed Quotas
Naturally, recordFeatureUsage()
has a callback parameter that gets called whenever the amount of consumption gets over the allocated total quota right when recording the usage.
For example, customers can have 5 seats in total, but when all of 5 seats are full, you might want to re-check the amount of exceeded quota and billing separately:
Last updated