Building a Usage-Based Product in Revenium
A step by step guide to build a usage-based product in Revenium, create a subscription, send invoices, and collect payments.
Last updated
A step by step guide to build a usage-based product in Revenium, create a subscription, send invoices, and collect payments.
Last updated
© Revenium - www.revenium.io
Start the video below for a quick review of the entire process before diving into the details below.
Use one of our many connectors in this section to begin sending usage data to Revenium.
Once you have connected an API Gateway, SDK, or other data source to Revenium, you will configure the data sources you intend to use for analytics or for monetization in Revenium.
Sources are auto-created by Revenium once your platform is connected, but you'll still want to review the sources corrected and ensure they are configured as needed.
The product configuration is where you choose how much customers will pay you for access to your products. You can define recurring non-usage based charges such as a monthly subscription fee, usage-based charges that vary based on information received from the data sources added to the product, as well as many other optional attributes.
Once Products are created, they can be resold multiple times to different end subscribers. You will create a subscription for each user who is licensed to use your product, and at the end of each invoicing period, the subscription owner will receive an invoice according to the pricing definition in the product. Need to collect automatically with a credit card? Just add your Stripe key to Revenium, that's it. No complex configuration required in Stripe. Provide the key, we'll take care of the rest.
Credentials are used to allow you to report usage against a subscription on an additional level. For example, if your customer asks you to report on usage separately for two divisions, or separate subscribers, but wants all subscribers to be charged against the master subscription, you can achieve this goal through the use of Credentials.
Credentials are configured in Revenium with a unique identifier issued by your software or API gateway, and when that identifier is sent with the usage information, Revenium will categorize that usage accordingly under the master subscription.
If you'd like to dive a bit deeper into Subscriber Credentials and other key objects in Revenium, it may be helpful to review "Key Concepts & Relationships in Revenium" as well.
Revenium allows you to notify your Subscribers when common events occur to avoid having to build this functionality into your own application. Our default notifications are generic enough to be used in most situations, but most customers choose to customize them to their own brand before going live.