Metering is how you track buyer usage of your software application in order to bill them. When you upload usage metrics (like resources levels, network bandwidth, and data storage) to Tackle, the metrics are directed to cloud providers who, then, bill your buyer.
How metering works
As a vendor, you are responsible for keeping track of your buyer's usage and any potential overages. You can either do this internally, or hire someone to do it for you. When you use Tackle, you can submit usage metrics to the cloud providers and to track and manage metering for all your marketplaces in one place.
You can use Tackle to bill all of your customers through the cloud, or you can use it in combination with other billing methods, for example, simply to track overage. If you are using a third-party vendor like Orb to track usage, Tackle offers a native integration for submitting Orb invoices to the marketplace for metering. Other partners, like Metronome or M3ter, can also submit usage metrics through Tackle to the marketplaces with the Tackle API๐.
To get started, you need:
A marketplace listing with usage-based billing dimensions
An active contract for the buyer on that listing
With that, you just need to submit metering records to Tackle to track usage for that buyer. For each buyer contract, you can submit multiple records. Each record tracks a single dimension (for example, how many users are in your product during a certain time). Depending on how you gather your usage data and how your company handles billing, you can submit usage data to Tackle one of three ways:
Create a metering record: Manually enter records in the Tackle platform by adding a few records at a time (useful for submitting true-ups).
Upload a CSV to create multiple records: Efficiently create multiple records at a time by exporting your usage data and submitting it all at once to Tackle.
Connect to the Tackle API: For ongoing, automated submission of usage data. This will require developer assistance to set up.
With all of your metering tracked in Tackle, you can:
Check the status of your submissions in the Tackle platform, or by making an API call.
Review buyers and their contracts, including dimensions and quantities, and submit charges by creating new records.
Search and filter metering records across marketplaces, products and buyers.
Export metering data for auditing or reporting purposes.
Metering for each cloud marketplace
Tackle supports metering for the AWS Marketplace, Google Cloud Marketplace, and Microsoft commercial marketplace. If you have an AWS meterable listing and an active contract on that listing, Tackle submits hourly zero quantity records on your behalf. It is possible to cancel your contract before the end of the subscription date. You must submit any outstanding usage within the allowable timeframe dictated by the marketplace. For AWS you have one hour, for Microsoft it is 24 hours, and for Google Cloud you have one hour after it was canceled with a timestamp of usage before the cancellation time.
If you accidentally submit the wrong dimension or quantity, you will need to process these changes with the cloud provider directly, but you can Contact Tackle Support๐ for assistance in escalating this request if needed. If you miss reporting usage, follow best practice guidance from your cloud provider. For more information on metering see cloud provider documentation:
Metering records
Filter and search metering records using the tools at the top of the page. You can also track statuses at any time.
In Tackle, click Metering in the left menu to see a list of metering records.
โ
Each card represents a single record and displays:
Submission date: Time and date that the metering record was created in Tackle. (To see the submission date/time, hover-over the icon next the Dimension label.
Buyer Name: The name of the company whose usage you are metering
Product Name: The name of your product you are metering
Status: The current state of this record (indicated by an icon)
Reason for that status: Hover over the status icon for further details about the status
Dimension: What you are measuring
Quantity: How much is being used
Use the search at the top of the page to search by details in the metering record (like company name or product name).
Use the filters to filter by marketplace, listing or creation date (which is the submission date).
Metering statuses
Metering statuses show the current state of your submitted usage. This helps confirm if you have successfully billed a customer or understand why a record was rejected.
There are three ways to view metering statuses and reasons:
In Tackle, go to the left menu and click Metering. Each metering record displays an icon for status (shown below). Hover over the icon for more information about the reason for that status.
Export a CSV: Both Status and Reason are column headers in the downloaded CSV
Use the API: Check statuses through an API call๐.
Status | Icon | Status Meaning | Reason |
Accepted | This metering record has been accepted by the cloud provider. | Displays date and time that the metering record was submitted to the cloud. | |
Pending | Waiting for submission or approval of this metering record. | Displays the date and time since this record has been pending. | |
Rejected | This metering record has been rejected by the cloud provider. | Displays the date that the metering record was rejected, with one of the reasons listed below. |
If a metering record is rejected, you'll also see it associated with one of the following error messages:
customer-not-entitled
: Usually, this occurs because the order was canceled or it canโt be found in the Tackle system, or the cloud provider system.duplicate-request
: For AWS, a record is considered a duplicate if a record has already been submitted for the same product, customer, and dimension within the same hour.external-access-denied
: There is an invalid configuration in Tackle (for example, user role, API credentials). Contact Tackle Support๐ for more help.external-product-misconfiguration
: For Google Cloud only, either billing isnโt enabled on a product, visibility is denied or the service isnโt activated.invalid-usage-dimension
: Usage dimensions on the metering record don't match the dimensions listed on the marketplace. To address this, double-check the spelling of your usage dimensions in Tackle and verify that they are the same dimensions listed on the marketplace.timestamp-out-of-bounds
: The usage record'sstart_time
orend_time
was invalid, likely due to a violation of cloud marketplace rules.For AWS, the
start_time
(timestamp) for usage can be up to six hours in the past - as long as the customer is still subscribed to your product. However, if the customer unsubscribes, you must send the metering records within one hour of their cancellation to avoid any issues.For Google Cloud, the
end_time
should always be in the past, and thestart_time
should be before theend_time
. Theend_time
can be up to 5 minutes in the future.
Next step: Create a metering record