The Appflow billing cycle runs monthly based on the subscription creation date. All the usage is tracked based on the billing cycle.
Native builds
Appflow tracks usage for native builds based on build run time minutes and credits. Appflow uses the following base metric to convert native build run-time minutes to credits for each billing cycle.
1 Android build run time minute = 1 credit^
1 iOS build run time minute = 2 credit*^
*credit metrics may be different depending on the build stack used if applicable
^We only include complete minutes in the credit calculations
For each billing cycle, run-time minutes for all builds completed during that time frame get added, and the credit conversion formula is applied. The usage page shows minutes and credits per app.
If a credit limit applies to your Appflow plan, you can track your usage toward the credit limit via the usage page in the dashboard.
The Usage History section shows the cumulative minutes and credits for the current and past five billing cycles.
Live Updates (LU)
Appflow Live Update functionality tracks usage based on downloads and monthly active users (MAUs) for each billing cycle.
For downloads, each update downloaded on the user's device counts as one download. Monthly Active Users counts each unique device that downloads the updates available. All new Appflow customers will default to MAU.
Examples below provide more details on the tracking -
5 updates are deployed during the billing cycle, and 10 users download each update; the total download count will be 50.
5 updates are deployed during the billing cycle, and 10 users download each update; the total MAU count will be 10.
NOTE - Appflow added support for MAU tracking starting Jul 1, 2023
Based on this timeframe, some historical billing cycles will show N/A if no MAU data is available.
Comments
0 comments
Article is closed for comments.