Metronome Destination
UpdatedAbout this integration
Metronome provides an easy-to-configure billing infrastructure that scales to support businesses at any stage. It enables product-led growth by serving as a reliable source for use and billing data. This integration sends events to Metronome, helping you track audience activities in the platform, so you can experiment with pricing and packaging and see how your changes affect your users.
Getting started
Go to Data & Integrations > Integrations and select the Metronome entry in the Directory tab.
(Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
Configure your integration.
- Api Token: Your Metronome API Token
Click Enable Destination.
Actions
When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.
You may need to add actions for this integration
While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our actions page for help setting up actions.
| Action | Default Trigger | Description |
|---|---|---|
| Send Event | Send an event to Metronome |
Mapping events to Metronome
Metronome uses a specific event format that requires the following fields. When you map the Send Event action, you’ll need to make sure that you also map the following five fields.
| Field | Type | Description |
|---|---|---|
transaction_id | string | The unique identifier for each event, analgous to our messageId. |
customer_id | string | Represents which customer in Metronome the event applies to, analagous to our userId or anonymousId |
timestamp | string | When the event happened in RFC 3339 format. |
event_type | string | Typically our event name property, like, page_view or cpu_used. |
properties | (object) | The key/value pairs with details of the event—typically $.properties from the source event. |
