Merge pull request #2818 from segmentio/develop

rchinn1 · web-flow · commit 13e00e2a0946 · 2022-04-28T09:36:05.000-07:00
Release 22.17.2
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -1,13 +1,11 @@
 * @segmentio/segment-doc-team
 # The default owners for everything in
 # the repo. Unless a later match takes precedence.
-CODEOWNERS  @segmentio/segment-doc-team @markzegarelli
+CODEOWNERS  @segmentio/segment-doc-team 
 
-# Diagram library
-# /diagram-library @markzegarelli
 
 # Utility scripts
-# /scripts @segmentio/segment-doc-team
+/scripts @segmentio/segment-doc-team
 
 # Vale Linting
 # /vale-styles @segmentio/segment-doc-team
@@ -23,28 +21,20 @@ CODEOWNERS  @segmentio/segment-doc-team @markzegarelli
 
 
 # Libraries owners
-# /src/connections/catalog/libraries   @bsneed @pooyaj @juliofarah
-
-# Destinations owners
-# /src/connections/destinations  @segmentio/segment-doc-team
-
-
-# Privacy owners TODO
-# /src/privacy
+/src/connections/catalog/libraries @stayseesong @markzegarelli
 
 
-# Protocols owners TODO
-# /src/protocols
-
-# Partner Program owners
-# /src/partners  @misteryeo @n2parko @benhorowitz
-
-# Personas owners TODO
+# Destinations owners
+/src/connections/destinations  @stayseesong @markzegarelli
 
-# Usage & Billing TODO
+# Engage
+/src/engage/ @markzegarelli @pwseg @rchinn-segment
 
-# Config API TODO
+# Personas owners 
+/src/personas @pwseg @rchinn-segent
 
-# Segment App TODO
+# Protocols owners
+/src/protocols @forstisabella
 
-# Guides TODO
+# Storage owners
+/src/connections/storage @forstisabella
diff --git a/src/_data/catalog/overrides.yml b/src/_data/catalog/overrides.yml
@@ -1,6 +1,18 @@
 # This file is manually generated. When you add or remove an item, add or remove
 # it from the `overrides-list.yml` too.
 items:
+- slug: drip
+  id: 54521fd525e721e32a72eeaa
+  connection_modes:
+    device:
+      web: true
+      mobile: true
+      server: false
+    cloud:
+      web: false
+      mobile: true
+      server: true
+
 - slug: clevertap
   id: 5711271880412f644ff13150
   connection_modes:
diff --git a/src/connections/destinations/catalog/drip/index.md b/src/connections/destinations/catalog/drip/index.md
@@ -1,8 +1,9 @@
 ---
 title: Drip Destination
 id: 54521fd525e721e32a72eeaa
+cmode-override: true
 ---
-Our Drip destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-drip),(iOS and Android work using the server destination).
+The Drip destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-drip),(iOS and Android work using the server destination).
 
 ## Getting Started
 
@@ -11,11 +12,11 @@ When you enable Drip in the Segment web app, your changes appear in the Segment
 
 ## Identify
 
-When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we call [`identify`](/docs/connections/spec/identify/) on Drip and pass through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you've enabled it in the Drip UI, you'll need to pass `email` as a trait on the identify call on both domains.
+When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, Segment calls [`identify`](/docs/connections/spec/identify/) on Drip and passes through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you've enabled it in the Drip UI, you'll need to pass `email` as a trait on the identify call on both domains.
 
 ## Track
 
-When you call [`track`](/docs/connections/spec/track/), we'll send the event to Drip with the event `name` and all `properties` that you specified. If you include `revenue` as a property, it will get passed to Drip as the conversion value of this event.
+When you call [`track`](/docs/connections/spec/track/), Segment sends the event to Drip with the event `name` and all `properties` that you specified. If you include `revenue` as a property, it will get passed to Drip as the conversion value of this event.
 
 **Note:**
 - If you are sending custom server side events, you must include an `email` property of the user that the event belongs to.
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md
@@ -8,7 +8,7 @@ id: 9EMcTqiKok
 With Analytics-Kotlin, you can send data using Kotlin applications to any analytics or marketing tool without having to learn, test, or implement a new API every time. Analytics-Kotlin enables you to process and track the history of a payload, while Segment controls the API and prevents unintended operations.
 
 > info ""
-> Segment supports [these destinations](#supported-destinations) with more to come. If you don't see your destination, you can [build your own](#build-your-own-destination).
+> Segment supports [these destinations](#supported-destinations) in device-mode, with more to follow. Cloud-mode destinations are also supported. If you don't see your destination, you can [build your own](#build-your-own-destination).
 
 > success ""
 > You can choose to set up your Analytics Kotlin source on [mobile](/docs/connections/sources/catalog/libraries/mobile/kotlin-android) or on the [server](/docs/connections/sources/catalog/libraries/server/kotlin). Segment doesn't support device-mode destinations on the server-side.
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/index.md b/src/connections/sources/catalog/libraries/mobile/react-native/index.md
@@ -492,7 +492,7 @@ These are the example plugins you can use and alter to meet your tracking needs:
 | IDFA                | `@segment/analytics-react-native-plugin-idfa`                |
 
 ## Supported Destinations
-Segment supports these destinations for Analytics React Native 2.0 with more to come:
+Segment supports these destinations for Analytics React Native 2.0 in device-mode, with more to follow. Cloud-mode destinations are also supported:
 - [Adjust](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-adjust){:target="_blank"}
 - [Amplitude Session](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-amplitude-session){:target="_blank"}
 - [Appsflyer](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-appsflyer){:target="_blank"}
diff --git a/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md b/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md
@@ -10,7 +10,7 @@ With Analytics-Swift, you can send data from iOS, tvOS, iPadOS, WatchOS, macOS a
 If you're migrating to Analytics-Swift from a different mobile library, you can skip to the [migration guide](/docs/connections/sources/catalog/libraries/mobile/swift-ios/migration/).
 
 > info ""
-> Analytics-Swift currently supports [these destinations](#supported-destinations), with more to follow.
+> Analytics-Swift currently supports [these destinations](#supported-destinations) in device-mode, with more to follow. Cloud-mode destinations are also supported.
 
 
 ## Getting Started
diff --git a/src/engage/profiles/csv-upload.md b/src/engage/profiles/csv-upload.md
@@ -20,11 +20,11 @@ Click **Download Template** to download a CSV template with identifier columns f
 > info ""
 > CSV files can only have a single **email** and **phone** identifier column. Include any additional email addresses or phone numbers for a user profile as a separate row.
 
-Navigate to **Personas > Settings** and select the Identity Resolution tab to view or add identifiers in your Segment workspace.
+Navigate to **Personas > Settings** and select the **Identity Resolution** tab to view or add identifiers in your Segment workspace.
 
 ### 2. Upload a CSV file
 
-Upload a CSV file to Twilio Engage two ways:
+Upload a CSV file to Twilio Engage in two ways:
 - Drag and drop the CSV file in the dropzone.
 - Click **Browse** to locate the CSV file.
 
@@ -88,6 +88,11 @@ Please note the following limits as you upload CSV files to Twilio Engage:
 - You can only upload one file at a time.
 - The CSV file size can't exceed 15 MB.
 
+> warning ""
+> At this time, the following beta limitations apply:
+> - Email addresses and phone numbers that unsubscribe from your campaigns can't be re-subscribed.
+> - If you upload the same email or phone number with different subscription states in a CSV file, the resulting subscription status isn't guaranteed.
+
 ## Message consent
 
 Only send messages to subscribed users. If a recipient deletes or flags an unwanted message as spam, inbox providers might start to filter your messages straight to spam folders. View more SendGrid delivery [Best Practices](https://sendgrid.com/blog/why-are-my-emails-going-to-spam/){:target="_blank"} to prevent email from going to spam.
diff --git a/src/guides/usage-and-billing/billing.md b/src/guides/usage-and-billing/billing.md
@@ -6,7 +6,7 @@ title: Billing and Account FAQs
 
 On the Segment monthly Team plan, your billing cycle starts the day after your 14-day trial ends. You're billed on this day for each month while you're on this plan. 
 
-On the Segment annual Team plan, you're billed at the end of your 14-day trial for the amount of an entire year of service including a specific number of [MTUs](docs/guides/usage-and-billing/mtus-and-throughput#what-is-an-mtu). Annual plan subscribers are billed for MTU overages at the end of each monthly cycle.
+On the Segment annual Team plan, you're billed at the end of your 14-day trial for the amount of an entire year of service including a specific number of [MTUs](/docs/guides/usage-and-billing/mtus-and-throughput#what-is-an-mtu). Annual plan subscribers are billed for MTU overages at the end of each monthly cycle.
 
 
 ## How do I change my plan?
diff --git a/src/partners/streams.md b/src/partners/streams.md
@@ -90,7 +90,7 @@ If you want to batch requests to the HTTP endpoint, refer to the batching docume
 ## Regional Segment
 Segment offers customers the option to lead on data residency by providing regional infrastructure in both the Europe and the United States.
 
-Segment recommends you enable the user to the Segment [endpoint](/docs/guides/regional-segment/#server-side-and-project-sources) to send data to for the given writeKey.
+Segment recommends you enable the user to choose which Segment [endpoint](/docs/guides/regional-segment/#server-side-and-project-sources) to send data to for the given writeKey from your system.
 
 # Process
 
diff --git a/src/personas/audiences/index.md b/src/personas/audiences/index.md
@@ -106,7 +106,10 @@ To edit a realtime Trait or Audience, follow these steps:
 3. Select the **Builder** tab and make your edits.
 4. Select **Save Audience** to confirm your edits.
 
-Personas then processes your realtime Audience or Trait edits.  Once Personas has finished incorporating your changes, you'll be able to access your updated Audience or Trait.
+Personas then processes your realtime Audience or Trait edits. While the edit task runs, the audience remains locked and you can't make further changes. Once Personas has finished incorporating your changes, you'll be able to access your updated Audience or Trait.
+
+> warning ""
+> If your audience includes historical data (Historical Backfill is enabled), editing an audience creates a new backfill task. The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Personas can backfill. View a list of [rate-limited destinations](/docs/personas/using-personas-data/#rate-limits-on-personas-event-destinations).
 
 ## Accessing your Audiences using the Profiles API
 
