Ready to deploy (#3022)

Author: markzegarelli

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

@@ -2,18 +2,25 @@
 title: Metronome (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
+hidden: true
 id: 61a8032ea5f157ee37a720be
 redirect_from:
   - '/connections/destinations/catalog/vendor-metronome'
-versions:
-  - name: Metronome
-    link: /docs/connections/destinations/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](https://www.metronome.com){:target="_blank"} 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.
+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.
+
+## 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.
 
 ## Getting Started
 
@@ -23,22 +30,20 @@ versions:
 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).
 
-## Mapping
+{% include components/actions-fields.html %}
 
-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: 
+## Mapping events to Metronome
 
-* transaction_id (string) - unique identifier for each event
-* customer_id  (string) - which customer in Metronome the event applies to
-* timestamp (string) - when the event happened in [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"}
-* event_type (string) - the kind of event, e.g. page_view or cpu_used
-* properties (object) - key/value pairs with details of the event
+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: 
 
 
-## Benefits of Metronome (Actions)
-Metronome (Actions) provides the following benefits:
+| Metronome field  | Type   | Description                                                                                                            |
+| ---------------- | ------ | ---------------------------------------------------------------------------------------------------------------------- |
+| `transaction_id` | String | A unique identifier for each event.                                                                                    |
+| `customer_id`    | String | The customer in Metronome to which the event applies                                                                   |
+| `timestamp`      | String | The time at which the event occurred, in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt){:target="_blank"} format. |
+| `event_type`     | String | The type of event passed. For example, `page_view` or `cpu_used`.                                                      |
+| `properties`     | Object | Key/value pairs with details of the event                                                                              |
 
-- **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.