Merge pull request #444 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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

@@ -4,6 +4,7 @@ hide-boilerplate: true
 id: 61a8032ea5f157ee37a720be
 redirect_from:
   - '/connections/destinations/catalog/vendor-metronome'
+  - '/connections/destinations/catalog/metronome-actions'
 ---
 {% include content/plan-grid.md name="actions" %}
 

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 following fields: 
+
+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/sources/catalog/cloud-apps/drip/index.md

@@ -2,6 +2,8 @@
 title: Drip Source
 id: m6FUZHH7tQ
 ---
+{% include content/source-region-unsupported.md %}
+
 Drip is an automated email tool that lets you set up a drip campaign on your site in a few minutes. After a user signs up, it'll send them the next email in your series every few days. [Visit Website](http://mbsy.co/lqb7?utm_source=segmentio&utm_medium=docs&utm_campaign=partners)
 
 Take your company's email analysis to the next level by **adding Drip as a Source to Segment.** Segment automatically  collects email events like `Email Delivered` and `Email Opened`, forward them to your destinations, and load them into your data warehouse. 

src/personas/journeys/build-journey.md

@@ -54,10 +54,25 @@ Define the number of branches you want to create, then add a **Wait for conditio
 > info ""
 > Journeys doesn't enforce mutual exclusivity in branch conditions. For more information about ensuring branch exclusivity, see [Best Practices](#).
 
-**Connect to existing step** joins two separate branches. Use this step to target multiple groups with one step. 
+**Connect to existing step** joins two separate branches. Use this step to target multiple groups with one step.
 
 **Send to Destinations** delivers information about the Journey to the selected Destination. For more information, see [Send data to Destinations](/docs/personas/journeys/send-data)
 
+## Publishing a Journey
+
+To publish and activate a Journey, click **Publish Journey** from the Journey Overview. You can also click **Publish Journey** in the bottom-right corner of the Journey Builder.
+
+> info ""
+> Some Journey features can only be edited before publication. For more information, see the difference between Draft and Published Journeys below.
+
+## Journey re-entry
+
+The Journeys re-entry setting allows users to repeat Journeys they've already exited. Common use cases for Journeys re-entry include the following:
+
+- Retargeting users who abandon multiple carts
+- Recurring rewards and promotion offers
+- Notifying users when to renew a subscription
+
 ## Cloning a Journey
 
 To clone a Journey:
@@ -68,20 +83,31 @@ Segment then creates a draft of your Journey.
 
 You can also clone a Journey from a Journey's Overview by clicking the **…** icon.
 
-## Publishing a Journey
-
-To publish and activate a Journey, click **Publish Journey** from the Journey Overview. You can also click **Publish Journey** in the bottom-right corner of the Journey Builder.
+## Randomized splits
 
 > info ""
-> Some Journey features can only be edited before publication. For more information, see the difference between Draft and Published Journeys below.
+> The randomized splits step is in beta and available to users with a Personas Advanced plan.
 
-## Journey re-entry
+A randomized split lets you experiment with and test the performance of a Journey's branches. When you create a randomized split, you add up to five Journey branches, each with a different step. Journeys then sends eligible users down one of the branches at random. Each branch receives a portion of the eligible users based on percentages that you assign to the branches.
 
-The Journeys re-entry setting allows users to repeat Journeys they've already exited. Common use cases for Journeys re-entry include the following:
+To test your messaging channels, for example, you might create a randomized split with three different branches, assigning 40% of users to an email campaign, 40% to an SMS campaign, and 20% to a control group. Once users flow through the split, you can determine the success of the email and SMS campaigns compared to each other and the control group.
 
-- Retargeting users who abandon multiple carts
-- Recurring rewards and promotion offers
-- Notifying users when to renew a subscription
+### Add a randomized split
+
+Follow these steps to add a randomized split to a Journey:
+
+1. Create a new Journey, and [add an entry condition](#adding-the-entry-condition).
+2. Select the **+** icon to add a step, then select **Create a randomized split**.
+3. Name the randomized split step, then add up to five branches.
+4. Set the distribution percentage for each branch, then select **Save**.
+5. For each branch in the split, select the child **+** icon and add a step.
+3. Save and publish your Journey.
+
+Users who meet the Journey's entry condition will then enter the Journey and flow through the randomized split.
+
+### Act on the split's results
+
+Once users complete your Journey's randomized split step, you'll have insight into how each split performed. You can take action on the results by cloning the Journey and sending a new set of users through the highest performing branch.
 
 ### Exit and re-entry times