Merge branch 'segmentio:develop' into develop

Author: nagendra-d

src/connections/reverse-etl/index.md

@@ -97,28 +97,29 @@ To create a mapping:
 4. Select the model to sync from.
 5. Select the **Action** you want to sync and click **Next**.
       * Actions determine the information sent to the destination. The list of Actions will be unique to each destination.
-6. In the **Select record to map and send** section, select which records to send to your destination after Segment completes extracting data based on your model. You can choose from:
+6. Add the mapping's name. The initial name will default to the Action's name (e.g. 'Track Event') but is completely customizable. It will allow you to identify the mapping amongst others.
+7. In the **Select record to map and send** section, select which records to send to your destination after Segment completes extracting data based on your model. You can choose from:
       * Added records
       * Updated records
       * Added or updated records
       * Deleted records
-7. Select a test record to preview the fields that you can map to your destination in the **Add test record** field.
-8. Select the Schedule type for the times you want the model’s data to be extracted from your warehouse. You can choose from:
+8. Select a test record to preview the fields that you can map to your destination in the **Add test record** field.
+9. Select the Schedule type for the times you want the model’s data to be extracted from your warehouse. You can choose from:
     * **Interval**: Extractions perform based on a selected time cycle.
     * **Day and time**: Extractions perform at specific times on selected days of the week.
-9. Select how often you want the schedule to sync in **Schedule configuration**.
+10. Select how often you want the schedule to sync in **Schedule configuration**.
     * For an **Interval** schedule type, you can choose from: 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 6 hours, 8 hours, 12 hours, 1 day.
         * 15 minutes is considered real-time for warehouse syncs
     * For a **Day and time** schedule type, you can choose the day(s) you’d like the schedule to sync as well as the time.
         * You can only choose to start the extraction at the top of the hour.
         * Scheduling multiple extractions to start at the same time inside the same data warehouse causes extraction errors.
-10. Define how to map the record columns from your model to your destination in the **Select Mappings** section.
+11. Define how to map the record columns from your model to your destination in the **Select Mappings** section.
     * You map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
     * If you're setting up a destination action, depending on the destination, some mapping fields may require data to be in the form of an object or array. See the [supported objects and arrays for mapping](#supported-object-and-arrays).
-11. *(Optional)* Send a test record to verify the mappings correctly send to your destination.
-12. Click **Create Mapping**.
-13. Select the destination you’d like to enable on the **My Destinations** page under **Reverse ETL > Destinations**.
-14. Turn the toggle on for the **Mapping Status**. Events that match the trigger condition in the mapping will be sent to the destination.
+12. *(Optional)* Send a test record to verify the mappings correctly send to your destination.
+13. Click **Create Mapping**.
+14. Select the destination you’d like to enable on the **My Destinations** page under **Reverse ETL > Destinations**.
+15. Turn the toggle on for the **Mapping Status**. Events that match the trigger condition in the mapping will be sent to the destination.
     * If you disable the mapping state to the destination, events that match the trigger condition in the mapping won’t be sent to the destination.
 
 To add multiple mappings from your warehouse to your destination, repeat steps 1-13 above.

src/connections/sources/catalog/libraries/website/javascript/analytics-js-2.md

@@ -1006,27 +1006,4 @@ Here are some examples of using Analytics.js. Note that the examples assume Anal
 
 ## External dependencies
 
-Analytics.js includes the following open source dependencies:
-
-**uuid v2.0.0** ([https://github.com/lukeed/uuid](https://github.com/lukeed/uuid))
-Copyright Luke Edwards <[luke.edwards05@gmail.com](mailto:luke.edwards05@gmail.com)> ([lukeed.com](https://lukeed.com/))
-License: MIT License, available here: [https://github.com/lukeed/uuid/blob/master/license](https://github.com/lukeed/uuid/blob/master/license)
-
-
-**dset v2.0.1** ([https://github.com/lukeed/dset](https://github.com/lukeed/dset))
-Copyright (c) Luke Edwards <[luke.edwards05@gmail.com](mailto:luke.edwards05@gmail.com)> ([lukeed.com](https://lukeed.com/))
-License: MIT License, available here: [https://github.com/lukeed/dset/blob/master/license](https://github.com/lukeed/dset/blob/master/license)
-
-**js-cookie v2.2.1**
-Copyright (c) 2018 Copyright 2018 Klaus Hartl, Fagner Brack, GitHub Contributors
- 	License: MIT License, available here: [https://github.com/js-cookie/js-cookie/blob/master/LICENSE](https://github.com/js-cookie/js-cookie/blob/master/LICENSE)
-
-**md5 v2.3.0** ([https://github.com/pvorb/node-md5](https://github.com/pvorb/node-md5))
-Copyright (c) 2011-2012, Paul Vorbach.
-Copyright (c) 2009, Jeff Mott.
-License: BSD-3-Clause “New” or “Revised” License, available at:
-[https://github.com/pvorb/node-md5/blob/master/LICENSE](https://github.com/pvorb/node-md5/blob/master/LICENSE)
-
-**unfetch v4.1.0** ([https://github.com/developit/unfetch](https://github.com/developit/unfetch))
-Copyright (c) 2017 Jason Miller
-License: MIT License, available at: [https://github.com/developit/unfetch/blob/master/LICENSE.md](https://github.com/developit/unfetch/blob/master/LICENSE.md)
+Analytics.js production dependencies are [listed under the **dependencies** key](https://github.com/segmentio/analytics-next/blob/master/packages/browser/package.json){:target="_blank”}.

src/connections/sources/catalog/libraries/website/javascript/index.md

@@ -200,7 +200,7 @@ Other libraries only collect `context.library`, any other context variables must
 | traits                   |              | ✅             | ✅                 |
 | userAgent                | ✅            |               | ✅                 |
 | userAgentData*           | ✅           |                |                    |
-| timezone                 |              | ✅             | ✅                 |
+| timezone                 | ✅            | ✅             | ✅                 |
 
 - IP Address isn't collected by Segment's libraries, but is instead filled in by Segment's servers when it receives a message for **client side events only**.
 > info "IPv6 Addresses are not Supported"