Merge branch 'master' into DOC-151_Redshift-update

markzegarelli · markzegarelli · commit 53ce7e5656c4 · 2021-04-09T13:57:17.000-07:00
diff --git a/Gemfile.lock b/Gemfile.lock
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2021-03-29 
+# destination categories last updated 2021-04-01 
 items:
 - display_name: Email Marketing
   slug: email-marketing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination data last updated 2021-03-29 
+# destination data last updated 2021-04-09 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -12123,6 +12123,64 @@ items:
   previous_names:
   - Keen IO
   - Keen
+- display_name: Kevel
+  slug: kevel
+  name: catalog/destinations/kevel
+  description: Target users using your Segment user data with Kevel's UserDB.
+  hidden: false
+  url: connections/destinations/catalog/kevel
+  status: PUBLIC_BETA
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/dcf9c366-5cf3-479f-8465-bb15e2505df0.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/47bc76ec-43e8-4a7c-987f-87e25f08f9e9.svg
+  categories:
+  - Advertising
+  components: []
+  platforms:
+    browser: true
+    server: true
+    mobile: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  methods:
+    alias: false
+    group: false
+    identify: true
+    page_view: false
+    track: false
+  settings:
+  - name: apiKey
+    display_name: API Key
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: '^.{8,}$'
+    description: You can generate a new API Key from the Settings page in Kevel
+    settings: []
+  - name: networkId
+    display_name: Network ID
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: ''
+    description: You can find this value in the top bar of the Kevel App
+    settings: []
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+  previous_names:
+  - Kevel
 - display_name: Kitemetrics
   slug: kitemetrics
   name: catalog/destinations/kitemetrics
@@ -13093,17 +13151,6 @@ items:
       Required for client-side integration functionality. You can generate your
       API Key on the Segment integration page of the Lou Dashboard.
     settings: []
-  - name: organizationId
-    display_name: Organization ID
-    type: STRING
-    deprecated: false
-    required: false
-    string_validators:
-      regexp: ''
-    description: >-
-      Required for client-side integration functionality. You can find your
-      Organization ID on the Segment integration page of the Lou Dashboard.
-    settings: []
   connection_modes:
     device:
       web: false
@@ -13672,26 +13719,6 @@ 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
@@ -13714,6 +13741,26 @@ 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
@@ -15325,7 +15372,12 @@ items:
 - display_name: Nielsen DCR
   slug: nielsen-dcr
   name: catalog/destinations/nielsen-dcr
-  description: ''
+  description: >-
+    Consumers engage with digital content across many platforms, so it's
+    imperative that market participants have clear knowledge of their total
+    content consumption. Nielsen's Digital Content Ratings provides that insight
+    by including video and static content ratings for web pages and app
+    sections.
   hidden: false
   url: connections/destinations/catalog/nielsen-dcr
   status: PUBLIC_BETA
@@ -15413,6 +15465,18 @@ items:
       you would like to set up a custom property mapping for content asset ids
       please indicate the name of the property here. 
     settings: []
+  - name: customSectionProperty
+    display_name: Custom Page/Screen Section Property Name
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: >-
+      Segment will map the page/screen `name` field to Nielsen's `section`
+      field. If you would like to set up a custom property mapping for the
+      page/screen section name please indicate the name of the property here. 
+    settings: []
   - name: nolDevDebug
     display_name: Enable Debug Mode
     type: BOOLEAN
@@ -18009,15 +18073,6 @@ items:
       required: false
       description: Map your Segment properties to Responsys Columns
       settings:
-      - name: columns
-        display_name: Segment Property Name
-        type: STRING
-        deprecated: false
-        required: true
-        string_validators:
-          regexp: ''
-        description: Enter the Segment Property Name.
-        settings: []
       - name: fieldName
         display_name: Responsys Column Name
         type: STRING
@@ -18051,6 +18106,15 @@ items:
         required: false
         description: Mark this property as a Primary Key in Responsys.
         settings: []
+      - name: columns
+        display_name: Segment Property Name
+        type: STRING
+        deprecated: false
+        required: true
+        string_validators:
+          regexp: ''
+        description: Enter the Segment Property Name.
+        settings: []
     - name: mapEmail
       display_name: Map Email
       type: BOOLEAN
@@ -23033,9 +23097,9 @@ items:
     url: >-
       https://public-segment-devcenter-production.s3.amazonaws.com/b6a1db0f-1b55-4651-9cc5-d78d8365a447.svg
   categories:
+  - Surveys
   - Customer Success
   - Analytics
-  - Surveys
   - Personalization
   components: []
   platforms:
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2021-03-29 
+# source cateogries last updated 2021-04-01 
 items:
 - display_name: Server
   slug: server
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# sources last updated 2021-03-29 
+# sources last updated 2021-04-01 
 items:
 - display_name: .NET
   slug: net
diff --git a/src/_data/sidenav/strat.yml b/src/_data/sidenav/strat.yml
@@ -146,5 +146,5 @@ sections:
     title: Analytics-React-Native mobile source
   - path: /connections/sources/catalog/libraries/mobile/react-native/troubleshooting
     title: Troubleshooting Analytics-React-Native
-  - path: /connections/sources/catalog/libraries/mobile/android/react-faqs
+  - path: /connections/sources/catalog/libraries/mobile/react-native/react-faqs/
     title: React-Native FAQs
diff --git a/src/_includes/content/personas.md b/src/_includes/content/personas.md
@@ -1,7 +1,7 @@
 ## Personas
 
-You can send computed traits and audiences generated through [Segment Personas](/docs/personas/) to this destination as a **user property**. To learn more about Personas, contact us for a [demo](https://segment.com/contact/demo).
+You can send computed traits and audiences generated through [Segment Personas](/docs/personas/) to this destination as a **user property**. To learn more about Personas, contact us for a [demo](https://segment.com/demo).
 
-For user-property destinations, an [identify](/docs/connections/spec/identify/) call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property `order_completed_last_30days: true`, and when this user no longer satisfies we will set that value to `false`. 
+For user-property destinations, Personas sends an [Identify call](/docs/connections/spec/identify/) to the destination for each user that is added or removed from an audience. The property name is the `snake_cased` version of the audience name you provide, with a boolean (`true`/`false`) value to indicate if they're a member of the audience. For example, when a user first completes an order in the last 30 days, Personas sends an identify call with the property `order_completed_last_30days: true`, and when this user no longer satisfies these criteria (if the user does not complete another order over 30 days) Personas sends another Identify call to set that value to `false`.
 
-When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
+When Personas first creates the audience, it sends an Identify call for every user in the audience. Later syncs only update users which were added or removed since the last sync.
diff --git a/src/_includes/sidebar/related-categories.html b/src/_includes/sidebar/related-categories.html
@@ -9,7 +9,7 @@
     <ul class="related-categories__list menu-side">
       {% for category in current_integration.categories %}
         <li class="related-categories__item">
-          <a href="{{ catalog_url }}/#{{ category | slugify }}" class="related-categories__link">
+          <a href="{{ catalog_url }}#{{ category | slugify }}" class="related-categories__link">
             {{ category }}
           </a>
         </li>
diff --git a/src/connections/data-residency.md b/src/connections/data-residency.md
@@ -2,6 +2,11 @@
 title: Data Residency
 beta: true
 ---
+
+> info ""
+> **Note**: Data residency is in public beta, and its use is governed by the [(1) Segment First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/) and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/).
+
+
 Segment offers customers the option to lead on data residency by providing regional infrastructure across Europe, Middle East, Africa and Asia Pacific. The default region for all customers is in Oregon, United States. The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region.
 
 ## Enable Local Data Ingest and Storage
diff --git a/src/connections/destinations/catalog/amplitude/index.md b/src/connections/destinations/catalog/amplitude/index.md
@@ -448,7 +448,10 @@ Segment Alias call allows you to associate a Segment user's `previousId`
 with the user's `userId`, or what Amplitude refers to, respectively, as a
 `user_id` and a `global_user_id`.
 
-By default, Segment does **NOT** send Alias events to Amplitude. To forward Alias events from Segment, go to your Amplitude destination settings in the Segment web app, and set the **Enable Alias** setting to "on". Once enabled, Segment forwards both client-based and server-based Alias calls. Segment processes _all_ Alias calls before sending them to Amplitude, so you won't see a `usermap` request to Amplitude if you check your browser's Network activity after making a Segment Alias call.
+By default, Segment does **NOT** send Alias events to Amplitude. To forward Alias events from Segment, go to your Amplitude destination settings in the
+Segment web app, and set the **Enable Alias** setting to "on". Once enabled, Segment forwards Alias events from Segment's servers only. This means
+that Alias events reach Amplitude only when you're sending events from the client and have set your Amplitude instance's connection mode to "Cloud Mode",
+or are sending Alias events from a Segment server-side library (such as Node).
 
 > note ""
 > To use Alias, you must have the Amplitude Portfolio add-on enabled.
diff --git a/src/connections/destinations/catalog/iterable/index.md b/src/connections/destinations/catalog/iterable/index.md
@@ -67,11 +67,25 @@ Subsequent `track` with `userId`
 
 Iterable also supports Segment's [ecommerce events](/docs/connections/spec/ecommerce/v2/). This works just as you would expect, using the `track` method.
 
-There is one important difference from the Segment documentation. If you are using the `Product Added` / `Product Removed` events, you must also pass along the "products" field with the cart info, just like Segment's example for the `Order Completed` event. You must include all required fields for the Purchase events in Iterable, which includes the total value of the purchase with the property: `total`. This value works best as a float, double, and possibly an integer. An example might look like this:
+Iterable has one important difference from the Segment Ecommerce spec. If you use the `Product Added` / `Product Removed`/ `Order Completed` events, you must include the "products" field with the cart info, as in the `Order Completed` example event. You must include [all required fields for the Purchase events in Iterable](https://api.iterable.com/api/docs#commerce_trackPurchase).  This includes the total value of the purchase as `total` (best as a float, double, and possibly an integer), and an array of objects called `products`. Each product must include an `id` or `productId` as a string, and a `name`, `price`, and `quantity` on each product object in the array. These are used to map to Iterable's expected `items` array. An example might look like this:
 
 ```js
 analytics.track("Order Completed", {
-  total: 100.00
+  total: 100.00,
+  products: [
+    {
+      product_id: '507f1f77bcf86cd799439011',
+      name: 'Monopoly: 3rd Edition',
+      price: 19,
+      quantity: 1
+    },
+    {
+      product_id: '505bd76785ebb509fc183733',
+      name: 'Uno Card Game',
+      price: 3,
+      quantity: 2
+    }
+  ]
 });
 ```
 
diff --git a/src/connections/destinations/catalog/kevel/index.md b/src/connections/destinations/catalog/kevel/index.md
@@ -0,0 +1,32 @@
+---
+rewrite: true
+title: Kevel Destination
+---
+
+With [Kevel](https://kevel.co)'s ad serving APIs, you can build custom ad platforms for sponsored listings, internal promotions, native ads, and more — so you can take back the Internet and drive more revenue.
+
+This destination is maintained by Kevel. For any issues with the destination, [contact the Kevel Support team](mailto:support@kevel.co).
+
+
+## Getting Started
+
+{% include content/connection-modes.md %} 
+
+1. From the Segment web app, click **Catalog**.
+2. Search for "Kevel" in the Catalog, select it, and choose which of your sources to connect the destination to.
+3. In the [Kevel App](https://app.kevel.co), click the Information icon in the top-right navigation to find your **Network ID**.
+4. Still in the [Kevel app](https://app.kevel.co), go to **Settings -> API Keys** in the top navigation. Either copy an existing key, or generate a new one.
+5. Back in the Kevel destination settings in the Segment app, enter the values for the **Network ID** and the **API Key**.
+
+
+## Identify
+
+If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
+
+```js
+analytics.identify('userId123', {
+  email: 'john.doe@example.com'
+});
+```
+
+Segment sends Identify calls to Kevel as [UserDB updates](https://dev.kevel.co/docs/userdb-1). Traits with `boolean` values are stored as `interests` on the UserDB Record. Other traits are stored in the `custom` property.
diff --git a/src/connections/functions/usage.md b/src/connections/functions/usage.md
@@ -14,7 +14,7 @@ The amount of time you are allotted changes depending on your [Segment pricing p
 
 We measure execution time from when the function first receives an event to the time the function either returns successfully or throws an error. If Segment retries your function (for example, if there was a timeout), those retries also count as billable execution time.
 
-Functions are billed in 100ms increments, rounded up. For example, a function that takes 80ms to complete will be billed as 100ms. A function that takes 105ms to complete will be billed as 200ms.
+Starting on April 8, 2021 Functions usage is measured in millisecond increments. This makes your usage and billing much more precise. Prior to this change, Functions was measured in 100ms increments, and then rounded up. For example, a function that took 80ms to complete was previously billed as 100ms. Using the new usage calculation, it is billed as 80ms. 
 
 ## Execution timeouts
 
diff --git a/src/connections/sources/catalog/libraries/server/php/index.md b/src/connections/sources/catalog/libraries/server/php/index.md
@@ -517,6 +517,4 @@ $ sudo service cron reload    # reload the cron daemon
 
 If you only need support for PHP5, the team at [Underground Elephant](http://undergroundelephant.com/) has released a [3rd-party library](https://github.com/uecode/segment-io-php) based on Guzzle.
 
-For [FuelPHP](http://fuelphp.com/) support, our friends at [Bit API Hub](http://bitapihub.com/) built this [3rd-party library Segment package](https://github.com/BitAPIHub/FuelPHP-Segment-io).
-
 If you're using Laravel 4 our friends at Catchet have written a wrapper for you! Docs and GitHub repo can be found here: https://github.com/cachethq/Laravel-Segment
diff --git a/src/connections/sources/catalog/libraries/website/shopify-littledata/index.md b/src/connections/sources/catalog/libraries/website/shopify-littledata/index.md
diff --git a/src/connections/spec/ecommerce/v2.md b/src/connections/spec/ecommerce/v2.md
