Centralize customer data and enable integrations with custom fields

Apr 4, 2023
 • 
0 MIN READ
Gold share tray icon
Claudia Finn
Product
Get updates into your inbox
Sample Metronome billing dashboard
Share

As the usage and billing source-of-truth for our customers, we recognize the importance of streamlining our customers' external workflows which rely on this data. We’re excited to announce that with the release of custom fields, our customers can now store additional metadata on Metronome entities to have a comprehensive view of customer data and connect data to different systems.

How do custom fields work?

Think of custom fields as metadata that can be added to Metronome entities such as customers, products, charges, and credit grants. Each custom field is represented as a key value pair. Keys are placed on entities, and values are set per instantiation of the entity. Values can be unique or non-unique.

For example, you can add a custom field key called ‘netsuite_item_id’ to Metronome charges. For each charge, you can add the corresponding unique value such as: 

Charge: all_purpose_compute
netsuite_item_id: 0000000001

Charge: aws_compute
netsuite_item_id: 0000000002
View and manage custom field keys in the UI under General settings.

How can I leverage custom fields? 

Maintain a customer source of truth

With custom fields, customers can quickly query the Metronome API and access centralized customer information. One example is pulling a customer in the Metronome API and seeing ‘salesforce_id’, ‘referring_partner’, ‘netsuitecustomer_id’ in one place.

Connect Metronome data to other systems

Custom fields can also be used to map fields from Metronome into customer-managed workflows and external systems. Developers interested in building their own workflows can now easily create custom scripts that use our API, without needing to maintain their own mapping of Metronome IDs to external IDs in another system.

Custom fields also unlock our ability to build integrations to connect Metronome with our customers’ tech stack. We’ll be announcing a few integrations soon—if you’re interested in testing out our new integrations, please reach out to your Metronome representative.

Get started

Custom fields are now available to all customers via the Metronome API and Metronome UI. Developers can create and manage custom fields through the API and business users can create new custom field keys and set custom field values in the Metronome UI. See our documentation for more details.

To create new custom field keys in the UI, navigate to General settings > Custom fields (see earlier product image).

To view or set the value of a specific custom field, use the more menu (three dots) on the specific entity that you want to set (see below).

View and manage values for custom fields on products, customers, charges, and credit grants in the UI.

You can contact us here or reach out to your Growth representative if you’re interested in learning more.

Company Industry Outcome-Based Pricing Model Key Metrics for Pricing Notable Features
Salesforce (Agentforce) CRM / AI Customer Service

$2 per conversation handled by Agentforce (AI agent)

A conversation is defined as when a customer sends at least one message or selects at least one menu option or choice other than the End Chat button within a 24-hour period.

Number of support conversations handled by the AI agent

First major CRM to adopt a "semi"outcome-based pricing for AI; aligns cost with actual support volumes (clear ROI)

Addresses inefficiencies of idle licenses by charging only when value (a handled conversation) is delivered

Intercom (Fin AI) Customer Support Software

$0.99 per successful resolution by "Fin" AI chatbot - clients pay only when the bot successfully resolves a customer query

Fees accrue based on AI-solved issues

Count of support conversations resolved by the AI agent

Early adopter of AI outcome-based pricing in 2023

Lowers adoption risk by charging for resolved queries instead of a flat rate; combines usage- and value-based pricing to tie cost directly to support effectiveness.

Zendesk (AI Answer Bot) Customer Support

Per successful AI chatbot-handled resolution

No charge if the bot fails and a human must step in

Number of customer issues or tickets auto-resolved by the bot

Aimed at cost-conscious customers wary of paying for unproven AI

Aligns price with realized automation benefit; part of a broader industry shift from per-agent pricing to value-delivered pricing in support

Chargeflow Fintech (Chargeback Management)

Charges a fraction of recovered funds on chargebacks

Example: ~25% fee per successful chargeback recovery

No fees for chargebacks lost

Alert service charges $39 per prevented chargeback

Value/count of chargebacks recovered (disputes won) and chargebacks prevented (for prevention alerts)

4× ROI guarantee on recoveries

No contracts or monthly fees

Revenue comes only from successful outcomes; pricing directly aligns with merchant's regained revenue, meaning Chargeflow only profits when the client does (win-win model)

Riskified*

(source: https://www.chargeflow.io/blog/riskified-vs-forter)

E-commerce Fraud Prevention

remain fraud-free

PAYGO, 0.4% per transaction

Only charges for transactions it approves that

Number or value of approved transactions without fraud (i.e. successfully processed legitimate sales).

Provider shares financial risk of fraud with clients; pricing tied to outcome of increased safe sales

Incentivizes vendor to maintain high accuracy (they only profit when fraud is stopped)

Foster continuous improvement in their fraud-detection algorithms

Subscribe

Keep up with the latest in
pricing and packaging