Send usage events from Segment

Map your Segment events to the Metronome usage event format. The five fields listed are the required fields for Metronome. To start, click the Mappings tab at the top of the Settings pane. You have a set of mappings by default. To add to or change them, choose Edit Mapping from the ellipsis dropdown.

All mappings are required

You must specify a mapping even if the property name doesn’t differ between the Segment event and the Metronome payload.

analytics.track('billing_event', {
  cid: '533c3db43f22',
  data: {
    action: 'runJob',
    jobId: 'fd82-aa0f-45a7-a756',
    username: 'jsmith'
  },
  t: 'user_action',
  ts: new Date('2020-04-02T00:10:25.000Z')
});

Transaction ID required

Metronome usage events require the transaction_id field to ensure all events are processed exactly once. The default mapping uses the Segment messageId field as the Metronome transaction_id. This is probably ideal for most users, but if you want to control the Metronome transaction_id manually, you can provide a mapping to any field in the Segment event.

The integration supports Destination Actions, allowing users to create subscriptions. This means that the Metronome (Actions) destination sends data to Metronome based on a set of conditions known as triggers. Create additional triggers and mappings by clicking on the New Mapping button on the Mapping pane. You can set a trigger for any number of conditions. For example, create a condition to trigger events to Metronome only when the User ID field is not an email address from your company (does not contain @company.com).