Work with limited-type metric
Ideal for fixed-price plans, this metric type ensures that customers do not incur unexpected charges. When the predefined usage limit is reached, the system automatically rejects any further requests, keeping usage within budget.
The limited-type metric (numeric type) is used to track user usage and prevent overconsumption.
The metric system integrates with the UniBee API, which provides event-based statistics.
You can report usage data by sending events to the Event API.
The metric counting for each product, you may need specified for the productId
at Event API, default product will used if not specified
Aggregation Type of Count metric event, it increases 1 usage number
same externalEventId , no double counting
Aggregation Type of Latest metric event, it Inspect 5, event of Latest type will not be add up
if this metricCode is Aggregation Type of Sum, 5 will be add up to the current value
Normally, if the user has a subscription, the event interface returns the current value (based on the aggregation type) and the limit value for the user
When the user reaches the upper limit value set-up at Plan definision page, the event interface will return an error message (such as “reject”)to inform Multilogin that the usage has reached the upper limit.
All the metric value will be reset to 0 when the user’s subscription enters into the new billing cycle.
Event also can be revoked in the same subscription period by API UniBee API , and relative usage revoke yet.