Metronome (Actions) Destination
Metronome helps software companies launch, iterate, and scale their business models with billing infrastructure that works at any size and stage. With Metronome, your team can set up a world-class billing infrastructure with minimal time and investment.
Metronome also enables product-led growth with a consistent source of truth for use and billing. Freely experiment with pricing and packaging and put iteration directly in the hands of your Product team.
Getting Started
- From the Segment web app, click Catalog, then click Destinations
- Search for Metronome (Actions) within the Destinations Catalog and select Metronome (Actions)
- Click Configure Metronome (Actions).
- Select the source you’d like to connect to and give the destination a name.
- Enter your Metronome API Token into the Segment Connection Settings UI (save changes).
Destination Settings
| Setting | Description |
|---|---|
| API Token | Required. Your Metronome API Token |
Available Presets
Metronome (Actions) has the following presets:
| Preset Name | Trigger | Default Action |
|---|---|---|
| Send track events to Metronome | Event type = "track" |
Send Event |
Available Actions
Build your own Mappings. Combine supported triggers with the following Metronome-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Send Event
Send an event to Metronome
Send Event is a Cloud action.
| Field | Description |
|---|---|
| transaction_id* | Type: STRINGThe Metronome transaction ID uniquely identifies an event to ensure Metronome only processes each event once. |
| customer_id* | Type: STRINGThe Metronome customer ID or ingest alias this event should be associated with. |
| timestamp* | Type: DATETIMEThe timestamp at which this event occurred. |
| event_type* | Type: STRINGThe Metronome |
| properties* | Type: OBJECTThe Metronome properties object. |
Mapping events to Metronome
Map Segment events to the Metronome event format. Metronome requires the five following fields:
| Field | Type | Description |
|---|---|---|
transaction_id |
(string) | The unique identifier for each event. |
customer_id |
(string) | Represents which customer in Metronome the event applies to. |
timestamp |
(string) | This is when the event happened in RFC 3339. |
event_type |
(string) | This is the kind of event. For example, page_view or cpu_used. |
properties |
(object) | The key/value pairs with details of the event. |
Benefits of Metronome (Actions)
Metronome (Actions) provides the following benefits:
-
Streamlined Configuration. Configure connection details on a per-event basis, rather than for the destination as a whole.
-
Easy access to data. The event variables picker shows you all the available data from the event you use to test the Trigger. Variables are clearly labeled to ensure they stand out from other text and markup.
-
Clear mapping of data Actions-based destinations enable you to define the mapping between the data Segment receives from your source and the data Segment sends to Metronome.
This page was last modified: 29 Jun 2022
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!