One meter is sufficient when the source data does not change.
Aggregations (including compound aggregations), segmentation and pricing can then be leveraged to create different data summaries and price points. As a general rule, you should use a single Meter with multiple Data Fields when the data being collected is of a similar or related type. For example:
Suppose you want to charge your end customers on the basis of the number of logins they make and where they are logging into your service from. You could create a single Meter and define two non-numeric Data Fields: a Who Data Field to collect the required data for login counts on specific users; a Where Data Field for collecting the location of logins.
However, you might also want to charge your customers on the basis of the volume of data they upload to store on your service during a given billing period. You should then create a second and separate Meter with a numeric Measure Data Field to sum each customer's quantity of data stored.
Typically you would create a product per accounting code in your accounts receivables (AR) system. This way, when integrating with the AR, m3ter knows which product to assign to the invoice line so that revenue for the product/service can be easily identifiable and recognized.
If using commitments/prepayments or plan groups (for cross-product minimums) a separate “accounting” product can be defined in the configuration and associated with the commitment or plan group. This can then be used to account for revenue from those contractual constructs.
Login to the Support portal for additional help and to send questions to our Support team.