Merge pull request #325 from segmentio/repo-sync

repo sync

Author: bot-docsteam

.github/Vocab/Docs/accept.txt

@@ -18,6 +18,7 @@ Adwords
 allowlist
 Amberflo
 Appboy
+Appsflyer
 blocklist
 boolean
 Chargebee

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2022-04-13 
+# destination categories last updated 2022-04-21 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2022-04-13 
+# destination data last updated 2022-04-21 
 items:
 - id: 60b5d0a01f3726b85dc05aab
   display_name: 2mee
@@ -587,7 +587,7 @@ items:
     defaultValue: {}
     description: >-
       Map values you pass into the context object to [Context Data
-      Variables](https://marketing.adobe.com/resources/help/en_US/sc/implement/context_data_variables.html)
+      Variables](https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/contextdata.html)
       in Adobe Analytics. Then you can use processing rules to map you Context
       Data Variables in Adobe to other variables with Adobe Analytics Processing
       Rules. In the box on the left, put your Segment context key. The box on
@@ -599,7 +599,7 @@ items:
       you wanted to map the page referrer, you would put: page.referrer. 
 
 
-      **NOTE**: By default we send all your `properties` as Context Data
+      **NOTE**: By default Segment send alls your `properties` as Context Data
       Variables so you do not need to map them again here.
     required: false
     label: Context Data Variables
@@ -9613,10 +9613,8 @@ items:
   website: https://www.custify.com/
   status: PUBLIC
   categories:
-  - Analytics
   - Customer Success
-  - Performance Monitoring
-  - Surveys
+  - CRM
   logo:
     url: >-
       https://public-segment-devcenter-production.s3.amazonaws.com/9873ccd2-76af-4491-9940-42016a404fd5.svg
@@ -25563,7 +25561,7 @@ items:
   display_name: Mailmodo
   name: Mailmodo
   slug: mailmodo
-  hidden: false
+  hidden: true
   endpoints:
   - us
   regions:
@@ -37724,7 +37722,7 @@ items:
   display_name: Willow
   name: Willow
   slug: willow
-  hidden: true
+  hidden: false
   endpoints:
   - us
   regions:

src/_data/catalog/regional-supported.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2022-04-13 
+# Last updated 2022-04-21 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2022-04-13 
+# source cateogries last updated 2022-04-21 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2022-04-13 
+# sources last updated 2022-04-21 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

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

@@ -2,8 +2,9 @@
 rewrite: true
 title: AppsFlyer Destination
 id: 54521fd525e721e32a72ee8f
+hide-personas-partial: true
 ---
-[AppsFlyer](https://www.appsflyer.com/) is the world's leading mobile attribution & marketing analytics platform, helping app marketers around the world make better decisions. Our AppsFlyer destination code is open-source. You can browse the code on GitHub for [iOS](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
+[AppsFlyer](https://www.appsflyer.com/){:target="blank"} is the world's leading mobile attribution & marketing analytics platform, helping app marketers around the world make better decisions. The AppsFlyer destination code is open-source. You can browse the code on GitHub for [iOS](https://github.com/AppsFlyerSDK/segment-appsflyer-ios){:target="blank"} and [Android](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration){:target="blank"}.
 
 Segment's Appsflyer destination code is open source and available on GitHub. You can view these repositories:
 - [Android](https://github.com/AppsFlyerSDK/appsflyer-segment-android-plugin){:target="_blank"}
@@ -18,8 +19,8 @@ Segment's Appsflyer destination code is open source and available on GitHub. You
   1. From the Segment web app, click **Catalog**.
   2. Search for "AppsFlyer" in the Catalog, select it, and choose which of your sources to connect the destination to.
   3. In the destination settings, enter your `AppsFlyer Dev Key`, which can be retrieved from the App Settings section of your AppsFlyer account.
-  4. Follow the instructions in the GitHub repos: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
-  5. After you build and release to the app store, we start translating and sending your data to AppsFlyer automatically.
+  4. Follow the instructions in the GitHub repositories: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios){:target="blank"} and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration){:target="blank"}.
+  5. After you build and release to the app store, Segment starts translating and sending your data to AppsFlyer automatically.
 
 **Important:** If you plan on using the server-side destination for an Android project, make sure to enter your **Android App ID**. If you are using only the mobile SDK, Android projects only require the **AppsFlyer Dev Key**. iOS projects always require both the **AppsFlyer Dev Key** and the **Apple App ID**. Also, note that if you do use the server-side destination, you will not be able to selectively disable calls sent to AppsFlyer using your Segment dashboard.
 
@@ -80,7 +81,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
                                 traits:@{ @"email": @"[email protected]" }];
 ```
 
-When you call `.identify()`, we will use AppsFlyer's `setCustomerUserID` to send the `userId` that was passed in.
+When you call `.identify()`, Segment uses AppsFlyer's `setCustomerUserID` to send the `userId` that was passed in.
 
 **Note:** `identify` calls are not supported using AppsFlyer's HTTP API at the moment. You can only send `.identify` calls if you have the AppsFlyer SDK bundled.
 
@@ -95,9 +96,9 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 
 When you call `track`, Segment translates it automatically and sends the event to AppsFlyer.
 
-We include all the event properties as callback parameters on the AppsFlyer event, and automatically translate `properties.revenue` to the appropriate AppsFlyer purchase event properties based on our spec'd properties.
+Segment includes all the event properties as callback parameters on the AppsFlyer event, and automatically translate `properties.revenue` to the appropriate AppsFlyer purchase event properties based on the spec'd properties.
 
-Finally, we automatically use AppsFlyer's `transactionId` deduplication when you send an an `orderId` (see the [e-commerce spec](/docs/connections/spec/ecommerce/v2/)).
+Finally, Segment uses AppsFlyer's `transactionId` deduplication when you send an `orderId` (see the [e-commerce spec](/docs/connections/spec/ecommerce/v2/)).
 
 ### Server
 
@@ -136,23 +137,24 @@ analytics.track({
   }
 });
 ```
-> Check your specific [serverside library docs](/docs/connections/sources/#server) for specifics on how to format the method properly.
+> Check your specific [server-side library docs](/docs/connections/sources/#server) for specifics on how to format the method properly.
 
-Finally, the serverside component will look for the following `properties` and handle them specially:
+Finally, the server-side component will look for the following `properties` and handle them specially:
 
 - `ip` (this should be the `ip` of your customer--this is not collected by Segment's libraries out-of-the-box)
-- `timestamp` (refer to AppsFlyer's docs on [how they process timestamps](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-). Since our libraries generate a [timestamp](/docs/connections/spec/common/#timestamps), we will always set this value)
+- `timestamp` (refer to AppsFlyer's docs on [how they process timestamps](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-){:target="blank"}. Since the libraries generate a [timestamp](/docs/connections/spec/common/#timestamps), Segment always sets this value)
 - `currency` (defaults to `"USD"`)
 - `revenue` (For `Order Completed` events, precedence is given to `total`, falling back to `properties.revenue`)
 
 All other `properties` will be sent to AppsFlyer as custom properties inside `eventValue`.
 
-> **Note:** Be sure to calibrate/update the time window in AppsFlyer's dashboard to see your events!
+> info ""
+> Be sure to calibrate/update the time window in AppsFlyer's dashboard to see your events!
 
 ## Install Attributed
 
 ### Client
-Segment will automatically trigger an `Install Attributed` event if you have **trackAttributionData** enabled in your settings, and the Segment-AppsFlyer integration installed in your app. The event payload will adhere to our `Install Attributed` event specification documented [here](/docs/connections/spec/mobile/#install-attributed) and will propagate to your other downstream destinations.
+Segment will automatically trigger an `Install Attributed` event if you have **trackAttributionData** enabled in your settings, and the Segment-AppsFlyer integration installed in your app. The event payload will adhere to the `Install Attributed` event specification documented [here](/docs/connections/spec/mobile/#install-attributed) and will propagate to your other downstream destinations.
 
 ### Server
 If you are tracking events server-side, AppsFlyer can still send attribution postbacks but you will need to configure this functionality in your AppsFlyer account. To enable this, navigate to your AppsFlyer app and on the sidebar of the main screen click on **Integrated Partners** and search for Segment. You will be prompted with a couple of configuration options and asked to input your Segment Write Key. Once enabled, successfully attributed app installs will begin showing up as `Install Attributed` events similar to the client side behavior documented above.

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

@@ -73,6 +73,12 @@ analytics.identify('userId123', {
 
 The first thing you'll want to do is to identify your users so Mixpanel knows who they are. You'll use the Identify method to accomplish this which takes the unique `userId` of a user and any `traits` you know about them.
 
+> info ""
+> **Important:** Mixpanel used to require that you call `alias` in all libraries to connect anonymous visitors to identified users. However, with the release of Mixpanel's new [Identity Merge feature](https://help.mixpanel.com/hc/en-us/articles/360039133851#enable-id-merge) this is no longer necessary. To enable ID Merge, go to your Mixpanel Settings Dashboard, navigate to **Project Settings > Identity Merge** and enable the setting from that screen. If you are _not_ using this setting, use the instructions below.
+
+
+As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`.
+
 ### People
 
 Segment doesn't send data to Mixpanel People by default, since this usually requires upgrading your Mixpanel account. To enable Mixpanel People, change the "Use Mixpanel People" setting in the Mixpanel Destination settings in Segment.

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

@@ -27,7 +27,7 @@ This destination supports the most important pain point for Salesforce users: ge
 
 ### Identifying a Lead
 
-Let's go through a quick javascript example of identifying a lead:
+The example below demonstrates identifying a lead:
 
 ```javascript
 analytics.identify('YOUR_USERS_ID', {
@@ -91,7 +91,7 @@ By default Segment does not send identify calls to Salesforce, given their stric
 
 ## Group
 
-`.group()` calls create or update **Account Objects** inside Salesforce. When Segment receives a group call, similar to the `.identify()` call, it first checks using the `groupId` to see if the Account Object already exists in your Salesforce account. Depending on the response, Segment updates that object or create a new one. Creating/updating Accounts is the default behavior of `group` events. If you would like to customize this you can do so using [Actions](#custom-actions)
+`.group()` calls create or update **Account Objects** inside Salesforce. When Segment receives a group call, similar to the `.identify()` call, it first checks using the `groupId` to see if the Account Object already exists in your Salesforce account. Depending on the response, Segment updates that object or create a new one. Creating/updating Accounts is the default behavior of `group` events.
 
 Take this sample `.group()` call that you might send to Segment: