Merge branch 'master' into littledata-docs-update

Author: edwardupton

_config.yml

@@ -55,3 +55,4 @@ algolia:
   index_name:     segment-docs
   files_to_exclude:
     - _release_notes/*
+  nodes_to_index: 'p, table#limit'

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2021-04-20 
+# destination categories last updated 2021-04-23 
 items:
 - display_name: Email Marketing
   slug: email-marketing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination data last updated 2021-04-20 
+# destination data last updated 2021-04-23 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -6587,11 +6587,9 @@ items:
   previous_names:
   - Digioh
   logo:
-    url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/efc8aed0-e80b-4285-80b3-12ec1294257e.svg
+    url: 'https://cdn.filepicker.io/api/file/edr4ZVFPT22RIAMui2Kk'
   mark:
-    url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/c4298d78-7115-4f48-b8ef-0e7aab492ff5.svg
+    url: 'https://cdn.filepicker.io/api/file/JE0a9XqxSdujRRcOY9tP'
   categories:
   - Email Marketing
   - Marketing Automation
@@ -14474,6 +14472,26 @@ items:
       required: false
       description: Map your Segment properties to the Marketo Activity Fields
       settings:
+      - name: marketoAttributeType
+        display_name: Marketo Field Type
+        type: SELECT
+        deprecated: false
+        required: true
+        select_validators:
+          select_options:
+          - string
+          - boolean
+          - number
+          - date
+        description: Enter the Marketo Field type.
+        settings: []
+      - name: primaryKey
+        display_name: Set as Primary Key
+        type: BOOLEAN
+        deprecated: false
+        required: false
+        description: Mark this property as the Primary field in Marketo.
+        settings: []
       - name: segmentProperty
         display_name: Segment Property Name
         type: STRING
@@ -14496,26 +14514,6 @@ items:
           Enter the Marketo Field name. Make sure to copy and paste the exact
           API Name for your field as it appears in Marketo.
         settings: []
-      - name: marketoAttributeType
-        display_name: Marketo Field Type
-        type: SELECT
-        deprecated: false
-        required: true
-        select_validators:
-          select_options:
-          - string
-          - boolean
-          - number
-          - date
-        description: Enter the Marketo Field type.
-        settings: []
-      - name: primaryKey
-        display_name: Set as Primary Key
-        type: BOOLEAN
-        deprecated: false
-        required: false
-        description: Mark this property as the Primary field in Marketo.
-        settings: []
     - name: event
       display_name: Segment Event Name
       type: STRING

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2021-04-20 
+# source cateogries last updated 2021-04-23 
 items:
 - display_name: Server
   slug: server

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# sources last updated 2021-04-20 
+# sources last updated 2021-04-23 
 items:
 - display_name: .NET
   slug: net

src/_data/sidenav/main.yml

@@ -273,8 +273,8 @@ sections:
     title: Personas and GDPR
   - path: /personas/faqs
     title: Personas FAQs
-  - path: /personas/rate-limits
-    title: Rate Limits
+  - path: /personas/product-limits
+    title: Personas Limits
 - section_title: Privacy
   section:
   - path: /privacy

src/connections/destinations/add-destination.md

@@ -125,8 +125,9 @@ You can add multiple instances of a destination using the Segment Config API. Se
 ### Multi-instance destinations and Device-mode
 
 - **_Mobile_ sources cannot connect to multiple instances of a destination.**
+  - _Beware_: Bundling one instance of a destination in a mobile source while having other instances of that destination for a given source will have unexpected consequences.
 - **You can connect a source to an unlimited number of instances of a destination if all of the instances use cloud-mode.** Destinations using cloud-mode receive data directly from the Segment servers.
-- **Each source can only connect to one *device-mode* instance of a destination, in addition to unlimited cloud-mode instances.** A device-mode instance of a destination receives data directly from the user’s browser (instead of through the Segment servers), by bundling a copy of destination’s code with the Segment SDK. Segment can’t bundle multiple copies of the destination SDK and so it can’t send data to multiple instances of the destination from the browser.
+- **Non-mobile sources can only connect to one *device-mode* instance of a destination, in addition to unlimited cloud-mode instances.** A web browser device-mode instance of a destination receives data directly from the user’s browser (instead of through the Segment servers), by bundling a copy of destination’s code with the Segment SDK. Segment can’t bundle multiple copies of the destination SDK and so it can’t send data to multiple instances of the destination from the browser.
 - **You cannot connect a source to more than one instance of a destination that operates in device-mode only**. These destinations can only accept data from code directly on the user’s device, and Segment cannot include duplicates of that code for a single source.
 
 For more information see [the compatible destination lists below](#multi-instance-compatible-destinations).

src/connections/destinations/catalog/adwords-remarketing-lists/index.md

@@ -20,7 +20,18 @@ hide-boilerplate: true
 | [Google Analytics](/docs/connections/destinations/catalog/google-analytics/)             | Yes - Event Destination   |
 | Google Adwords Remarketing Lists        | Yes - List Destination   |
 
+## Details
 
+- **Supports Personas**: Yes
+- **Personas Destination type**: List
+- **Must create audience_name field before Personas can update those values?**: No, Personas creates the audience for you.
+- **Audience appears as**: A Customer list, in the Audience Manager under Audience lists.
+- **Destination rate limit**: None
+- **Lookback window allowed**: Yes
+- **Identifiers required** : Email or Mobile Device ID (IDFA)
+- **Identifiers accepted** : Email and Mobile Device ID (IDFA)
+- **Client or Server-Side Connection**: Server-side
+- **Minimum audience size required**: 100
 
 ## Overview
 
@@ -68,19 +79,6 @@ When you create an audience in Personas and connect it to Google Adwords Remarke
 2. Adds any users that fit the audience definition based on Email or Mobile ID (IDFA). Google uses these identifiers to match users in your list to users in the Google system who can be served ads.
 3. Every hour, Segment either adds or removes users from this audience based on the same identifiers.
 
-## Quick Info
-
-- **Supports Personas**: Yes
-- **Personas Destination type**: List
-- **Must create audience_name field before Personas can update those values?**: No, Personas creates the audience for you.
-- **Audience appears as**: A Customer list, in the Audience Manager under Audience lists.
-- **Destination rate limit**: None
-- **Lookback window allowed**: Yes
-- **Identifiers required** : Email or Mobile Device ID (IDFA)
-- **Identifiers accepted** : Email and Mobile Device ID (IDFA)
-- **Client or Server-Side Connection**: Server-side
-- **Minimum audience size required**: 100
-
 
 <!-- commenting out for now because this table format takes a wholepage
 | **Support for Personas**      | Yes       |

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

@@ -306,7 +306,7 @@ You can also see this in the contact property history for each user record.
 
 
 
-## HubSpot Personas Quick Info
+## HubSpot Personas Details
 
 - **Personas Destination type**: Event Method (data is delivered to this Destination one-by-one on a realtime basis)
 - **Traits and Audiences created by**: Identify calls add and update traits and audiences as traits on the user, Track calls send events for `Audience Entered` and `Audience Exited`.

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

@@ -191,7 +191,7 @@ To send computed traits or audiences to Iterable, you first must connect it to y
 3. On the set up screen, enter in your API Key for the Iterable.
 
 
-## Iterable Personas Quick Info
+## Iterable Personas Details
 
 - **Personas Destination type**: Event Method (data is delivered to this Destination one-by-one on a realtime basis)
 - **Traits and Audiences created by**:You can add traits and audiences as user properties using `identify` calls. You can send audiences as `Audience Entered` or `Audience Exited` `track` calls with the audience name as an event property.