Merge pull request #630 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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

@@ -1,7 +1,6 @@
 ---
 title: LaunchDarkly (Actions) Destination
 hide-boilerplate: true
-hide-dossier: true
 id: 624dddd054ced46facfdb9c0
 ---
 
@@ -43,11 +42,13 @@ To get started with LaunchDarkly (Actions):
 
 {% include components/actions-fields.html %}
 
+> info "A note about Identify calls"
+> LaunchDarkly doesn't store user attributes for use with flag evaluations. As a result, Segment doesn't support mapping Identify calls to LaunchDarkly actions.
+
 ## Creating LaunchDarkly metrics
 
 In order to take full-advantage of the LaunchDarkly (Actions) Destination, you need to create metrics in LaunchDarkly that correspond to Segment track events. Read [Creating metrics](https://docs.launchdarkly.com/home/experimentation/metrics){:target="_blank"} to learn how to create metrics in LaunchDarkly.
 
-<!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
 
 ## Migration from the classic LaunchDarkly destination
 

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

@@ -31,21 +31,33 @@ Page calls will be sent to Mutiny as an `impression`.
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
-```
+```js
 analytics.identify('userId123', {
   email: 'john.doe@example.com'
 });
 ```
 
-Identify calls will be sent to Mutiny as an `identify` event. We use this in order to associate traits with an individual, which can be targeted for personalization in outbound email campaigns.
+Identify calls will be sent to Mutiny as an `identify` event. Segment uses this in order to associate traits with an individual, which can be targeted for personalization in outbound email campaigns.
 
 
 ## Track
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
-```
+```js
 analytics.track('Clicked Login Button')
 ```
 
-Track calls will be sent to Mutiny as a `track` event. Within the Mutiny dashboard, you can select which events signal a conversion for your website visitors. When a `track` event is processed for these events, a visitor will be marked as converted and that information will be displayed in the experiment results for a given experience.
+Track calls are sent to Mutiny as a `track` event. Within the Mutiny dashboard, you can select which events signal a conversion for your website visitors. When a `track` event is processed for these events, a visitor will be marked as converted and that information will be displayed in the experiment results for a given experience.
+
+Mutiny's integration with Segment enables customers to use Segment events to track conversions in Mutiny. Mutiny also sends events *to* Segment to help track attribution for Mutiny experiences. Mutiny sends the `Mutiny Experience Viewed` with the `audienceSegment`, `experience`, and `personalized` properties. For example:
+
+```js
+analytics.track('Mutiny Experience Viewed', {
+  experience: 'Corporate Website Experiment',
+  audienceSegment: 'Small company',
+  personalized: true,
+});
+```
+
+The `personalized` property is `true` for personalized experiences and `false` for a control views. For more information, contact [Mutiny Support](mailto:mutinylovesyou@mutinyhq.com).

src/connections/sources/catalog/libraries/server/python/index.md

@@ -23,7 +23,7 @@ If you're using a system for managing dependencies, you'll want to pin the libra
 Inside your app, you'll want to **set your `write_key`** before making any analytics calls:
 
 ```python
-import analytics
+import segment.analytics as analytics
 
 analytics.write_key = 'YOUR_WRITE_KEY'
 ```
@@ -344,7 +344,7 @@ assert d.tzinfo is not None and d.tzinfo.utcoffset(d) is not None
 ```python
 import dateutil.parser
 
-import analytics
+import segment.analytics as analytics
 analytics.write_key = 'YOUR_WRITE_KEY'
 
 log = [
@@ -475,7 +475,7 @@ To add analytics to your Django web server, you need to include the initializati
 
 ```python
 from django.apps import AppConfig
-import analytics
+import segment.analytics as analytics
 
 class MyAppConfig(AppConfig):
 
@@ -524,7 +524,7 @@ and turn on module logging in your initialization call in `urls.py`.
 
 ```python
 import logging
-import analytics
+import segment.analytics as analytics
 
 analytics.debug = True # turn on debug logging
 analytics.write_key = 'YOUR_WRITE_KEY'
@@ -567,7 +567,7 @@ Be sure to see the full [reference of supported keys](/docs/connections/spec/com
 Check that you have the most recent version.
 
 ```
-python -c "import analytics; print analytics.VERSION"
+python -c "import segment.analytics as analytics; print analytics.VERSION"
 ```
 
 Does it match [the most current version](https://github.com/segmentio/analytics-python/blob/master/analytics/version.py#L2)?
@@ -591,7 +591,7 @@ easy_install --upgrade segment-analytics-python
 In some cases, you will want to disable threads and send each request synchronously. To do so, you can use the `sync_mode` option:
 
 ```python
-import analytics
+import segment.analytics as analytics
 
 analytics.write_key = 'YOUR_WRITE_KEY'
 analytics.sync_mode = True

src/connections/spec/common.md

@@ -194,7 +194,7 @@ Other libraries only collect `context.library`, any other context variables must
 
 ## Integrations
 
-A dictionary of destination names that the message should be sent to. `'All'` is a special key that applies when no key for a specific destination n is found.
+A dictionary of destination names that the message should be sent to. `'All'` is a special key that applies when no key for a specific destination is found.
 
 Integrations defaults to the following: