Changelog - Metronome

January 12, 2026

Billing configuration API endpoints now return response bodies

The set billing provider configuration and archive billing provider configuration API endpoints now return response bodies.Previously, these endpoints returned undefined responses, which caused JSON parsing errors when using Metronome SDKs. This update improves SDK compatibility and provides a more consistent API experience.

November 14, 2025

Launch week recap: Monetization Infrastructure for AI

This week, we introduced new features that define how modern software companies monetize in the AI era. Here’s what we launched:

Pricing models built for change

AI-driven products require flexible infrastructure that can serve every go-to-market motion. We launched three new features so you can ship pricing as fast as you ship product:Seat-based credits combine the predictability of per-seat billing with usage-based consumption. Assign credit allowances per user that can be pooled across teams or assigned to individual users. Learn more about seat-based credits here and modeling subscriptions here.Packages power PLG with good/better/best tiers. Create and manage packages in one place, update pricing instantly without engineering support, and analyze adoption by package. Learn more about Packages here.Account hierarchy brings structure to enterprise billing with parent-child contract setups. Manage usage and commitments across multi-entity organizations with organization-wide visibility. Reach out to your Metronome representative to learn more.Read the full announcement here.

Invoicing that unifies every revenue motion

Managing PLG, sales-led, and marketplace motions on separate systems creates reconciliation gaps and operational friction. We launched two features to unify invoicing across every channel:PLG invoicing automates payment collection for self-serve customers. Collect payments via credit card through the Metronome Billing Console, with built-in tax calculation and payment retry logic. Learn more about PLG invoicing here.Cloud marketplace integrations now include GCP, joining our existing AWS and Azure integrations. Metronome handles usage metering and rating across all marketplaces, serving as your single source of truth. Learn more about invoicing with GCP marketplace here.Read the full announcement here.

Billing as part of the product experience

Modern billing should feel as transparent and responsive as the product itself. We launched three features to embed monetization into the customer experience:Cost preview API gives customers accurate cost estimates before they take action in the product. Show token consumption, processing costs, or credit utilization to reduce bill shock and build trust. Learn more about the cost preview API here.Embeddable billing console brings invoicing, payments, and usage tracking directly into your product. Give customers self-service access to invoices and real-time usage data. Learn more about payment through the Metronome billing console here.Customer lifecycle notifications sends real-time signals to teams and customers about trials, renewals, and credit expirations. Configure time-based notifications to engage at the right moment. Learn more about Customer Lifecycle Notifications here.Read the full announcement here.

What this enables

These capabilities provide the pricing flexibility, unified invoicing, and customer experience companies need to turn monetization into a growth advantage.See everything we shipped at metronome.com/launch-week. If you’re interested in learning more, please reach out to your Metronome representative.

November 3, 2025

Invoicing with Google Cloud Marketplace

Metronome now supports invoicing through the Google Cloud Marketplace, enabling you to send metered usage data from Metronome directly to GCP for accurate billing and invoicing.With native integrations across AWS, Azure, and GCP, Metronome makes it easy to launch faster, scale confidently, and deliver transparency to your customers.

Launch faster: Metronome handles real-time usage metering and rating so you can accelerate revenue recognition through cloud marketplaces.
One source of truth: Manage pricing, packaging, and GTM motions in a single system. Changes made in Metronome flow directly to your marketplace listings.
Build customer trust: Give customers real-time visibility into usage and spend through their cloud billing consoles, rather than waiting for end-of-month invoices.

This feature is available to customers using Contracts and follows the same setup process as our existing AWS and Azure marketplace integrations. See docs here.

October 14, 2025

September fixes and improvements

UI

Create a spend_threshold_reached notification for all values of a group key in the UI. This builds on a previous release, which enabled the ability to create a notification based on a specific group key value (e.g. notify if user_id=123 exceeds $1,000 in spend). With this update, you can now set a notification for all values of the group key (e.g. notify if any user_id exceeds $1,000 in spend).
Add a billing configuration to a contract that doesn’t already have one in the UI.
Archive a billing provider on a customer in the UI. Archived billing providers can be reassigned to new customers. If you archive a billing provider that is attached to an active contract, the configuration will be archived immediately and will no longer bill to the associated destination.
Edit the rate type of a recurring commit in the UI.
Improved search accuracy in Products and Rate Cards tables.
View product ID in commit/credit metadata flyover.
Improved formatting of our Audit Logs in the UI.
New filtering on the rate card table to allow users to hide disabled entitlements and archived products.
Products within the rates table now display the attached billable metric on hover.

API

Create a spend_threshold_reached notification for all values of a group key through the API.
Add a billing configuration to a contract that doesn’t already have one through the API.
Archive a billing provider on a customer through the API.
Edit the rate type of a recurring commit through the API.
v1.0.0 versions of our Node, Go, Python, and Ruby SDKs are available.

September 24, 2025

Make advanced contract overrides in the Metronome app

You can now encode advanced overrides when creating or editing a contract directly in the Metronome UI. This makes it easy for deal desk and finance teams to model complex enterprise discounts without engineering involvement.Examples include:

Apply a one-off discount for a specific customer org_id shown on invoices.
Dimensional pricing examples include: Apply a 10% discount on Data Storage usage only in us-east-1 and us-west-1 regions.
Apply a 5% discount only when compute_type is batch across all model types.

Contract overrides in the UI are available to customers using Contracts. See docs here.

September 24, 2025

Custom Reports

Custom Reports provides access to custom Metronome datasets in CSV format without needing to set up a full Data Export pipeline — helping unblock critical revenue recognition, compliance, and financial reporting. These reports are available for download in the Metronome app.To get started, contact your Metronome Solutions Architect with your reporting requirements. Once the report is configured, you can trigger it from the Reports tab in the app and download the results as a CSV.Custom Reports is a paid feature. Reach out to your Metronome Solutions Architect to learn more. See docs here.

September 18, 2025

Customer Lifecycle Notifications

Customer Lifecycle Notifications deliver real-time webhooks for contract, credit, and commit events, with built-in offset logic to support in-product, internal, and customer-facing workflows.This feature:

Supports time-based events (e.g. when a contract begins or ends) and write-based events (e.g. when a contract is created or edited).
Enables flexible time-based offsets so you can trigger actions before or after events.
Keeps your systems and workflows in sync without polling, manual tracking, or brittle scripts.

Use cases include:

Internal alerts: Pipe events into Slack, Salesforce, or your CRM to give GTM teams more timely notifications on renewals and expansions. Notify engineering on contract changes to ensure entitlement systems are synced and running properly.
In-product experiences: Trigger upgrade nudges, trial reminders, or credit update notifications directly in your app.
Customer-facing communications: Connect to email or messaging systems to keep customers informed about renewals or changes before they happen.

Customer Lifecycle Notifications are available to all customers on Contracts and/or Plans in the Metronome app and API. See docs here for more information.With the launch of Customer Lifecycle Notifications, we’ve introduced a unified Notifications UI (replacing Alerts). The new experience brings all notification types into one place:

Threshold: usage or spend-based alerts
Offset: customer lifecycle notifications with time-based offsets
System: default customer lifecycle notifications with no configuration needed

The updated UI includes a condition builder for defining custom notification logic, along with detail pages showing policy previews and payload previews for easier testing and debugging.

September 11, 2025

New documentation experience

We’re excited to share a major upgrade to Metronome’s documentation experience—bringing intelligent search, interactive learning tools, and a more intuitive structure to help users navigate, understand, and leverage our billing architecture.These enhancements are designed to streamline onboarding, accelerate development, and elevate the overall documentation experience.

What’s new

Ask AI

AI-powered chat interface embedded directly within documentation, allowing you to ask conversational questions about how to use Metronome to set up and maintain your billing architecture.

API playground

Interactive API explorer built into documentation pages. You can craft requests, execute them, and examine responses in real time without navigating away.

Improved search and information architecture

Upgraded search functionality with enhanced indexing, optimized relevance ranking, and natural-language understanding to surface content more accurately.
Revamped information architecture reorganizes content into a cleaner, more intuitive hierarchy—making it easier to navigate topics, concepts, and reference material.

Expanded guides

Added additional guides focused on helping Metronome users getting started quickly such as Planning Your Billing Architecture, Getting to an Invoice, Testing Strategy, Production Checklist.
Updated core API usage documentation with refreshed guides on Authentication, Idempotency, and Responses

Updated API reference descriptions

Each endpoint now includes:

What the endpoint does
Why you would use it
Important caveats or usage notes

September 10, 2025

August fixes and improvements

UI

Select contracts data when setting up your data exports in the UI.
Edit the priority of both contract-level and customer-level commits in the UI.
Select a date preset when creating a contract in the UI.
Access a set of quick actions on the customer page by clicking the ellipsis in the UI. You can add a contract, add a plan, manage custom fields, add ingest alias, and archive the customer.
Updated Billable Metric descriptions to provide additional guidance around the use case for each type.

API

Edit the priority of both contract-level and customer-level commits through the API using the edit a commit endpoint.
Create products through the API with custom fields attached.
Create scheduled charges through the create contract endpoint with custom fields attached.
View the “type” of invoice line items in our API. You can see this field in the get an invoice, list invoice breakdowns, and list invoices endpoints.
v0.3.0 versions of our Node, Go, Python, and Ruby SDKs are available.
Add a “uniqueness_key” parameter when using our edit contract endpoint to ensure changes are applied once.

August 15, 2025

Invoice breakdowns in Data Export

We’ve introduced Invoice Breakdowns in Data Export, giving you daily and hourly granularity on invoice and line item spend—directly in your data warehouse.This feature makes it easier to:

Build usage analytics dashboards with daily or hourly consumption trends
Track revenue recognition and monitor daily revenue
Identify peak usage periods throughout the month for capacity planning and cost optimization
Generate detailed billing and finance reports for finance teams and customer success
Troubleshoot billing disputes by examining usage patterns throughout the calendar month
Power real-time cost monitoring and alerting systems

Invoice breakdowns in Data Export are available to customers using Contracts and/or Plans. See docs here for more information. If you’re interested in enabling this feature, reach out to your Metronome representative.

August 5, 2025

July fixes and improvements

UI

Contract edits now support setting a Stripe billing provider after the contract has been created.
Add a prepaid or postpaid commit for a customer in the Metronome UI without generating an invoice. This is useful when invoicing contract commitments outside of Metronome, or when migrating already-billed credits or commits within Metronome.
Contract names can be edited through the UI.
Filter preferences on the Contracts and Plans Table as well as the Invoices table will be saved. When you customize how you view invoices, contracts, or plans, your preferences are automatically saved and are persistent across each customer page.
View the history of billable metric changes on a product in the Metronome UI.
Create a billable metric directly from the product creation page.
View IP address and user agent in the audit logs in the Metronome UI.
Commits now contain metadata on when they were created. This can be viewed in the UI through Commit->View metadata.
Design components now have consistent colors across the whole platform.
Users can now filter and view archived products within the UI.
Search functionality has been added for all alerts attached to a customer.
1Password will now only recognize password-related form elements, ignoring all others.
Added space visualization for pricing group keys/values, making leading and trailing spaces visible to users.

API

The Search events endpoint allows you to fetch matched billable metrics and customers by transaction ID (last 34 days). This endpoint can help with testing your Metronome integration.
Add a prepaid or postpaid commit for a customer in the API without generating an invoice. This is useful when invoicing contract commitments outside of Metronome, or when migrating already-billed credits/commits within Metronome. You can set the “do_not_invoice” field in the API when creating a new commit using the /v1/contracts/customerCommits/create, /v2/contracts/edit, and /v1/contracts/create endpoints.
Contract names can now be edited through the API. Provide update_contract_name in the v2/contracts/edit API to update this field. Setting the value to null will un-set the name.
Commits now contain metadata on when they were created. This can be viewed in the API under commit.created_at in the v2/contracts/get, v1/contracts/customerCommits/list, and v2/contracts/list endpoints.
v0.1.0 and v0.2.0 versions of our Node, Go, Python, and Ruby SDKs are available.

Integrations

Send Metronome events to Slack without building a custom webhook handler.

August 4, 2025

Use group keys to set budgets across users, teams, and projects

Metronome now supports spend-based alerts scoped to group key values, giving customers a powerful way to monitor usage and set budgets across users, teams, projects, or any relevant dimensions.These alerts give customers the spend visibility and controls needed to avoid billing surprises and proactively manage spend.Alerts can be triggered when spend for a specific group key value crosses a defined threshold.Examples include:

user_id = 123 exceeds $1,000 in spend
project_id = ai_lab consumes more than 100 AI credits

This is especially useful for seat-based credit models, where tracking usage and credit consumption at the user or cohort level is critical. See our docs on launching hybrid pricing models here.This feature is available to all customers using Contracts. See docs here.

August 4, 2025

Seat-based credit pools

Metronome supports seat-based credit pools, a pricing model where each seat includes a fixed number of credits that are shared across the entire customer account.For example, if a customer has 100 users and each user gets 50 credits, the organization has a shared pool of 5,000 credits.This model is widely used by AI companies and is especially valuable for teams launching seat-based plans with usage entitlements, such as AI credits, included per seat.This feature builds on two foundational primitives in Metronome: subscriptions and recurring credits or commits. With seat-based credit pools, you can now link a recurring credit directly to a subscription. When the subscription quantity changes, such as when a customer adds or removes seats, Metronome automatically adjusts the credit balance. There is no need to build or maintain custom provisioning logic.This makes it easy to:

Charge per seat and grant credits to a shared pool
Automatically adjust credits when seats are added or removed
Track usage against the pool and set spend alerts by user or team. See our docs on creating spend alerts by group key here.

You also have the flexibility to implement seat-based credit pools based on your existing systems and workflows.

Using Metronome only: Create customers and contracts with a subscription and linked recurring credit. Then, send Metronome the increments or decrements when customers add or remove seats.
Using Metronome and Stripe: Continue using Stripe for subscriptions and Metronome as a credit add-on. Create a $0 subscription in Metronome and link it to the recurring credit. Then, send Metronome and Stripe the increments or decrements when customers add or remove seats.

This is the first out-of-the-box solution in the market for seat-based credit pool models. Other vendors require custom workflows and engineering effort. With Metronome, you can model this pricing pattern cleanly and easily adjust credit burndown rates, experiment with new pricing, or launch new usage-based add-ons without engineering time.By removing the need to build or maintain homegrown tooling, this feature helps you:

Launch and manage seat-based credit pools with ease
Reduce engineering effort
Speed up financial reporting and reconciliation
Improve the end-customer experience with real-time transparency and controls

This feature is available to all customers using Contracts. See docs here.

August 1, 2025

Embeddable dashboard for credit and commit balances

We now have an embeddable dashboard for credits and commits that gives customers real-time visibility into their remaining balances, drawdown history, and expirations.

This out-of-the-box dashboard gives customers insight into:

Remaining and historical commit/credit balance
Grant and deduction history
Access schedules
Relevant metadata (such as expiration)

Give customers a way to monitor and understand their spend, without requiring custom engineering work on your end. Customers can track their spend, see when credits expire, and understand which products are using their balance, all within their billing dashboard experience.This feature is available to all customers using Contracts. See docs here.

July 23, 2025

Threshold billing and auto-recharge

Metronome now supports threshold billing, giving customers more options to balance customer adoption and company safeguards for their PLG motion.

What’s new

Payment-gated commits: manually create a commit which is gated on successful payment collection. This can also be used to power threshold billing and hybrid subscription models where payment is required before access. See docs here.
Spend threshold billing: bill customers when they hit a defined spend threshold. This option balances low customer friction with automated company safeguards against runaway usage or fraud. See docs here. How it works: Set an invoice spend threshold on the contract via the create contract flow.
When a user hits their spend threshold, you are alerted via webhook and a prepaid commit is issued, bring the total outstanding spend for the customer back to $0.
Configure whether the release of the commit should be gated on successful payment collection.

Example: “User hit $100 of usage, trigger an invoice. Payment is successful, release the commit to return outstanding spend to $0.”

Auto-recharge (prepaid balance thresholds): automatically charge for and top up a customer’s balance when it falls below a threshold. This minimizes potential fraud risk via a prepaid model while ensuring uninterrupted product access for end users. See docs here and view our launch guide for prepaid credits here. How it works: On contract creation, configure the recharge threshold that triggers a top up and the amount the customer should be recharged to.
When a user hits the threshold amount, you are alerted via webhook and a prepaid commit is issued.
Configure whether the release of the commit should be gated based on successful payment collection.

Example: “User’s balance fell below $20, automatically attempt payment to bring it to $50. Payment is successful, release the commit.”These features are available to all customers on Contracts. To learn more about common billing models and how to evaluate them for your business, see our blog post here.

July 15, 2025

Set up multi-entity billing

Metronome now supports multi-entity billing with Stripe, allowing customers to connect multiple Stripe accounts to a single Metronome environment and configure which Stripe account each contract on a customer should be billed to. As part of this, clients can also customize invoice presentation and other settings on a per Stripe account basis.This unlocks the ability for large-scale enterprises to manage billing complexity from operating across multiple geographies or business units. For example, companies billing North American and European customers from separate Stripe entities like “Stripe NA” and “Stripe EU” can now do so in a single Metronome environment.This capability helps companies to scale internationally, while staying compliant with local regulations.Multi-entity billing is available to all customers using Contracts. See docs here.

June 26, 2025

Scope credits and commits to specific pricing or presentation group values

You can now scope credits and commits to specific pricing group values or presentation group values, in addition to the existing support for products and product families.This gives you more control and flexibility when defining how credits and commits apply—whether you’re supporting advanced enterprise contracts or running targeted promotions.Example use cases:

Enterprise contract commits: A customer negotiating an enterprise contract may only plan to use a product in two specific regions, where region is a pricing dimension. You can now create a commit that only applies to usage within those regions.
Per-user credit grants: A user on a Teams plan participating in a research study can be granted a free $10 credit as a thank you for their time. You can ensure that only this user can consume the credit—other users on the Teams plan won’t have access to it.

This feature is available to all customers using Contracts, in both the UI and API. For customers using Data Export, a new field called specifiers will also be exported on the commits, balances, and recurring_commits_and_credits tables.See docs here.

June 13, 2025

Edit recurring commits and credits

It’s now possible to edit the following fields on recurring commits and credits:

ending_before
access_amount
invoice_amount (for commits)

When a recurring commit or credit is updated, all child commits with future-dated access schedules will also be updated automatically. Active or expired child commits will remain unchanged and can be modified individually using the edit contract flow.This feature makes it easier to keep customer contracts aligned with evolving pricing strategies—without needing to create new recurring commits or duplicate contract logic.Example:A pricing tier may currently charge $30 a month for 50 credits. This is represented on customer contracts as a recurring commit with an access_amount of 50 credits and an invoice_amount of $30.If the cost of delivering the service decreases and the plan is to offer more credits at the same price, the contract can be edited to increase the access amount from 50 to 70 credits per month—without creating a new recurring commit.Editing recurring commits and credits is available in the UI and API to all customers on Contracts who have contract editing enabled. See docs here.If you do not have contract editing enabled and would like to have access, please reach out to your growth representative.

June 13, 2025

Support for seat-based subscription billing

Metronome now supports seat-based subscription billing models, giving customers the ability to encode subscription pricing directly in Metronome. Subscriptions include recurring platform fees or seat-based subscriptions.This enables teams to power both subscription and usage-based pricing within a single platform. Subscriptions in Metronome are powered by our centralized rate card, making it easy to schedule price changes, apply discounts, and launch new products without requiring engineering support.For example, changing a price for a subscription is as simple as updating it on the rate card. The new price will automatically and immediately propagate to all contracts using that subscription, with no migration or additional work needed. See docs here on how to update pricing for subscriptions.Seat-based subscriptions are available to all customers using Contracts, in both the UI and API. See docs here.We’re continuing to invest in expanding our subscription capabilities. Reach out to your Metronome growth representative to learn more.

May 20, 2025

April fixes and improvements

UI

View the billing provider for a specific contract on the Contracts Overview page under Contract details.
New dropdown in the dashboard sidebar lets you quickly create a customer, billable metric, product, rate card, or alert.
Line items are no longer created for pricing group keys with no usage data. Note that unlike usage products without a pricing group key, Metronome does not create line items for each pricing group key unless it has usage data.
Search weights for Products have been adjusted to deliver more accurate and relevant results.

API

getCustomer and listCustomers endpoints now return a created at timestamp for customers.
Product tags are now included in the getInvoice, listInvoices, and listBreakdownInvoices endpoints to make it easier to view product metadata for any invoice.
Rate cards can now be archived from both the UI and API, making it easier to manage your production environment. API docs here.

Integrations

Metronome customer_id is now included as metadata on Stripe invoices, helping you track how customer ids are mapped between Metronome and Stripe.

May 8, 2025

Remove overrides and archive commits and scheduled charges

You can now archive commits and scheduled charges as well as remove overrides when editing a contract.

In the UI, select Edit contract, scroll down to Overrides, and use the three-dot menu to remove an override.Customer-level commits are also archivable through the UI and API endpoint.See API docs here.

May 5, 2025

Support for NZD and SGD currencies

We’ve added support for New Zealand dollars (NZD) and Singapore dollars (SGD) to our list of supported fiat currencies.For the full list of supported currencies, see docs here.

May 1, 2025

Ruby SDK

We’ve expanded our SDK library with a new Ruby SDK, making it easier to integrate Metronome into your Ruby applications.Access the Ruby SDK here.Learn more about our SDKs in our docs here.

April 29, 2025

Updated UI for creating and editing contracts, customer-level commits, and customer-level credits

We’ve shipped UI updates to simplify creating and editing contracts. The new UI highlights important inputs front and center while maintaining flexibility for advanced use cases.You can now more easily create and edit contracts, customer-level commits, and customer-level credits. The UI also supports creating recurring commits and recurring credits—previously only available through the API.The updated UI helps:

Deal desk teams quickly create complex enterprise contracts with commitments and discounts.
Finance and billing operations teams efficiently manage workflows like granting free credits, extending commit terms, and correcting manual entry mistakes.

This feature is available to all customers using Contracts.

April 9, 2025

Edit rates in the Rate Card UI

Previously, updating a rate in the UI was done by appending a new rate. Now, you can also edit existing rates in the Rate Card UI using the Edit rate button.The form is pre-populated with the existing rate values, making it easier and more intuitive to update pricing.

April 2, 2025

Usage threshold alerts supported on Contracts

Customers using Contracts can now set usage threshold alerts for any billable metric.How it works: The alert monitors raw usage volume, sums usage across active billing periods, and triggers when a defined quantity threshold is reached.This makes it easy to track usage milestones and surface potential issues before they lead to billing surprises or customer escalations.Example supported use cases include:

Internal workflows: Alert account teams when customers approach usage limits, enabling proactive outreach.
Detect misuse or misconfiguration that could have financial impact to the business.
End-customer experience: Power in-product alerts when usage nears a limit and allow customers to set their own usage thresholds alerts.
Enable contextual upsell nudges based on actual usage.

This is available to all customers. See docs here.

April 2, 2025

Contract editing

Clients now have additional flexibility to self-serve edits to contract terms—including commits, credits, scheduled charges, and more—directly from Metronome’s UI or API.Contract editing allows you to react quickly to business needs, such as correcting manual entry mistakes or adjusting a contract mid-period to reflect an upsell or change in terms.This feature is available to all clients using Contracts. Read more in our docs.

April 1, 2025

Support for weekly frequencies for billing, recurring commits, and credits

In addition to monthly, quarterly, and annual billing frequencies, Metronome now supports weekly billing frequencies. This gives you more flexibility to bill customers at the cadence that best balances the customer experience and revenue collection.Weekly frequencies are also supported for recurring commits and recurring credits, enabling even more granular contract configurations.This feature is available to all customers using Contracts, in both the UI and API. See our API docs for more information on how you can set usage_statement_schedule to weekly for billing, or set recurrence_frequency to weekly for recurring credits and/or commits.

March 26, 2025

In Tempo: Spring 2025 changelog

What’s new

We’re excited to share our first changelog of the year!Highlights from this update include:

Expanded alert functionality for contract balance and spend threshold alerts
New invoice breakdowns API
Expanded business model support for recurring commits & credits, commit rates, and commit-specific overrides
New Metronome Trust Center
Continued Metronome 1.0 -> 2.0 parity investments

Alerts

Resolved notifications on contract balance alerts

For contract balance alerts, we now have the ability to send a “resolved” notification when the alert transitions from in-alarm to resolved. This provides an accurate, real-time indication of when customers have purchased additional credits or commits, helping to manage customer transitions between entitlement states. See docs here. If you are interested in turning on this functionality, reach out to your Metronome representative.

Custom field filters on spend threshold alerts

Alerts can be configured to track spend for contracts with a particular custom_field. This allows you to target your alerts to specific contracts or subsets of contracts. For example, you could segment your customer base into customer cohorts by labeling each contract with a custom_field, and easily implement different spend threshold alerts for each cohort. See docs here.

API investments

Invoice breakdowns

List daily or hourly breakdowns of customer invoices, optionally filtered by status, date range, and/or credit type. Invoice breakdowns provide consistent and repeatable record of customer spend, credits, and commits broken into hourly or daily buckets to help you power reliable customer-facing revenue analyses and spend dashboards. See API docs here. For more details on leveraging this data to power customer-facing dashboards, see docs here.

List balance calculation per commit or credit

The /listCustomerBalances API now returns the amount of a specific credit or commit that a customer has access to use at this moment by summing up all of the ledger entries for a commit or credit. The API allows you to easily display this information to customers, as well as facilitate downstream Finance, RevOps, and GTM workflows based on credit or commit balances. See docs here.

Uniqueness key on CreateCustomerCommit and CreateCustomerCredit APIs

/createCustomerCommit and /createCustomerCredit APIs now include the option to add a uniqueness_key to the request body to prevent creating duplicate commits or credits on retry. Request retries with a previously-consumed uniqueness key will fail with a 409 Conflict Error.The /listCustomerCommits and /listCustomerCredits APIs also now include the uniqueness_key. See docs here.

Product custom fields in invoice and rate card APIs

Product custom fields are now available in the /getInvoice, /listInvoices, /listRateCards and /getRateSchedule API endpoints. See docs here.

Prevent updating contract end date to before end_timestamp of existing finalized invoices

In the /updateContractEndDate API, you can now set a flag to prevent you from ending the contract earlier than the end_timestamp of existing finalized usage invoices on the contract. This scenario can happen if a contract is created, a usage invoice is finalized, and the end date of the contract is later changed to end before an existing finalized invoice. See docs here.

If you would like to prevent backdating contract end dates before finalized usage invoices, you can set allow_ending_before_finalized_invoice=false in the request body.
In the frontend, we always allow backdating the contract end date. There is a warning in the UI: “Finalized invoices will be unchanged (void scheduled invoices to remove them, and void and regenerate usage statements to incorporate the new end date).”

Business model support

Recurring commits & credits

As part of a subscription or contract, organizations commonly allocate a fixed amount of usage to a customer. The amount generally scales with the tier of the plan, such as Good, Better, and Best. Organizations adopt this model to get the benefits of subscriptions with fixed recurring revenue and usage-based billing with collecting on overages. Model this behavior in Metronome by setting up a recurring credit or commit on a Contract.You can create a recurring credit or commit on a Contract via the /createContract API. You can specify a recurrence period distinct from the usage statement cadence and optionally choose to prorate the first and/or last month’s commit value. Once created via API, you can view recurring credits and commits in the UI and data export. See docs here.

Commit rates and commit-specific overrides

Companies often prefer that their customers commit to spending thresholds upfront to generate more predictable revenue. To incentivize customers to do so, companies will offer discounts for larger commitments. Metronome provides the flexibility to model these discounts in two primary ways:

Reduce the cost basis for the commit
Create commit-specific overrides on the customer contract

For advanced billing structures, Metronome also supports a third way to discount commits: encoding commit rates on a rate card, so you don’t need to use commit-specific overrides for every customer who makes a commitment.With Metronome’s built-in logic, you can manage both committed rates and fallback rates that kick in once the committed amount is used up—no engineering headaches required. The system automatically handles the transition to the fallback or on-demand rate, ensuring a smooth process without any manual intervention.See docs here, and additional use-case details here.

Composite charges with >100% rate

You can set a composite charge to have a percentage rate that is greater than 100%. This change increases the flexibility of composite charges to support creative pricing and discounting schemes. Learn more about creating composite charges here.

UI improvements

Lifetime billings on the Customers list page

In our Customers list view, we now show the total lifetime billings for each individual customer. This makes it easier to find the customer you are looking for if you have multiple customers with similar names.

UI badges for customer commits and credits status

We have added badges in the UI indicating if a commit is expired, upcoming, pending, or voided. This makes the status of each commit more easily understandable in the default views. Expired commits are hidden by default, but can be exposed by selecting “Expired” within the status filter.

Security

Metronome Trust Center

Trust and security are core to our commitment to our customers. The Metronome Trust Center provides a centralized location for our latest SOC reports and information related to common questions around security.

IP Address and User Agent in Audit Logs

IP address and user agent fields are now included in audit log entries. Since this information was not previously tracked, audit logs from before 1/8/2025 will not include these two fields.

Integrations

Control service period reporting in Stripe

You can choose to have Metronome set the “Invoice Date” (also called the “effective_at” date) at the top of your Stripe invoices with the last date of the invoice’s service period. This can simplify revenue reporting processes which key off of Stripe, ensuring usage invoices are tracked against the correct period. If left unset, by default Stripe populates this date with the date the invoice is finalized. See docs here.

Data Export

Balance calculation per commit or credit

The commits and balances tables now include a balance field, which reflects the current balance of the commit as of the time the exported report was generated.The balance will match the sum of all ledger entries with the exception of the case where the sum of negative manual ledger entries exceeds the positive amount remaining on the commit. In that case, the balance will be 0. All manual ledger entries associated with active commit segments are included in the balance, including future-dated manual ledger entries. See docs here.

Metronome 1.0 → 2.0 parity investments

In October, we launched Metronome 2.0—a major milestone in Metronome’s mission to turn billing from a bottleneck into a growth lever. Since then, in addition to the net new feature development noted above, we have been working to complete the process of extending support for existing Metronome 1.0 features to Metronome 2.0.

AWS and Azure Marketplaces

Our native AWS and Azure integrations make it easy to use Metronome’s usage aggregation and pricing capabilities while still invoicing customers through marketplaces. In addition to setting a global billing provider per customer, billing providers can also be assigned per individual contract, providing flexibility to support multi-cloud customers. This allows you to deploy a multi-cloud commitment GTM motion, unlocking larger volumes of committed customer spend while Metronome manages the tracking of the commitment across clouds. See docs here.

International Currencies

We support 16 international currencies, providing you with a single platform that can handle usage-based billing for all of your international business lines, allowing you to move faster and simplify your billing operations. See docs here.

Invoices and usage embeddable dashboards

Embeddable dashboards allow you to embed Metronome usage data and customer invoices into your website, making it easy to integrate world-class usage and cost visibility into your product experience and increase customer trust. This is the first step to getting to parity with our plans version of this feature, so that we can build beyond it. See API docs here.

Get in touch

Enjoying our changelog? Have feedback on how we can improve it? We’d love to hear from you! To learn more about these features, get in touch with us here or reach out to your Metronome representative.

October 17, 2024

Metronome 2.0

As we enter the next phase of innovation with Metronome 2.0, we’re thrilled to roll out the latest features that are designed to make pricing and billing simpler, faster, and more flexible. From a revamped pricing data model to enhanced commit contract functionality, our platform now gives you more control than ever to fine-tune your pricing strategy and scale effortlessly. Whether you’re looking to manage rate cards from a single source of truth, customize pricing down to the granular level, or automate workflows to streamline customer billing, Metronome 2.0 has you covered.While there are hundreds of features included in Metronome 2.0, this changelog highlights key investments we’ve made to the platform:

Simplify pricing updates with a centralized rate card model

Use centralized rate cards as your single source of truth for pricing. Easily manage and roll out updates for all customers—whether on standard or custom pricing—from a single place. Learn more about managing rate cards.

Offer custom pricing with granular customer configuration

Customize pricing with flexible discounts and overrides to any part of your list pricing, without needing new one-off plans. Make granular, time-based adjustments for individual customers and schedule updates to apply instantly, in the future, or retroactively. Learn more about customizing pricing.

Win high-value customers with flexible commit contracts

Empower your sales team to secure long-term commitments with our flexible commit model. Support prepaid or postpaid options, adjust schedules, and implement rollover or overage policies. Easily manage and update contract terms and balances throughout the customer lifecycle, from land to renewals and expansions. Learn more in our enterprise commit launch guide.

Segment pricing with dimensional pricing

Optimize your pricing by offering different price points based on factors such as customer segments, markets, regions, or costs. Easily segment a single metric by any dimension using pricing group keys and apply targeted discounts where they matter most—without creating multiple billable metrics. Learn more about dimensional pricing.

Design fully flexible SQL billable metrics

Easily construct queries on raw events with minimal pre-aggregation. Iterate pricing and backdate changes without altering your data pipeline or re-ingesting events. Learn more about billable metrics.

Offer convenience and choice with multiple contracts per customer

Allow an organization to create multiple active contracts, from PAYG to enterprise agreements, each tailored to specific projects or teams. Learn more about customer and contract provisioning.

Improve transparency with flexible billing presentation

Customize your in-product billing dashboard to give customers clear visibility into their real-time usage and spend. Allow them to track cost breakdowns by any metrics and time frames for better control over their budget. Learn more about building customer dashboards.

Streamline the customer journey with automated workflows

Improve your product experience by automating every step of customer purchase and billing journey. With end-to-end API support, streamline key workflows both in-product and across business systems—from customer acquisition and provisioning to usage tracking and invoicing. Learn how in our API documentation.

Scale confidently with API-driven pricing management

Manage your entire pricing and packaging with APIs. Enable efficient pricing updates, contract adjustments, and scalable billing processes. Ensure a consistent billing experience as your customer base expands and your pricing structures grow more complex. Learn how in our API documentation.

Provide customers peace of mind with spend control

Give customers control over their spend with configurable alerts, allowing them to set custom budgets for projects and receive notifications when thresholds are exceeded. Learn more about customer spend controls.

Simplify targeted engagement with custom alerts

Create flexible alerts for specific customer segments, sales motions, or promotions. Send relevant, real-time signals to your internal teams. Learn more about creating and managing alerts.

Increase sales efficiency with Salesforce data sync

Equip your sales team with real-time insights for upsells, cross-sells, and churn prevention. Metronome syncs customer spend, usage, and commit balances to Salesforce daily, letting your team focus on selling, not data gathering. Learn more about syncing billing data into Salesforce.

September 25, 2024

In Tempo: Fall 2024

What’s new

API investments

Void invoice API

Programmatically void a finalized invoice via the API. This functionality is useful if you have mis-billed a customer or need to adjust and re-generate an invoice that has already been finalized. See API docs here.

SDKs

We have published beta versions of SDKs in Go, Python, and TypeScript to provide a smoother developer experience for the Metronome APIs.

Usage threshold reached alerts are now evaluated in real-time

This alert type sets a threshold for a specific billable metric and labels a customer as ‘in_alarm’ if the customer’s usage for their current billing period (or previous billing period if events are received during the grace period) reaches or goes above your set threshold. This alert type is now measured throughout the day, so you will be alerted as soon as a billable metric passes the threshold. See docs here.

Invoice total reached alert

This alert type sets a threshold for an invoice total and sends a notification if any of the customer’s active invoices reaches or exceeds the configured threshold. Note that the invoice total used is the net total after any credits or other adjustments have been applied. This alert can also be configured to filter specific invoice types - for example, it can be set to only alert on usage invoices. See docs here.

Business model support

Automatic mid-month seat purchase invoices

We’ve expanded our seat-based billing functionality. Now, when end-customers add new seats mid-period, you can opt-in to have prorated seat purchase invoices generate automatically. Every hour, Metronome assesses the latest seat usage for each customer with an active seat plan and compares it to the number of seats already billed for the period. If the current usage is higher, Metronome automatically generates a prorated seat purchase invoice. See docs here. If you are interested in turning on this functionality, reach out to your Metronome representative.

Cross-invoice tiering

Usage can now be tiered beyond the invoicing period. Clients can configure how often the tier count should reset, providing the flexibility to tier usage over multiple billing periods. This update allows you to set a new ‘tier_reset_frequency’ value when modeling a usage-based tiered charge on a plan. If set to 0, the tier count does not reset for the duration of the customer plan. If set to any positive integer value X, the tier count will reset every X billing period. See docs here.

Step 1: Select ‘Edit tier reset period…’

Step 2: Choose how often the tier count should reset

Credit grant rollovers

Configure rollovers on new or existing credit grants. If the credit grant expires, all or a portion of the remaining credit grant balance will roll over into a new credit grant. See API docs here. If you are interested in this functionality, reach out to your Metronome representative.

Backdate credit grants

Credit grants can now be backdated in the UI. This functionality is useful when, for example, you may have mis-billed in a prior month or need to give a customer a credit applicable to a previous month’s bill. Using this functionality, you can create a credit grant backdated to that prior month and then void and regenerate that month’s invoice, allowing the invoice to draw down from that new backdated credit. If you are interested in this functionality, reach out to your Metronome representative.

UI improvements

Alert status visible on the customer’s alerts page

The state of an alert (‘evaluating’, ‘ok’, or ‘in_alarm’) can be viewed on the customer’s alerts page in the UI.

Customer with alert status ‘in_alarm’

Data export improvements

New ‘customer_plan’ table in data export

This table includes individual customers’ plan information, including fields like ‘created_at’, ‘starting_on’, ‘ending_before’, and ‘custom_fields’ which facilitates downstream reconciliation and analysis workflows. See docs here.

Get in touch

June 10, 2024

In Tempo: Spring 2024

What’s new

API investments

Create and manage billable metrics over API

Programmatically create, archive, and get billable metrics through the API. This is a longstanding customer request and we’re excited to support the automated creation of billable metrics. Previously, billable metric creation was done solely through the UI. See docs here.

Define how alerts should be evaluated using the API and UI

The ‘Create alerts’ endpoint can be configured to evaluate immediately for all customers who meet the alert threshold or evaluate only for future updates on customers who meet the alert threshold.The default behavior is to evaluate on all customers, but in certain instances, for example creating alerts on an existing set of customers, the preferred behavior may be to only evaluate this alert for future updates (e.g. new usage, customer updates, plan updates, etc.). See API docs here.

Choose alert evaluation behavior in the UI or API

Force re-evaluation of alerts for a customer

While alerts are continuously evaluated, Metronome only triggers notifications when an alert changes state. This could lead to unintended behavior if your systems reset their state in response to changes in a customer’s plan and an alert re-notification is expected. You can force a re-evaluation of the alert for a specific customer using the ‘Customer alerts reset’ endpoint. See Alerts docs here and API docs here.

Set free trials when adding a customer to a plan through the API

‘Add a plan to a customer’ endpoint now supports setting free trials. Programmatically set and edit free trials for customers through the API. See docs here.

Prevent writing duplicate credit grants

‘Create credit grant’ endpoint now has a ‘uniqueness_key’ on the request body to ensure idempotency and that there is no creation of duplicate credit grants for a customer. See docs here.

Create credit grant and add custom fields in a unified API

Add custom fields to credit grants using the ‘Create credit grant’ endpoint. These custom fields can be used to map to downstream integrations like Stripe. See docs here.

Set an idempotent billing configuration for AWS Marketplace

The ‘Set billing config’ endpoint for the AWS Marketplace integration is now more ergonomic by treating identical configurations set on the same Metronome customer as idempotent. This ensures that a second identical request isn’t treated as a duplicate configuration error.

Audit log enhancements

Added ‘Action description’ string to each mutation endpoint to show what changes have been made.
Filter ‘AuditLogs’ by ‘resource_type’, ‘resource_id’, and ‘ending_before’ to more easily track changes. See docs here.

Integration updates

Interact with the Metronome API using our public Workato connector

Customers using Workato can now interact with the Metronome API without writing custom HTTP calls. This also makes it easier for non-technical users to pull data from an API response through the Workato UI. See docs here.

Map credit grant custom fields to Stripe invoice line item metadata

In the Edit Stripe mappings UI, map credit grant metadata to the Stripe invoice line item metadata. One example use case is for revenue recognition–using Metronome custom fields to pass through NetSuite metadata into the Stripe credit purchase invoice.

UI updates

Data Export UI

Data Export is now under General Settings in its own tab, not nested under the Integrations tab.
Data Export layout has been updated to clearly show connected destinations and make it easier to update the destination and see the list of models being transferred out directly in the Metronome UI.

See the improved Data Export UI under General Settings.

Audit logs UI

Audit logs are now available in the Metronome UI. Easily view actions taken by users and export audit log data.

Track changes and export audit logs in the UI

RBAC error page

When a user is mistakenly assigned multiple RBAC roles, an error page will show the roles misconfigured to the same user, so you can quickly resolve errors.

GET STARTED

IMPLEMENT METRONOME

EVENTS

PRICING & PACKAGING

CUSTOMERS & BILLING

INVOICING

REPORTING & INSIGHTS

PLATFORM CONFIGURATION

​Billing configuration API endpoints now return response bodies

​Launch week recap: Monetization Infrastructure for AI

​Pricing models built for change

​Invoicing that unifies every revenue motion

​Billing as part of the product experience

​What this enables

​Invoicing with Google Cloud Marketplace

​September fixes and improvements

​UI

​API

​Make advanced contract overrides in the Metronome app

​Custom Reports

​Customer Lifecycle Notifications

​New documentation experience

​What’s new

​Ask AI

​API playground

​Improved search and information architecture

​Expanded guides

​Updated API reference descriptions

​August fixes and improvements

​UI

​API

​Invoice breakdowns in Data Export

​July fixes and improvements

​UI

​API

​Integrations

​Use group keys to set budgets across users, teams, and projects

​Seat-based credit pools

​Embeddable dashboard for credit and commit balances

​Threshold billing and auto-recharge

​What’s new

​Set up multi-entity billing

​Scope credits and commits to specific pricing or presentation group values

​Edit recurring commits and credits

​Support for seat-based subscription billing

​April fixes and improvements

​UI

​API

​Integrations

​Remove overrides and archive commits and scheduled charges

​Support for NZD and SGD currencies

​Ruby SDK

​Updated UI for creating and editing contracts, customer-level commits, and customer-level credits

​Edit rates in the Rate Card UI

​Usage threshold alerts supported on Contracts

​Contract editing

​Support for weekly frequencies for billing, recurring commits, and credits

​In Tempo: Spring 2025 changelog

​What’s new

​Alerts

​Resolved notifications on contract balance alerts

​Custom field filters on spend threshold alerts

​API investments

​Invoice breakdowns

​List balance calculation per commit or credit

​Uniqueness key on CreateCustomerCommit and CreateCustomerCredit APIs

​Product custom fields in invoice and rate card APIs

​Prevent updating contract end date to before end_timestamp of existing finalized invoices

​Business model support

​Recurring commits & credits

​Commit rates and commit-specific overrides

​Composite charges with >100% rate

​UI improvements

​Lifetime billings on the Customers list page

​UI badges for customer commits and credits status

​Security

​Metronome Trust Center

​IP Address and User Agent in Audit Logs

​Integrations

​Control service period reporting in Stripe

Billing configuration API endpoints now return response bodies

Launch week recap: Monetization Infrastructure for AI

Pricing models built for change

Invoicing that unifies every revenue motion

Billing as part of the product experience

What this enables

Invoicing with Google Cloud Marketplace

September fixes and improvements

UI

API

Make advanced contract overrides in the Metronome app

Custom Reports

Customer Lifecycle Notifications

New documentation experience

What’s new

Ask AI

API playground

Improved search and information architecture

Expanded guides

Updated API reference descriptions

August fixes and improvements

UI

API

Invoice breakdowns in Data Export

July fixes and improvements

UI

API

Integrations

Use group keys to set budgets across users, teams, and projects

Seat-based credit pools

Embeddable dashboard for credit and commit balances

Threshold billing and auto-recharge

What’s new

Set up multi-entity billing

Scope credits and commits to specific pricing or presentation group values

Edit recurring commits and credits

Support for seat-based subscription billing

April fixes and improvements

UI

API

Integrations

Remove overrides and archive commits and scheduled charges

Support for NZD and SGD currencies

Ruby SDK

Updated UI for creating and editing contracts, customer-level commits, and customer-level credits

Edit rates in the Rate Card UI

Usage threshold alerts supported on Contracts

Contract editing

Support for weekly frequencies for billing, recurring commits, and credits

In Tempo: Spring 2025 changelog

What’s new

Alerts

Resolved notifications on contract balance alerts

Custom field filters on spend threshold alerts

API investments

Invoice breakdowns

List balance calculation per commit or credit

Uniqueness key on CreateCustomerCommit and CreateCustomerCredit APIs

Product custom fields in invoice and rate card APIs

Prevent updating contract end date to before end_timestamp of existing finalized invoices

Business model support

Recurring commits & credits

Commit rates and commit-specific overrides

Composite charges with >100% rate

UI improvements

Lifetime billings on the Customers list page

UI badges for customer commits and credits status

Security

Metronome Trust Center

IP Address and User Agent in Audit Logs

Integrations

Control service period reporting in Stripe

Data Export

Balance calculation per commit or credit

Metronome 1.0 → 2.0 parity investments

AWS and Azure Marketplaces

International Currencies

Invoices and usage embeddable dashboards

Get in touch

Metronome 2.0