Skip to content

Commit b532e5c

Browse files
bot-docsteambot-docsteam
authored
Merge pull request #437 from segmentio/repo-sync
repo sync
2 parents 19d6557 + d985b87 commit b532e5c

File tree

7 files changed

+184
-29
lines changed

7 files changed

+184
-29
lines changed

‎src/_data/catalog/destination_categories.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# destination categories last updated 2022-06-22
2+
# destination categories last updated 2022-06-23
33
items:
44
- display_name: A/B Testing
55
slug: a-b-testing

‎src/_data/catalog/destinations.yml

Lines changed: 149 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# destination data last updated 2022-06-22
2+
# destination data last updated 2022-06-23
33
items:
44
- id: 60b5d0a01f3726b85dc05aab
55
display_name: 2mee
@@ -10127,7 +10127,7 @@ items:
1012710127
display_name: Criteo Audiences
1012810128
name: Criteo Audiences
1012910129
slug: criteo-audiences
10130-
hidden: false
10130+
hidden: true
1013110131
endpoints:
1013210132
- us
1013310133
regions:
@@ -28013,6 +28013,153 @@ items:
2801328013
label: Events
2801428014
actions: []
2801528015
presets: []
28016+
- id: 61a8032ea5f157ee37a720be
28017+
display_name: Metronome (Actions)
28018+
name: Metronome (Actions)
28019+
slug: metronome-actions
28020+
hidden: true
28021+
endpoints:
28022+
- us
28023+
regions:
28024+
- us
28025+
url: connections/destinations/catalog/metronome-actions
28026+
previous_names:
28027+
- Metronome (Actions)
28028+
website: https://metronome.com/
28029+
status: PUBLIC
28030+
categories: []
28031+
logo:
28032+
url: https://cdn.filepicker.io/api/file/PrwprKrRyCOXCl7ONjWR
28033+
mark:
28034+
url: https://cdn.filepicker.io/api/file/PSpWVXUqTpSx6CFKiKvB
28035+
methods:
28036+
track: true
28037+
identify: true
28038+
group: true
28039+
alias: true
28040+
page: true
28041+
platforms:
28042+
browser: true
28043+
mobile: false
28044+
server: true
28045+
components: []
28046+
browserUnbundlingSupported: false
28047+
browserUnbundlingPublic: false
28048+
replay: false
28049+
connection_modes:
28050+
device:
28051+
web: false
28052+
mobile: false
28053+
server: false
28054+
cloud:
28055+
web: false
28056+
mobile: false
28057+
server: false
28058+
settings:
28059+
- name: apiToken
28060+
type: string
28061+
defaultValue: ''
28062+
description: Your Metronome API Token
28063+
required: true
28064+
label: API Token
28065+
actions:
28066+
- id: juSSUDTbstNtNs7Rjt1jZD
28067+
name: Send Event
28068+
slug: sendEvent
28069+
description: Send an event to Metronome
28070+
platform: CLOUD
28071+
hidden: false
28072+
defaultTrigger: null
28073+
fields:
28074+
- id: QWCFNM4rUsP2B4o1gEonq
28075+
sortOrder: 0
28076+
fieldKey: transaction_id
28077+
label: transaction_id
28078+
type: STRING
28079+
description: >-
28080+
The Metronome transaction ID uniquely identifies an event to ensure
28081+
Metronome only processes each event once.
28082+
placeholder: ''
28083+
defaultValue:
28084+
'@path': $.messageId
28085+
required: true
28086+
multiple: false
28087+
choices: null
28088+
dynamic: false
28089+
allowNull: false
28090+
- id: ktu4KKRoDT9uYwdDxQwiWY
28091+
sortOrder: 1
28092+
fieldKey: customer_id
28093+
label: customer_id
28094+
type: STRING
28095+
description: >-
28096+
The Metronome customer ID or ingest alias this event should be
28097+
associated with.
28098+
placeholder: ''
28099+
defaultValue:
28100+
'@path': $.context.groupId
28101+
required: true
28102+
multiple: false
28103+
choices: null
28104+
dynamic: false
28105+
allowNull: false
28106+
- id: gWAU3F6LJYrmd2QStaHRiq
28107+
sortOrder: 2
28108+
fieldKey: timestamp
28109+
label: timestamp
28110+
type: DATETIME
28111+
description: The timestamp at which this event occurred.
28112+
placeholder: ''
28113+
defaultValue:
28114+
'@path': $.timestamp
28115+
required: true
28116+
multiple: false
28117+
choices: null
28118+
dynamic: false
28119+
allowNull: false
28120+
- id: qwLqDvB7hkuACMAsaSzPBe
28121+
sortOrder: 3
28122+
fieldKey: event_type
28123+
label: event_type
28124+
type: STRING
28125+
description: The Metronome `event_type`.
28126+
placeholder: ''
28127+
defaultValue:
28128+
'@path': $.event
28129+
required: true
28130+
multiple: false
28131+
choices: null
28132+
dynamic: false
28133+
allowNull: false
28134+
- id: 25C3GH3KPmWqvqX2VtiaRD
28135+
sortOrder: 4
28136+
fieldKey: properties
28137+
label: properties
28138+
type: OBJECT
28139+
description: The Metronome properties object.
28140+
placeholder: ''
28141+
defaultValue:
28142+
'@path': $.properties
28143+
required: true
28144+
multiple: false
28145+
choices: null
28146+
dynamic: false
28147+
allowNull: false
28148+
presets:
28149+
- actionId: juSSUDTbstNtNs7Rjt1jZD
28150+
name: Send track events to Metronome
28151+
fields:
28152+
transaction_id:
28153+
'@path': $.messageId
28154+
customer_id:
28155+
'@path': $.context.groupId
28156+
timestamp:
28157+
'@path': $.timestamp
28158+
event_type:
28159+
'@path': $.event
28160+
properties:
28161+
'@path': $.properties
28162+
trigger: type = "track"
2801628163
- id: 54521fd925e721e32a72eed5
2801728164
display_name: Millennial Media
2801828165
name: Millennial Media

‎src/_data/catalog/regional-supported.yml

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
2-
# Last updated 2022-06-22
2+
# Last updated 2022-06-23
33
warehouses:
44
- id: WcjBCzUGff
55
display_name: Azure SQL Data Warehouse
@@ -2598,6 +2598,14 @@ destinations:
25982598
- eu
25992599
endpoints:
26002600
- us
2601+
- id: 61a8032ea5f157ee37a720be
2602+
display_name: Metronome (Actions)
2603+
slug: metronome-actions
2604+
url: connections/destinations/catalog/metronome-actions
2605+
regions:
2606+
- us
2607+
endpoints:
2608+
- us
26012609
- id: 54521fd925e721e32a72eed5
26022610
display_name: Millennial Media
26032611
slug: millennial-media

‎src/_data/catalog/source_categories.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# source cateogries last updated 2022-06-22
2+
# source cateogries last updated 2022-06-23
33
items:
44
- display_name: A/B Testing
55
slug: a-b-testing

‎src/_data/catalog/sources.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# sources last updated 2022-06-22
2+
# sources last updated 2022-06-23
33
items:
44
- id: 8HWbgPTt3k
55
display_name: .NET

‎src/connections/destinations/catalog/actions-metronome/index.md

Lines changed: 17 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,6 @@
11
---
22
title: Metronome (Actions) Destination
33
hide-boilerplate: true
4-
hide-dossier: true
5-
hidden: true
6-
private: true
74
id: 61a8032ea5f157ee37a720be
85
redirect_from:
96
- '/connections/destinations/catalog/vendor-metronome'
@@ -14,37 +11,34 @@ redirect_from:
1411

1512
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.
1613

17-
## Benefits of Metronome (Actions)
18-
Metronome (Actions) provides the following benefits:
19-
20-
- **Streamlined Configuration**. Configure connection details on a per-event basis, rather than for the destination as a whole.
21-
22-
- **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.
23-
24-
- **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.
25-
2614
## Getting Started
2715

28-
1. From the Segment web app, click **Catalog**, then click **Destinations**
29-
2. Search for **Metronome** within the Destinations Catalog and select **Metronome (Actions)**
30-
3. Click **Configure Actions Metronome**.
16+
1. From the Segment web app, click **Catalog**, then click **Destinations**
17+
2. Search for **Metronome (Actions)** within the Destinations Catalog and select **Metronome (Actions)**
18+
3. Click **Configure Metronome (Actions)**.
3119
4. Select the source you’d like to connect to and give the destination a name
3220
5. Enter your Metronome API Token into the Segment Connection Settings UI (save changes).
3321

3422
{% include components/actions-fields.html %}
3523

24+
3625
## Mapping events to Metronome
3726

38-
Map Segment events the [Metronome event format](https://docs.metronome.com/getting-usage-data-into-metronome/overview/){:target="_blank"}. Metronome requires the five fields listed below:
27+
Map Segment events to the [Metronome event format](https://docs.metronome.com/getting-usage-data-into-metronome/overview/){:target="_blank"}. Metronome requires the five fields listed below:
3928

29+
Field | Type | Description
30+
----- | ---- | ------------
31+
`transaction_id` | (string) | The unique identifier for each event.
32+
`customer_id` | (string) | Represents which customer in Metronome the event applies to.
33+
`timestamp` | (string) | This is when the event happened in [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"}.
34+
`event_type` | (string) | This is the kind of event. For example, `page_view` or `cpu_used`.
35+
`properties` | (object) | The key/value pairs with details of the event.
4036

41-
| Metronome field | Type | Description |
42-
| ---------------- | ------ | ---------------------------------------------------------------------------------------------------------------------- |
43-
| `transaction_id` | String | A unique identifier for each event. |
44-
| `customer_id` | String | The customer in Metronome to which the event applies |
45-
| `timestamp` | String | The time at which the event occurred, in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"} format. |
46-
| `event_type` | String | The type of event passed. For example, `page_view` or `cpu_used`. |
47-
| `properties` | Object | Key/value pairs with details of the event |
37+
## Benefits of Metronome (Actions)
38+
Metronome (Actions) provides the following benefits:
4839

40+
- **Streamlined Configuration**. Configure connection details on a per-event basis, rather than for the destination as a whole.
4941

42+
- **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.
5043

44+
- **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.

‎src/connections/destinations/catalog/metronome-actions/index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
title: 'Metronome (Actions) Destination'
3+
hidden: true
4+
id: 61a8032ea5f157ee37a720be
5+
published: false
6+
---

0 commit comments

Comments
 (0)