For watchRTC billing, we’ve got a straightforward approach to ensure fairness and accuracy in tracking your usage. Let’s break down how we measure those billable minutes:
- Initialization and Connection: Billable minutes commence either when the watchRTC SDK establishes a websocket connection or when the first crucial message is collected—whichever happens earlier.
- Session Duration: Upon closure of the websocket, the elapsed time is rounded up to the nearest minute.
- End Time Calculation: The end time of a session is determined by the moment the watchRTC SDK disconnects from its websocket or an approximation based on the last received message. This ensures that the billing period accurately reflects the entirety of the session.
There may be times when minutes will be excluded from billable minutes due to certain types of edge cases and application behavior. Here you will find a list of such failure types.
- Delayed Peer Connection: watchRTC collects events and logs prior to a WebRTC peer connection generation. If more than 10 minutes elapses before a peer connection is established, then all events and logs collected prior to these 10 minutes are flushed and discarded. Once discarded, they aren’t calculated as billable time.
- Server Compensation: watchRTC relies on the device clock to figure out time differences across the events in order to calculate and visualize time series data of metric values. That said, the billable time is calculated by the server, which actively checks for clock changes on the user’s device and compensates for them.
In case of a dispute in calculations, contact our support.