DOC-146 Data Res Update

Author: markzegarelli

src/_data/sidenav/strat.yml

@@ -1,7 +1,7 @@
 ---
 sections:
 - slug: adobe
-  section_title: Adobe Analytics
+  section_title: Adobe Integrations
   section:
   - path: /connections/destinations/catalog/adobe-analytics
     title: Adobe Analytics destination
@@ -15,6 +15,13 @@ sections:
     title: Adobe Analytics Heartbeat
   - path: /connections/destinations/catalog/adobe-analytics/best-practices
     title: Adobe Analytics best practices
+  - path: /connections/destinations/catalog/marketo-v2
+    title: Marketo destination
+  - path: /connections/destinations/catalog/marketo-static-lists
+    title: Marketo static lists destination (Personas)
+  - path: /connections/sources/catalog/cloud-apps/marketo
+    title: Marketo cloud source
+
 
 - slug: facebook
   section_title: Facebook Integrations
@@ -78,6 +85,7 @@ sections:
     title: Salesforce Marketing Cloud cloud source
 
 
+
 - slug: ajs
   section_title: Analytics.js Documentation
   section:

src/_includes/content/react-dest.md

@@ -0,0 +1,31 @@
+<!-- Usage: `include react-dest only={ios|android}` -->
+<!-- in the file we're pulling from the API, "name" corresponds with the path to the yml blob for a specific destination.-->
+{% assign currentSlug = page.url | split: "/" | last %}
+{% assign thisDest = site.data.catalog.destinations.items | where: "slug", currentSlug | first %}
+{% assign thisDestName = thisDest.display_name %}
+{% assign thisDestRNspecific = include.only %}
+
+
+{% if thisDestRNspecific %}
+<div class="premonition info">
+<div class="fa fa-info-circle"></div>
+<div class="content"><p>
+The {{thisDestName}} device-mode destination SDK is only available for {{thisDestRNspecific}} in React Native.
+</p></div></div>
+{%endif%}
+
+To add the {{thisDestName}} device-mode SDK to a [React Native](/docs/connections/sources/catalog/libraries/mobile/react-native/) project:
+1. Navigate to the root folder of your project, and run a `yarn add {{thisDestName | downcase | replace: " ", "-" }}{% if thisDestRNspecific %}-{{thisDestRNspecific}}{%endif%}` command to add the destination SDK to your project.
+2. Add an `import` statement to your project, as in the example below.
+   ```js
+   import {{thisDestName | replace: " ", "" }} from '@segment/analytics-react-native-{{thisDestName | downcase | replace: " ", "" }}{% if thisDestRNspecific %}-{{thisDestRNspecific}}{%endif%}'
+   ```
+3. In the same project file, add the destination to the `using` list in the `await` command.
+   ```js
+   await analytics.setup('YOUR_WRITE_KEY', {
+     // Add any of your Device-mode destinations. This ensures they load before continuing.
+     using: {{thisDestName | replace: " ", "" }}
+     // ...
+   })
+   ```
+4. Finally, change to your iOS development folder ( `cd ios` ) and run `pod install`.

src/_sass/components/_stage.scss

@@ -21,5 +21,6 @@
   &__body {
     flex: 1;
     max-width: 100%;
+    min-width: 0;
   }
 }

src/connections/data-residency.md

@@ -1,26 +1,170 @@
 ---
 title: Data Residency
+beta: true
 ---
 Segment offers customers the option to mitigate risk 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.
 
-## Agree to Terms
+## Enable Local Data Ingest and Storage
+
+This feature is in Public Preview. You can enable Local Data Ingest and Storage from the Regional Settings tab within your Workspace settings. Enabling the feature here makes the feature available to both client-side and server-side sources.
+
+![enable](images/enable-regional-ingest.png)
+
+## Local Data Ingest
+
+Local Data Ingest enables you to send data to Segment from both Client-side and Server-side sources through locally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions.
+
+### Client-side sources
+
+You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Ingest Region in that source's settings.
+
+![ingest region](images/regional-ingest.png)
+
+All regions are configured on a **per-source** basis. You'll need to configure the region for each source separately if you do not want to use the default region (Oregon). All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app is reloaded. You do not need to change code when you switch regions.
+
+### Server-side and project sources
+
+When you send data from a server-side or project source, you can use the `host` configuration parameter to send data to the desired region:
+
+1. Oregon (Default) — `api.segment.io/v1`
+2. Dublin — `in.eu2.segmentapis.com/v1`
+3. Singapore — `in.ap1.segmentapis.com/v1`
+4. Sydney — `in.au1.segmentapis.com/v1`
+
+## Local Data Storage
+
+Local Data Storage allows you to preserve your raw events in Amazon S3 buckets hosted regionally. These buckets are hosted by you, in your desired region.
 
 > note ""
-> This feature is in Public Preview.
+> Configure Local Data Storage on new sources instead of enabling on an existing source to avoid deletion of historical data and a change in retention policy. Historical data that is expired due to a retention policy cannot be replayed at a time in the future. Historical data cannot migrate from the US to your regional buckets.
+
+### Pre-requisites
+
+To begin with Local Data Storage, complete the following steps in your AWS account:
+
+1. Create an S3 bucket in the preferred region
+2. Create a folder named `segment-logs` in the new bucket
+3. Edit the bucket policy to allow Segment access to the S3 bucket
+   ```json
+    {
+      "Version": "2008-10-17",
+      "Id": "Policy1425281770533",
+      "Statement": [
+          {
+            "Sid": "AllowSegmentUser",
+            "Effect": "Allow",
+            "Principal": {
+                    "AWS": "arn:aws:iam::107630771604:user/s3-copy"
+            },
+            "Action": "s3:PutObject",
+            "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME/segment-logs/*"
+          }
+      ]
+    }
+   ```
+  **Note**: `Resource` property string must end with `/*`.
+
+    Segment requires this access to write raw data to your regionally hosted S3 bucket. Specifically, this allows Segment to use `s3:PutObject`. To enable encryption at rest, use the default S3 mechanism. If you have server-side encryption enabled with AWS KMS managed keys, see the additional [required configuration step](/docs/connections/storage/catalog/amazon-s3/#encryption). To edit the bucket policy, right-click the bucket name in the AWS management console, and select **Edit policy**.
+
+4. Create a new IAM role in your AWS account with a trust relationship to the role which allows Segment to use the Segment `workspace_id` as `externalID`.
+   ```json
+  {
+    "Version": "2012-10-17",
+    "Statement": [
+      {
+        "Sid": "",
+        "Effect": "Allow",
+        "Principal": {
+          "AWS": [
+            "arn:aws:iam::294048959147:role/segment-regional-archives-production"
+          "arn:aws:iam::294048959147:role/warehouse-replays" 
+          ]
+        },
+        "Action": "sts:AssumeRole",
+        "Condition": {
+          "StringEquals": {
+            "sts:ExternalId": [
+              "YOUR_WORKSPACE_ID"
+            ]
+          }
+        }
+      }
+    ]
+  }
+  ```
+5. Attach this IAM policy to the role defined in Step 4.
+   ```json
+  {
+    "Version": "2012-10-17",
+    "Statement": [
+      {
+        "Sid": "ListObjectsInBucket",
+        "Effect": "Allow",
+        "Action": "s3:ListBucket",
+        "Resource": [
+          "arn:aws:s3:::YOUR_BUCKET_NAME/*",
+          "arn:aws:s3:::YOUR_BUCKET_NAME"
+        ]
+      },
+      {
+        "Sid": "AllObjectActions",
+        "Effect": "Allow",
+        "Action": "s3:*Object*",
+        "Resource": [
+          "arn:aws:s3:::YOUR_BUCKET_NAME/*",
+          "arn:aws:s3:::YOUR_BUCKET_NAME"
+        ]
+      },
+      {
+          "Sid": "AllowKMS",
+          "Effect": "Allow",
+          "Action": "kms:GenerateDataKey",
+          "Resource": "*"
+      }
+    ]
+  }
+  ```
+
+> note ""
+> This access allows Segment to run local deletions jobs from regionally hosted data for a given user ID.
+
+### Local Data Storage configuration
+
+After you configure the policy and roles, as defined above, navigate to the Settings tab of the source for which you want to store data regionally.
+
+![local storage](images/regional-data-source.png)
+
+To complete the configuration of Local Data Storage:
+
+1. Enter the name of the S3 Bucket you created in the Pre-requisites section
+2. Add a regional label to help locate the bucket from AWS at a later date. For example, `us-west2-294048959147` or `country-REGION-AWS_ACCOUNT`
+3. Enter the ARN of the IAM role set up as a pre-requisite and click **Save**
+4. Navigate to *Privacy > Settings > Data Retention*
+5. Identify the Source in the source-level archive retention periods list
+6. Set the Retention for this source to the suggested value of `7 days` and click **Save**
+
+The Local Data Storage bucket will take roughly one hour to receive data.
 
-Before you can enable Regional Data Ingest and Storage on your workspace, you must read and agree to the [First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/) and [Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/).
+### Deletion from Local Data Storage
 
-Once agreed to, click **Accept Terms** to enable the feature on your active workspace.
+Local Data Storage offers the same ability to delete end-user data when they revoke or alter their consent to have data collected, as long as they can be identified by a `userId`. For example, if an end-user invokes their Right to Object or Right to Erasure under the GDPR or CCPA, you can use these features to:
+- block ongoing data collection for that user
+- delete all historical data about them from Segment's systems, connected S3 buckets and warehouses, and supported downstream partners
 
-![](images/enable-regaional-ingest.png)
+Contact [Segment Support](https://segment.com/help/contact/) to initiate a deletion and provide a valid `userId` for each user to be deleted. Deletion requests are run within the region, and have a 30 day SLA, but requires that the raw data is accessible to Segment in an unaltered state. Deletion from Local Data Storage is not available from the [Privacy Portal](/docs/privacy/user-deletion-and-suppression/#deletion-requests) or through the API.
 
-## Enable Regional Data Ingest
+> note "Business Plan Customers"
+> If you use this feature to delete data, you cannot Replay the deleted data at the same time. For standard Replay requests, you must wait for any pending deletions to complete. You cannot submit new deletions requests for the period of time that Segment replays data for you.
 
-Regional Data Ingest enables you to send data to segment from either Client-side or Server-side sources, through locally hosted API ingest points. The regional infrastructure has the capability to fail-over across locations within the region, but will not cross regions.
+### Replays from Local Data Storage
 
-### Client-side Sources
+Local Data Storage supports [Replays](/docs/guides/what-is-replay/#replays-for-tooling-changes) to both existing and new tools. To request a Replay, [contact Segment](https://segment.com/help/contact/) with the following:
+- Source ID
+- Date Range
+- Destination
 
-You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host by selecting the ingest region on a per-source basis.
+Segment will initiate Replay jobs and update status as they progress.
 
-![](images/regional-ingest.png)
+### Debugging and support
 
+The Segment Customer Success and Support Engineering teams do not have access to customer hosted regional buckets used for Local Data Storage and cannot provide event level debug support.

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

@@ -106,6 +106,10 @@ analytics = new Analytics.Builder(this, "write_key")
 
 After you build and release to the App Store, Segment automatically starts translating and sending your data to Adjust.
 
+### React Native
+
+{% include content/react-dest.md %}
+
 ### Server
 
 Our Cloud-mode integration allows you to send *supplemental* data to Adjust.  This, however, *does not* include attribution events. If you are relying on the Adjust server-side component, and you are not bundling the Segment-Adjust SDK, your installs will not be attributed. E-commerce events and other general `track` events are supported out of the box. You **must** map your `track` events to your custom Adjust Event Token in your [Adjust destination settings](#map-your-events-to-custom-adjust-event-tokens).

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

@@ -43,6 +43,10 @@ In addition to the docs below, Amplitude created a [integration guide](https://d
 
 If you included Segment's Javascript snippet on your page, then Amplitude's SDK loads on your page automatically and you can use Segment's to begin sending events right away.
 
+### React Native device mode set up
+
+{% include content/react-dest.md %}
+
 
 ## Page and Screen
 
@@ -446,7 +450,7 @@ with the user's `userId`, or what Amplitude refers to, respectively, as a
 
 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.
 
-> note ""  
+> note ""
 > To use Alias, you must have the Amplitude Portfolio add-on enabled.
 
 For more information, see the [Segment Spec page for the Alias method](https://segment.com/docs/connections/spec/alias/) and [the Amplitude `usermap` documentation](https://amplitude.zendesk.com/hc/en-us/articles/360002750712-Portfolio-Cross-Project-Analysis#user-mapping-aliasing).

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

@@ -54,6 +54,10 @@ If you have the **Can Omit AppsFlyerID** setting enabled, but aren't sending an
 
 To prevent this, you can enable the new **Fallback to send IDFV when advertisingId key not present** setting in your AppsFlyer destination settings. With this enabled, when you send data using cloud-mode (through the Segment servers), Segment sends the user's IDFV (the `device.id`) when `device.advertisingId` is missing or blank AND “Can Omit AppsFlyerID” is enabled.
 
+#### Additional React Native device-mode set up
+
+{% include content/react-dest.md %}
+
 ### Server
 
 AppsFlyer offers an **augmentative** server-side [HTTP API](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-) intended for use along side the AppsFlyer mobile SDK. Use the cloud-mode destination _with_ the mobile SDK to link out-of-app events (such as website or offline purchases) with attributed users and devices.

src/connections/destinations/catalog/branch-metrics/index.md

@@ -31,6 +31,28 @@ This document was last updated on November 13, 2019. If you notice any gaps, out
   5. Paste the Branch Key in the destination settings and click **Save**.
 
 
+### Adding Branch device-mode SDKs for React Native
+
+<!-- LR, Mar2021: this should be a `react-dest` include but Branch changed their name from Branch-Metrics-->
+
+To add the Branch device-mode SDK to a [React Native](/docs/connections/sources/catalog/libraries/mobile/react-native/) project:
+1. Navigate to the root folder of your project, and run a `yarn add branch` command to add the destination SDK to your project.
+2. Add an `import` statement to your project, as in the example below.
+   ```js
+   import Branch from '@segment/analytics-react-native-branch'
+   ```
+3. In the same project file, add the destination to the `using` list in the `await` command.
+   ```js
+   await analytics.setup('YOUR_WRITE_KEY', {
+     // Add any of your Device-mode destinations. This ensures they load before continuing.
+     using: Branch
+     // ...
+   })
+   ```
+4. Finally, change to your iOS development folder ( `cd ios` ) and run `pod install`.
+
+
+
 ## Identify
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example iOS call would look like: