Merge pull request #300 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/_data/catalog/overrides.yml

@@ -1,6 +1,17 @@
 # This file is manually generated. When you add or remove an item, add or remove
 # it from the `overrides-list.yml` too.
 items:
+- slug: clevertap
+  id: 5711271880412f644ff13150
+  connection_modes:
+    device:
+      web: true
+      mobile: true
+      server: false
+    cloud:
+      web: true
+      mobile: true
+      server: true
 - slug: criteo-app-web-events
   id: 5787cc5180412f644ff14d7e
   connection_modes:
@@ -282,4 +293,4 @@ items:
     required: false
     label: >-
       Fallback to Zeroed IDFA when advertisingId key not present (Server-Side
-      Only)
+      Only)

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

@@ -1,12 +1,13 @@
 ---
 title: CleverTap Destination
 id: 5711271880412f644ff13150
+cmode-override: true
 ---
 ## Getting Started
 
 Once the Segment library is integrated, toggle CleverTap on in your Segment destinations, and add your CleverTap Account ID and CleverTap Account Token which you can find in the CleverTap Dashboard under Settings.
 
-You can integrate CleverTap using a server-side or mobile destination (iOS or Andriod). If you are interested in using CleverTap's push notifications or in-app notifications products, you should use the mobile destinations.
+You can integrate CleverTap using a server-side or mobile destination (iOS or Android). If you are interested in using CleverTap's push notifications or in-app notifications products, you should use the mobile destinations.
 
 All server-side destination requests require either a Segment Anonymous ID or a userId in the payload.
 
@@ -15,7 +16,7 @@ CleverTap supports the `identify`, `track`, `page` (server-side only), and `scre
 
 ## Identify
 
-When you identify a user, we'll pass that user's information to CleverTap with userId as CleverTap's Identity value. A number of Segment's special traits map to CleverTap's standard user profile fields.  You'll pass the key on the left into Segment and we will transform it to the key on the right before sending to CleverTap.
+When you identify a user, Segment passes that user's information to CleverTap with userId as CleverTap's Identity value. A number of Segment's special traits map to CleverTap's standard user profile fields.  You'll pass the key on the left into Segment and Segment transforms it to the key on the right before sending to CleverTap.
 
 - `name` maps to `Name`
 - `birthday` maps to `DOB`
@@ -24,28 +25,28 @@ When you identify a user, we'll pass that user's information to CleverTap with u
 - `phone` maps to `Phone`
 - `email` maps to `Email`
 
-All other traits will be sent to CleverTap as custom attributes. Please also note that the default logic will lower case and snake_case any user traits - custom or special - passed to CleverTap.
+All other traits will be sent to CleverTap as custom attributes. The default logic will lower case and snake_case any user traits - custom or special - passed to CleverTap.
 
 ## Track
 
-When you `track` an event, we will send that event to CleverTap as a custom event.  Note that CleverTap does not support arrays or nested objects for custom track event properties.
+When you `track` an event, Segment sends that event to CleverTap as a custom event.  Note that CleverTap does not support arrays or nested objects for custom track event properties.
 
 > note ""
 > CleverTap requires `identify` traits such as `userId` or `email` to record and associate the Track event. Without these traits, the Track event does not appear in CleverTap.
 
-Please also note that the default logic for our cloud mode connection to CleverTap will lower case and snake_case any event properties passed from Segment's servers to CleverTap. Our device mode connection will not lower case or snake_case any event properties passed directly to CleverTap from the client.
+The default logic for the cloud mode connection to CleverTap will lower case and snake_case any event properties passed from Segment's servers to CleverTap. The device mode connection will not lower case or snake_case any event properties passed directly to CleverTap from the client.
 
 ### Order Completed
 
-When you `track` an event using the server-side destination with the name `Order Completed` using the [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/), we will map that event to CleverTap's [Charged](https://support.clevertap.com/docs/working-with-events.html#recording-customer-purchases) event.
+When you `track` an event using the server-side destination with the name `Order Completed` using the [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/), Segment maps that event to CleverTap's [Charged](https://support.clevertap.com/docs/working-with-events.html#recording-customer-purchases){:target="_blank"} event.
 
 ## Page
 
-When you send a `page` event using the server-side destination, we will send that event to CleverTap as a Web Page Viewed event.
+When you send a `page` event using the server-side destination, Segment sends that event to CleverTap as a Web Page Viewed event.
 
 ## Screen
 
-When you send a `screen` event using the server-side destination or the iOS bundled SDK, we will send that event to CleverTap as an App Screen Viewed event.
+When you send a `screen` event using the server-side destination or the iOS bundled SDK, Segment sends that event to CleverTap as an App Screen Viewed event.
 
 ## Android
 
@@ -55,7 +56,7 @@ When you send a `screen` event using the server-side destination or the iOS bund
 
     `compile 'com.clevertap.android:clevertap-segment-android:+'`
 
-    **Note**: Our group Id is `com.clevertap.android`, not `com.segment.analytics.android.integrations`.
+    **Note**: The group Id is `com.clevertap.android`, not `com.segment.analytics.android.integrations`.
 
 2. Next, declare CleverTap's destination in your Analytics instance:
 
@@ -86,7 +87,7 @@ When you send a `screen` event using the server-side destination or the iOS bund
     </service>
     ```
 
-2. For more in-depth information, visit our [Android push integration documentation](https://developer.clevertap.com/docs/android).
+2. For more in-depth information, visit CleverTap's [Android push integration documentation](https://developer.clevertap.com/docs/android){:target="_blank"}.
 
 ### In-App Notifications
 
@@ -99,12 +100,12 @@ When you send a `screen` event using the server-side destination or the iOS bund
             android:theme="@android:style/Theme.Translucent.NoTitleBar" />
     ```
 
-    No further action is required to integrate in-app notifications, which are registered for and requested by default by our CleverTap Segment integration.
+    No further action is required to integrate in-app notifications, which are registered for and requested by default by the CleverTap Segment integration.
 
 
 ### Sample App
 
-CleverTap has created a sample Android application that integrates CleverTap using Segment. Check it out at the [GitHub repo](https://github.com/CleverTap/clevertap-segment-android-example).
+CleverTap has created a sample Android application that integrates CleverTap using Segment. Check it out at the [GitHub repository](https://github.com/CleverTap/clevertap-segment-android-example){:target="_blank"}.
 
 ## iOS
 
@@ -116,7 +117,7 @@ CleverTap has created a sample Android application that integrates CleverTap usi
    `pod 'Segment-CleverTap'`
    ```
 
-   We recommend using the latest version on [CocoaPods](https://cocoapods.org/pods/Segment-CleverTap) since it will contain the most up to date features and bug fixes.
+   Use the latest version on [CocoaPods](https://cocoapods.org/pods/Segment-CleverTap){:target="_blank"} since it will contain the most up to date features and bug fixes.
 
 2. Next, declare CleverTap's integration in your app delegate instance:
 
@@ -144,11 +145,11 @@ CleverTap has created a sample Android application that integrates CleverTap usi
 
 ### In-App Notifications
 
-No further action is required to integrate in-app notifications, which are registered for and requested by default by our CleverTap Segment integration.
+No further action is required to integrate in-app notifications, which are registered for and requested by default by the CleverTap Segment integration.
 
 ### Sample App
 
-CleverTap has created a sample iOS application that integrates CleverTap using Segment. Check it out at the [GitHub repo](https://github.com/CleverTap/clevertap-segment-ios/tree/master/Example).
+CleverTap has created a sample iOS application that integrates CleverTap using Segment. Check it out at the [GitHub repository](https://github.com/CleverTap/clevertap-segment-ios/tree/master/Example){:target="_blank"}.
 
 
 ## React Native

src/privacy/complying-with-the-gdpr.md

@@ -59,20 +59,9 @@ In addition to seeking independent legal advice regarding your obligations under
 
 ## Opting into the Data Processing Agreement and Standard Contractual Clauses
 
-Segment offers a Data Processing Agreement (DPA) and Standard Contractual Clauses (SCCs) as a means of meeting the regulatory contractual requirements of GDPR in our role as processor and also to address international data transfers.
+Segment offers a Data Processing Agreement (DPA) and Standard Contractual (SCCs) as a means of meeting contractual requirements of applicable data privacy laws and regulations, such as GDPR, and to address international data transfers. Segment’s online [Data Protection Addendum](https://www.twilio.com/legal/data-protection-addendum){:target="_blank"} (DPA) is already part of and incorporated into the [Terms of Service](https://www.twilio.com/legal/tos){:target="_blank"}. If you have a separate written agreement with Segment that does not include a Data Protection Addendum (DPA) or you would like to replace the existing Data Protection Addendum (DPA) that is attached to your separate written agreement with Segment’s latest Data Protection Addendum (DPA), please contact us at [[email protected]](mailto:[email protected]). 
+
+Segment offers a Data Processing Agreement (DPA) and Standard Contractual Clauses (SCCs) as a means of meeting the regulatory contractual requirements of GDPR in our role as processor and also to address international data transfers. 
 
 > note ""
 > **Note on Schrems II**: Despite the CJEU’s July 2020 ruling invalidating Privacy Shield as a means of validly transferring data to the USA from the EU, these developments are not expected to disrupt Segment’s ability to provide services to its EU customers as the European Court of Justice has reaffirmed that the Standard Contractual Clauses (SCC) remain valid as a method of transfer. Our standard Data Processing Agreement includes a provision whereby should Privacy Shield ever be invalidated (as is the case now) then the SCCs will automatically apply.
-
-To opt into the Data Processing Agreement and Standard Contractual Clauses:
-
-1.  Go to your [Workspace](https://app.segment.com).
-2.  Open the left side menu and select **Settings**.
-3.  Below **End User Privacy**, click **Privacy & Security.**
-4.  Below **Data Processing Agreement**, click **Review**.
-5.  Review and sign within Docusign.
-
-If you also wish to opt into the Standard Contractual Clauses:
-
-1.  Below **Standard Contractual Clauses**, click **Review**.
-2.  Review and sign within Docusign.

vale-styles/Vocab/Docs/accept.txt

@@ -7,6 +7,7 @@
 (?:L|l)ookback
 (?:P|p)ageviews?\b
 (?:P|p)endo
+(?:P|p)odfile
 (?:P|p)ostgres
 (?:R|r)emarketing
 (?:U|u)nlinks?\b