merge conflicts

Author: markzegarelli

.github/styles/Vocab/Docs/accept.txt

@@ -54,6 +54,7 @@ Hubspot
 incrementality
 ios
 iOS
+Iterable
 Javadoc
 Javadocs
 Javascript
@@ -77,6 +78,7 @@ onboarding
 Optimizely
 performant
 Preact
+Selligent
 Shopify
 Skalin
 Smartly

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

@@ -2,8 +2,7 @@
 title: Metronome (Actions) Destination
 hide-boilerplate: true
 id: 61a8032ea5f157ee37a720be
-redirect_from:
-  - '/connections/destinations/catalog/vendor-metronome'
+hidden: true
 ---
 {% include content/plan-grid.md name="actions" %}
 
@@ -14,10 +13,10 @@ Metronome also enables product-led growth with a consistent source of truth for
 ## Getting Started
 
 1. From the Segment web app, click **Catalog**, then click **Destinations**
-2. Search for **Metronome (Actions)** within the Destinations Catalog and select **Metronome (Actions)**
+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).
+4. Select the source you’d like to connect to and give the destination a name (for example, `Metronome Instance #1`).
+5. Enter your Metronome API Token on the **Settings** pane in the **API Token** box, and save changes.
 
 {% include components/actions-fields.html %}
 
@@ -41,4 +40,4 @@ Metronome (Actions) provides the following benefits:
 
 - **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.
+- **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

@@ -1,6 +1,45 @@
 ---
-title: 'Metronome (Actions) Destination'
-hidden: true
+title: Metronome (Actions) Destination
+hide-boilerplate: true
 id: 61a8032ea5f157ee37a720be
-published: false
+redirect_from:
+  - '/connections/destinations/catalog/vendor-metronome'
+  - '/connections/destinations/catalog/actions-metronome'
 ---
+{% include content/plan-grid.md name="actions" %}
+
+[Metronome](https://www.metronome.com){:target="_blank"} 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
+
+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).
+
+{% include components/actions-fields.html %}
+
+
+## Mapping events to Metronome
+
+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: 
+
+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](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"}.
+`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.

src/connections/destinations/catalog/orb/index.md

@@ -1,7 +1,41 @@
 ---
-title: 'Orb Destination'
-hidden: true
+title: Orb Destination
 id: 625ed45387dd6603f5380424
-published: false
 beta: true
 ---
+[Orb](https://www.withorb.com/) provides scalable, reliable, and flexible billing infrastructure for usage based revenue models at companies of all sizes.
+
+Orb maintains this destination. For any issues with the destination, [contact the Orb support team](mailto:[email protected]).
+
+## Getting started
+
+{% include content/connection-modes.md %}
+
+1. Navigate to **Connections** and click **Add Destination** in the Segment app. 
+2. Search for *Orb* in the Destinations Catalog, and select the **Orb** destination.
+3. Choose which Source should send data to the Orb destination.
+4. Go to the [Orb dashboard](https://app.billwithorb.com) and create a new API key from the configuration page.  Segment recommends you to create a new API key for this integration rather than using an existing one.
+5. Enter the **API Key** in the Orb destination settings in Segment.
+6. Enter the connection settings for the external customer ID and properties mapping fields.
+
+## Supported methods
+
+Orb currently supports track calls, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Track
+
+Use [Track](/docs/connections/spec/track) calls to automatically send usage events based on your customer's interactions with your application. Any Segment track call will be ingested through [Orb's ingestion pipeline](https://docs.withorb.com/docs/orb-docs/event-ingestion) and usage information will be used to calculate billable totals. For example:
+```js
+analytics.track({
+  event: "payment_confirmed",
+  userId: "external_customer_id",
+  properties: {
+    amount: 100.00,
+    currency: "USD",
+    confirmation_time: "2022-05-11T21:33:13.1652304793Z"
+  }
+});
+```
+Similar to Segment, Orb supports a flexible event schema in the `properties` dictionary, which should be non-null and not contain nested objects. Within Orb, you can configure metrics by filtering and aggregating events. When you configure the Orb destination, you are required to specify a mapping of keys from the original Segment event to Orb’s usage event. You can also configure keys corresponding to Orb’s required fields such as `event_name` , `idempotency_key`, and `external_customer_id`. 
+
+Events ingested through the track spec are available on the Orb admin dashboard, specifically on the [Events page](https://app.billwithorb.com/events).