Merge pull request #410 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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

@@ -0,0 +1,44 @@
+---
+title: Metronome (Actions) Destination
+hide-boilerplate: true
+hide-dossier: false
+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.
+
+## Getting Started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations** 
+2. Search for **Metronome** within the Destinations Catalog and select **Metronome (Actions)**
+3. Click **Configure Actions Metronome**.
+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
+
+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: 
+
+* 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
+
+
+## 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/actions-salesforce/index.md

@@ -7,9 +7,6 @@ id: 61957755c4d820be968457de
 ---
 Segment’s Salesforce (Actions) destination allows you to create, update or upsert records for any object type. Segment sends data to the [Salesforce REST API](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm){:target="_blank"}. 
 
-> info ""
-> The Salesforce (Actions) destination is in beta and is in active development. Some functionality may change before it becomes generally available.
-
 > success "Good to know"
 > This page is about the [Actions-framework](/docs/connections/destinations/actions/) Salesforce destination. There's also a page about the [non-Actions Salesforce destination](/docs/connections/destinations/catalog/salesforce/). Both of these destinations receive data _from_ Segment.
 

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

@@ -2,16 +2,14 @@
 title: Salesforce Destination
 strat: salesforce
 id: 54521fda25e721e32a72eeef
+maintenance: true
 ---
 
-Segment's Salesforce destination allows you to identify leads without using SOAP APIs.
+Segment's Salesforce destination allows you to create and store leads and records for other objects in Salesforce Sales Cloud.
 
 > info ""
 > Segment is aware of Salesforce's plans to enforce multi-factor authentication in 2022, and advises migrating to our new [Salesforce (Actions) destination](/docs/connections/destinations/catalog/actions-salesforce/) which supports OAuth 2.0.
 
-> success "Good to know"
-> This page is about the classic Salesforce Segment destination. There's also a page about the new [Salesforce (Actions) destination](/docs/connections/destinations/catalog/actions-salesforce/). Both of these destinations receive data _from_ Segment. Use the new Salesforce (Actions) destination for additional functionality and flexibility.
-
 ### API Access
 
 Segment uses the Salesforce SOAP API to connect. This API requires the following credentials of a registered Salesforce user:
@@ -27,7 +25,7 @@ Also make sure that IP Security is disabled in this Salesforce user account. Thi
 
 ## Identify
 
-This destination supports the most important pain point for Salesforce users: getting your prospective customers into Salesforce as Leads from your website or mobile app. Creating/updating Leads is the default behavior of `identify` events. If you would like to customize this you can do so using [Actions](#custom-actions)
+This destination supports the most important pain point for Salesforce users: getting your prospective customers into Salesforce as Leads from your website or mobile app. Creating/updating Leads is the default behavior of `identify` events. If you would like to customize this you can do so using [Actions](#custom-actions).
 
 ### Identifying a Lead