Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Metronome (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Metronome (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Metronome(link takes you to an external page) 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

getting-started page anchor
  1. From the Segment web app, click Catalog, then click Destinations
  2. Search for Metronome (Actions) within the Destinations Catalog and select Metronome (Actions)
  3. Click Configure Metronome (Actions).
  4. Select the source you'd like to connect to and give the destination a name.
  5. Enter your Metronome API Token into the Segment Connection Settings UI (save changes).

Property nameTypeRequiredDescription
API Tokenpassword
required

Your Metronome API Token


Metronome (Actions) has the following presets

Preset NameTriggerDefault Action
Send track events to MetronomeEvent type = "track"Send Event

Build your own Mappings. Combine supported triggers with the following Metronome-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Send Event

send-event page anchor

Send an event to Metronome

Send Event is a Cloud action.

Property nameTypeRequiredDescription
transaction_idSTRING
required

The Metronome transaction ID uniquely identifies an event to ensure Metronome only processes each event once.


customer_idSTRING
required

The Metronome customer ID or ingest alias this event should be associated with.


timestampDATETIME
required

The timestamp at which this event occurred.


event_typeSTRING
required

The Metronome event_type.


propertiesOBJECT
required

The Metronome properties object.


Mapping events to Metronome

mapping-events-to-metronome page anchor

Map Segment events to the Metronome event format(link takes you to an external page). Metronome requires the five following fields:

FieldTypeDescription
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(link takes you to an external page).
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)

benefits-of-metronome-actions page anchor

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.