Merge branch 'develop' into form-v2

forstisabella · forstisabella · commit be66de47b839 · 2023-05-08T20:01:19.000-04:00
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-05-02 
+# destination categories last updated 2023-05-04 
 items:
 - display_name: A/B Testing
   slug: a-b-testing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-05-02 
+# destination data last updated 2023-05-04 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -11810,9 +11810,9 @@ items:
     url: https://cdn.filepicker.io/api/file/C8J91fmdTveqfSKgWXuB
   methods:
     track: true
-    identify: true
-    group: true
-    alias: true
+    identify: false
+    group: false
+    alias: false
     screen: false
     page: true
   platforms:
@@ -61567,7 +61567,7 @@ items:
   display_name: TikTok Audiences
   name: TikTok Audiences
   slug: actions-tiktok-audiences
-  hidden: true
+  hidden: false
   endpoints:
   - US
   regions:
@@ -65670,163 +65670,6 @@ items:
       timestamp:
         '@path': $.timestamp
     trigger: type = "page"
-- id: 637c192eba61b944e08ee158
-  display_name: VWO Web Mode (Actions)
-  name: VWO Web Mode (Actions)
-  slug: vwo-web-mode-actions
-  hidden: true
-  endpoints:
-  - US
-  regions:
-  - us-west-2
-  - eu-west-1
-  url: connections/destinations/catalog/vwo-web-mode-actions
-  previous_names:
-  - VWO Web Mode (Actions)
-  website: https://vwo.com
-  status: PUBLIC
-  categories:
-  - A/B Testing
-  - Heatmaps & Recordings
-  logo:
-    url: https://cdn.filepicker.io/api/file/o9X4IJO1RDegnGVmfje0
-  mark:
-    url: https://cdn.filepicker.io/api/file/L6U6f3KrRoScOQbUDMKj
-  methods:
-    track: true
-    identify: true
-    group: true
-    alias: true
-    screen: false
-    page: true
-  platforms:
-    browser: true
-    mobile: false
-    server: false
-    warehouse: false
-  components: []
-  browserUnbundlingSupported: false
-  browserUnbundlingPublic: false
-  replay: false
-  connection_modes:
-    device:
-      web: false
-      mobile: false
-      server: false
-    cloud:
-      web: true
-      mobile: false
-      server: false
-  settings:
-  - name: libraryTolerance
-    type: number
-    defaultValue: 2500
-    description: >-
-      The maximum amount of time (in milliseconds) to wait for VWO’s full
-      library to be downloaded before simply displaying your original page.
-    required: true
-    label: Library Tolerance
-  - name: settingsTolerance
-    type: number
-    defaultValue: 2000
-    description: >-
-      The maximum amount of time (in milliseconds) to wait for test settings
-      before VWO will simply display your original page.
-    required: true
-    label: Settings Tolerance
-  - name: useExistingJquery
-    type: boolean
-    defaultValue: false
-    description: >-
-      If your page already includes JQuery, you can set this to “true”.
-      Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery
-      on the page to function correctly. 
-    required: true
-    label: Use Existing JQuery
-  - name: vwoAccountId
-    type: number
-    defaultValue: 0
-    description: Your VWO account ID, used for fetching your VWO async smart code.
-    required: true
-    label: VWO Account ID
-  actions:
-  - id: 6uTbf9uHvZBJ3YnMmFHWtZ
-    name: Track Event
-    slug: trackEvent
-    description: Sends Segment's track event to VWO
-    platform: WEB
-    hidden: false
-    defaultTrigger: type = "track"
-    fields:
-    - id: mvuYZipV7qAAF2Ta7VVVuy
-      sortOrder: 0
-      fieldKey: eventName
-      label: Name
-      type: STRING
-      description: Name of the event.
-      placeholder: ''
-      defaultValue:
-        '@path': $.event
-      required: true
-      multiple: false
-      choices: null
-      dynamic: false
-      allowNull: false
-    - id: u2SQL5Q9j5bxuW2QAAU75M
-      sortOrder: 1
-      fieldKey: properties
-      label: Properties
-      type: OBJECT
-      description: >-
-        JSON object containing additional properties that will be associated
-        with the event.
-      placeholder: ''
-      defaultValue:
-        '@path': $.properties
-      required: false
-      multiple: false
-      choices: null
-      dynamic: false
-      allowNull: false
-  - id: tR1J9N9e3vk4XtqGjUfTSm
-    name: Identify User
-    slug: identifyUser
-    description: Sends Segment's page event to VWO
-    platform: WEB
-    hidden: false
-    defaultTrigger: type = "identify"
-    fields:
-    - id: 2HnBcKRkZh78jdCgtj2FvV
-      sortOrder: 0
-      fieldKey: attributes
-      label: Attributes
-      type: OBJECT
-      description: >-
-        JSON object containing additional attributes that will be associated
-        with the user.
-      placeholder: ''
-      defaultValue:
-        '@path': $.traits
-      required: true
-      multiple: false
-      choices: null
-      dynamic: false
-      allowNull: false
-  presets:
-  - actionId: tR1J9N9e3vk4XtqGjUfTSm
-    name: Identify User
-    fields:
-      attributes:
-        '@path': $.traits
-    trigger: type = "identify"
-  - actionId: 6uTbf9uHvZBJ3YnMmFHWtZ
-    name: Track Event
-    fields:
-      eventName:
-        '@path': $.event
-      properties:
-        '@path': $.properties
-    trigger: type = "track"
 - id: 5d25d6e0885427000195bf80
   display_name: WalkMe
   name: WalkMe
diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2023-05-02 
+# Last updated 2023-05-04 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2023-05-02 
+# source cateogries last updated 2023-05-04 
 items:
   - display_name: A/B Testing
     slug: a-b-testing
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2023-05-02 
+# sources last updated 2023-05-04 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -380,7 +380,7 @@ items:
     isCloudEventSource: false
     slug: csharp
     url: connections/sources/catalog/libraries/mobile/csharp
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:
diff --git a/src/connections/destinations/catalog/intercom/index.md b/src/connections/destinations/catalog/intercom/index.md
@@ -493,7 +493,7 @@ If you are sending those two calls, then check that the CSS selector for the wid
 
 ### My client-side and server-side calls are going to one Segment source, but different Intercom projects
 
-Server-side calls go the the project selected when you authenticated your Intercom account while setting up the destination. Client-side calls go to the project referenced with the [App ID setting](#app-id-required-for-analyticsjs-and-mobile).
+Server-side calls go to the project selected when you authenticated your Intercom account while setting up the destination. Client-side calls go to the project referenced with the [App ID setting](#app-id-required-for-analyticsjs-and-mobile).
 Make sure those projects are the same.
 
 ### I'm seeing a "Cannot have more than 120 active event names" error
diff --git a/src/connections/destinations/catalog/klaviyo/index.md b/src/connections/destinations/catalog/klaviyo/index.md
@@ -142,6 +142,8 @@ analytics.track({
 
 When you call `track` on `analytics.js`, Segment calls Klaviyo's `track` with the same parameters.
 
+If you include `properties.revenue` in a track event, Segment maps it to Klaviyo's `$value` event.
+
 > info ""
 > When you're tracking client-side, some Klaviyo events require you send an Identify call  before a Track call. 
 
diff --git a/src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md b/src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md
@@ -74,11 +74,14 @@ Facebook offers the Facebook Pixel, which allows you to retarget these types of
 
 ### 1. Authorize Facebook Custom Audiences
 
-- Go to your Space in your Segment Workspace.
-- Go to the Destinations tab and click “Add Destination”.
+- Go to your Space in your Segment Workspace and click Engage Settings.
+- Go to the Destinations tab and click “Add Destination”. 
 - Select the Facebook Custom Audiences option, and click **Configure Facebook Custom Audiences**.
 - Authorize Facebook Ads and select a Facebook account ID to sync to.
 
+> info ""
+> Add the destination within the Engage space and not through the connections pipeline to ensure proper configuration.
+
 ### 2. Create an audience in Engage & connect to Facebook
 
 - Go to the Audience Builder in Engage and create a new Audience with your desired event and trait criteria.
diff --git a/src/connections/destinations/catalog/userpilot/index.md b/src/connections/destinations/catalog/userpilot/index.md
@@ -1,9 +1,9 @@
 ---
 rewrite: true
-title: Userpilot
+title: Userpilot Web Plugin
 id: 5ca9d0c1b7119500014381d3
 ---
-[Userpilot](https://userpilot.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) helps product teams increase user adoption by allowing them to trigger highly personalized onboarding experiences across the user journey. The Segment integration will help you install and send data to Userpilot without added development time.
+[Userpilot Web Plugin](https://userpilot.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} helps product teams increase user adoption by allowing them to trigger highly personalized onboarding experiences across the user journey. The Segment integration will help you install and send data to Userpilot without added development time.
 
 This destination is maintained by Userpilot. For any issues with the destination, [contact the Userpilot Support team](mailto:support@userpilot.io).
 
@@ -15,8 +15,8 @@ This destination is maintained by Userpilot. For any issues with the destination
 {% include content/connection-modes.md %}
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Userpilot" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "App Token" into your Segment Settings UI which you can find from your [Userpilot dashboard](https://app.userpilot.io/settings/setup) within the code snippet that looks like this `<script src = "https://deploy.userpilot.io/73fe57o8.js"></script>` where `73fe57o8` is the value you want to use.
+2. Search for *Userpilot Web Plugin* in the Catalog, select it, and choose the source you want to connect the destination to.
+3. Enter the **App Token** into your Segment Settings UI which you can find from your [Userpilot dashboard](https://app.userpilot.io/settings/setup){:target="_blank"} within the code snippet that looks like this `<script src = "https://deploy.userpilot.io/73fe57o8.js"></script>` where `73fe57o8` is the value you want to use.
 
 ## Page
 If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
@@ -41,7 +41,7 @@ Calling `identify` from `analytics.js` will trigger the `userpilot.identify`. We
 
 Data passed in the `identify` can be organized under different categories.
 * Properties about the user such as `plan` or `userRole` to help targetting a specifc segment.
-* Properties to personlize the content of the Userpilot experiences such as `name` or `company`
+* Properties to personalize the content of the Userpilot experiences such as `name` or `company`.
 * Properties to target users based on their lifecycle such as `createdAt`. This will allow you to target newly created accounts or accounts that have yet to achieve a certain feature in the user lifecyle.
 
 
@@ -53,4 +53,4 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 analytics.track('Clicked Login Button')
 ```
 
-Calling `track` from `analytics.js` will trigger `userpilot.track`. This will send events data to Userpilot where it can be used for content triggering.
+Calling `track` from `analytics.js` will trigger `userpilot.track`. This sends event data to Userpilot where it can be used for content triggering.
diff --git a/src/connections/sources/catalog/cloud-apps/mailchimp/index.md b/src/connections/sources/catalog/cloud-apps/mailchimp/index.md
@@ -44,5 +44,6 @@ Collections are the groupings of resources we pull from your source. In your war
 |  ------ | ------ | ------ |
 |  `conversations` | object | Conversation tracking is a [paid feature](http://kb.mailchimp.com/accounts/billing/how-mailchimp-pricing-plans-work) that lets you view subscribers' replies to your campaigns from inside your MailChimp account. Fetched using Mailchimp's [`/conversations`endpoint](https://mailchimp.com/developer/reference/conversations/). |
 |  `lists` | object | The state of your various lists in Mailchimp. Fetched using Mailchimp's [`/lists` endpoint](https://mailchimp.com/developer/reference/lists/). |
+|  `list members` | object | Get the list of members in a MailChimp list. Fetched using Mailchimp's [`/lists` endpoint] If you are interested in this collection, [contact Segment Support](https://segment.com/help/contact/) |
 |  `campaigns` | object | Your Mailchimp campaigns. Fetched using Mailchimp's [`/campaigns` endpoint](https://mailchimp.com/developer/reference/campaigns/). |
 |  `subscriber activity` | object | **Currently unavailable** Mailchimp's subscriber activity endpoint cannot support our Sources product. If you are interested in this collection, contact your MailChimp Client Success Manager and request that they update their export API functionality.* |
diff --git a/src/engage/onboarding.md b/src/engage/onboarding.md
@@ -70,7 +70,7 @@ Start by creating a SendGrid account and then upgrading to the SendGrid Pro Plan
 
 ### Create a subuser and check the dedicated IP address
 
-Next, you’ll create a SendGrid subuser and ensure that a dedicated IP has been assigned:
+Next, you’ll [create a SendGrid subuser](https://docs.sendgrid.com/ui/account-and-settings/subusers#create-a-subuser){:target="_blank"} and ensure that a dedicated IP has been assigned:
 
 1. In your SendGrid space, navigate to **Settings > Subuser Management**, then click **Create New Subuser**.
 2. In the **Create New Subuser** window, create a username for the subuser, then add an email address and password. Your SendGrid subuser username must begin with the prefix `twilio_engage_app_`. Add a unique identifier to the end of the prefix, for example, `twilio_engage_app_someusername`.
@@ -137,7 +137,10 @@ You’ll now need to enable event webhooks, which trigger webhook notifications
 
 Now, you'll generate an API key and API Key ID within SendGrid. **With your SendGrid account open in one tab, open your [Segment workspace](https://app.segment.com/workspaces){:target="_blank"} open in another. You’ll need both open to copy and paste the API credentials into your Engage settings.**
 
-1. Within your SendGrid subuser space, navigate to **Settings > API Keys**.
+> info "SendGrid Subuser Step"
+> Carry out the following steps in your SendGrid **subuser** space.
+
+1. **Within your SendGrid subuser space**, navigate to **Settings > API Keys**.
 2. Click the **Create API Key** button.
 3. In the Create API Key window, name your API key using the prefix `twilio_engage_app_`, with a suffix of your choice added to the end, like `twilio_engage_app_somekey`.
 4. Under API Key Permissions, select the **Full Access** radio button, then click **Create & View**.
diff --git a/src/protocols/validate/connect-sources.md b/src/protocols/validate/connect-sources.md
@@ -6,7 +6,7 @@ redirect_from: '/protocols/validate/'
 {% include content/plan-grid.md name="protocols" %}
 
 
-With your Tracking Plan is complete, it's time to apply the Tracking Plan to one or more Sources. Select **Connect Source** from the right hand menu for your specific Tracking Plan.
+With your Tracking Plan complete, it's time to apply the Tracking Plan to one or more Sources. Select **Connect Source** from the right hand menu for your specific Tracking Plan.
 
 ![Screenshot of the Tracking Plans page, with the overflow menu selected.](../images/5763308453_Screen+Shot+2018-08-31+at+5.54.18+PM.png)
 
diff --git a/src/unify/debugger.md b/src/unify/debugger.md
@@ -7,18 +7,18 @@ redirect_from:
 
 The Profile Source Debugger enables you to inspect and monitor events that Segment sends downstream
 
-Because Segment generates a unique Source for every Destination connected to a Space, the Debugger gives you insight into how Segment sends events before they reach their Destination. This automatically generated source cannot be deleted even when the destination is removed, in order for Segment to function as designed. The source will be reused by Segment as needed.
+Because Segment generates a unique source for every destination connected to a Space, the Debugger gives you insight into how Segment sends events before they reach their destination. Even when a destination is removed, you can't delete and shouldn't disable this source for Segment to function as designed. The source will be reused by Segment as needed.
 
-The Debugger provides you with the payload information you need to troubleshoot potential formatting issues and ensure Segment sends events as your Destinations expect.
+The Debugger provides you with the payload information you need to troubleshoot potential formatting issues and ensure Segment sends events as your destinations expect.
 
 ## Working with the Debugger
- 
-Navigate to the Debugger tab on the Unify settings page of the space you want to debug. Select the Source you want to inspect in the Debugger.
+
+Navigate to the Debugger tab on the Unify settings page of the space you want to debug. Select the source you want to inspect in the Debugger.
 
 The Debugger presents a stream of incoming events. The event inspector displays three tabs for each event:
 
-* **Pretty view** shows the actual API call Segment sends to your Destination.
-* **Raw view** shows the full JSON object Segment sends to your Destination from the calls you sent, including timestamps, properties, traits, and ids.
+* **Pretty view** shows the actual API call Segment sends to your destination.
+* **Raw view** shows the full JSON object Segment sends to your destination from the calls you sent, including timestamps, properties, traits, and ids.
 * **Violations** displays any violations triggered by the event.
 
 Similar to the Connections Debugger, you can search through events using information contained within the event's payload.
