Merge branch 'develop' of github.com:segmentio/segment-docs into develop

markzegarelli · markzegarelli · commit afb183ca2173 · 2023-01-17T10:27:37.000-08:00
diff --git a/.github/styles/segment/exclamation.yml b/.github/styles/segment/exclamation.yml
@@ -1,6 +1,8 @@
-extends: substitution
-message: "Please use '%s' instead of '%s'."
-link: https://docs.microsoft.com/en-us/style-guide/punctuation/exclamation-points
-level: warning
-swap:
-    '\w!\s': '\.'
+extends: existence
+message: "Don't use exclamation points in text."
+nonword: true
+level: error
+action:
+  name: remove
+tokens:
+  - '\w!(?:\s|$)'
diff --git a/.github/styles/segment/links copy.yml b/.github/styles/segment/links copy.yml
diff --git a/.github/styles/segment/links.yml b/.github/styles/segment/links.yml
@@ -3,4 +3,4 @@ message: "Write meaningful link text."
 link: https://docs.microsoft.com/en-us/style-guide/urls-web-addresses
 level: warning
 raw:
-  - '\[?here\]\('
+  - '\[?here\]\(.*'
diff --git a/.github/styles/segment/relative-url.yml b/.github/styles/segment/relative-url.yml
@@ -1,6 +1,6 @@
 extends: existence
-message: 'Link to Segment docs "%s" must be relative.'
+message: 'Link to Segment docs "%s" should be relative.'
 level: warning
 scope: raw
 raw:
-  - '\[.+\]\(https://(www.)?segment.com/docs.*\)'
+  - '(segment.com\/docs.[^)]*)'
diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml
@@ -43,6 +43,8 @@ sections:
     title: Replay
   - path: /guides/regional-segment
     title: Regional Segment
+  - path: /guides/audiences-and-journeys
+    title: Audiences and Journeys
 
   - section_title: How-to Guides
     slug: guides/how-to-guides
diff --git a/src/api/public-api/index.md b/src/api/public-api/index.md
@@ -24,4 +24,25 @@ The Public API includes the following benefits over the Config API:
 | Improved architecture   | The Public API is built with improved security, checks for authentication, authorization, input validation, HTTPS exposed services, auto-scaling, and more in mind. |
 | Cleaner mapping         | The Public API uses unique IDs for reference, in place of slugs in the Config API. Unique IDs are, by design, unique.                                               |
 | Available in Europe     | The Public API is accessible to both US and EU-based workspaces.                                                                                                                                                                   |
-| Increased reliability   | The Public API features more stable endpoints, and a 99.8% success rate                                                                                             |
+| Increased reliability   | The Public API features more stable endpoints, and a 99.8% success rate                                                                                             |
+
+## API Token Security
+
+To enhance API token security, Segment partners with GitHub to prevent fraudulent use of exposed API tokens found in public git repositories. This helps to prevent malicious actors from using exposed tokens to perform unauthorized actions in your Segment workspace. 
+
+Within seconds, GitHub scans each commit in public repositories for Public API tokens, and sends detected tokens to Segment. Valid tokens are automatically revoked and workspace owners are notified. 
+
+Learn more about [GitHub's secret scanning program](https://docs.github.com/en/developers/overview/secret-scanning-partner-program){:target="_blank"}.
+
+### Frequently Asked Questions
+#### What should I do if I see a notification that my token was exposed?
+In most cases, identifying and revoking an exposed token takes seconds. Segment recommends you check the [audit trail](/docs/segment-app/iam/audit-trail/) to ensure no unauthorized actions were taken with the token.
+
+#### How did my token get exposed?
+Developers can accidentally commit tokens to public repositories, exposing them to the public. This can happen when developers use a token in a local development environment and forget to remove it before committing their code.
+
+#### Why are exposed tokens automatically revoked?
+By automatically revoking the exposed token, Segment helps keep your workspace secure and prevents potential abuse of the token.
+
+#### How do I enable this feature?
+This feature is automatically enabled for all workspaces on Team or Business tier plans.
diff --git a/src/connections/destinations/catalog/clearbit-reveal/index.md b/src/connections/destinations/catalog/clearbit-reveal/index.md
@@ -22,6 +22,8 @@ Setup within Clearbit:
 
 To verify that the destination has been set up correctly, send a page event **that includes an IP address**, check the Debugger section of your Segment Source. Assuming everything is as it should be, you should start seeing Clearbit Reveal data populate in an `identify` event – click on the specific event you're interested in to see Clearbit Reveal traits. These traits will now be available to other Segment destinations in your account. Notice that all Clearbit Reveal traits are prefixed with `reveal_` to ensure they don't conflict with existing traits. Clearbit will also send a `track` event for 'enrichment_provider'.
 
+When you make requests to Clearbit, Clearbit send events with its own data back to your Segment source server-side using Segment's analytics-ruby library. If you see unexpected traffic from analytics-ruby in your Debugger, that traffic represents the events that Clearbit sends back.
+
 
 ## Page
 
diff --git a/src/connections/destinations/catalog/customer-io/index.md b/src/connections/destinations/catalog/customer-io/index.md
@@ -5,6 +5,7 @@ redirect_from: "/connections/destinations/catalog/customer.io/"
 hide-personas-partial: true
 maintenance: true
 id: 54521fd525e721e32a72eea8
+actions-slug: "customer-io-actions"
 ---
 [Customer.io](https://customer.io/) helps you send automated email, push, SMS, and webhooks based on your customers' activities in your app or product. It makes conversion tracking, optimization and re-marketing easier. The `analytics.js` Customer.io Destination is open-source. You can browse the code [on GitHub](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/customerio).
 
diff --git a/src/connections/destinations/catalog/posthog/index.md b/src/connections/destinations/catalog/posthog/index.md
@@ -3,9 +3,9 @@ title: PostHog Destination
 rewrite: true
 id: 5ece242d61055a0b1bb2e103
 ---
-[PostHog](https://posthog.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is self-hosted, open-source analytics product. Get the same powerful features as other product analytics software but keep full control over your data.
+[PostHog](https://posthog.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is a self-hosted, open-source analytics product. Get the same powerful features as other product analytics software but keep full control over your data.
 
-This destination is maintained by PostHog. For any issues with the destination, [contact the PostHog Support team](mailto:hey@posthog.com).
+This destination is maintained by PostHog. For any issues with the destination, check out the [PostHog users slack](https://posthog.com/slack){:target="_blank"} or [contact the PostHog Support team](mailto:hey@posthog.com).
 
 ## Getting Started
 
@@ -14,11 +14,12 @@ This destination is maintained by PostHog. For any issues with the destination,
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for "PostHog" in the Destinations Catalog, and select the PostHog destination.
 3. Choose which Source should send data to the PostHog destination.
-4. Go to your [PostHog set up page](https://app.posthog.com/setup), and find and copy the **API key**.
+4. Go to your [PostHog set up page](https://app.posthog.com/setup){:target="_blank"}, and copy the **API key**.
 5. Enter the PostHog API Key that you copied in the PostHog destination settings in Segment.
-
-> note ""
-> **Note**: If you're hosting your own PostHog instance, add the URL of your instance without the trailing slash in the **PostHog instance** setting. For example, `https://posthog-example.herokuapp.com`
+6. Enter your PostHog instance URL as the address to your instance **without any trailing slash**, for example:
+  - `https://app.posthog.com` if you use PostHog Cloud US
+  - `https://eu.posthog.com` if you use PostHog Cloud EU
+  - `https://posthog-example.herokuapp.com` if you self-host on Heroku
 
 ## Page
 
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/index.md b/src/connections/sources/catalog/libraries/mobile/react-native/index.md
@@ -595,7 +595,19 @@ No, only the plugins listed above are supported in device-mode for Analytics Rea
 ### Will I still see device-mode integrations listed as `false` in the integrations object?
 When you successfully package a plugin in device-mode, you won't see the integration listed as `false` in the integrations object for a Segment event. This logic is packaged in the event metadata, and isn't surfaced in the Segment debugger.
 ### Why are my IDs not set in UUID format?
-Due to [limitations](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/uuid.ts#L5){:target="_blank"} with the React Native bridge, Segment doesn't use UUID format for `anonymousId`s and `messageId`s in local development. These IDs will be set in UUID format for your live app.  
+Due to [limitations](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/uuid.ts#L5){:target="_blank"} with the React Native bridge, Segment doesn't use UUID format for `anonymousId` and `messageId` values in local development. These IDs will be set in UUID format for your live app.
+### How do I set a distinct writeKey for iOS and android?
+You can set different writeKeys for iOS and Android. This is helpful if you want to send data to different destinations based on the client side platform. To set different writeKeys, you can dynamically set the writeKey when you initialize the Segment client:
 
+```js
+import {Platform} from 'react-native';
+import { createClient } from '@segment/analytics-react-native';
+
+const segmentWriteKey = Platform.iOS ? 'ios-writekey' : 'android-writekey';
+
+const segmentClient = createClient({
+  writeKey: segmentWriteKey
+});
+```
 ## Changelog
 [View the Analytics React Native 2.0 changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.
diff --git a/src/guides/audiences-and-journeys.md b/src/guides/audiences-and-journeys.md
@@ -0,0 +1,76 @@
+---
+title: Audiences and Journeys
+plan: engage-foundations
+---
+
+Audiences and Journeys are fundamental to [Twilio Engage](/docs/engage/). Both let you segment your users, send them personalized content, and show them ads from platforms like Facebook or Google.
+
+In this guide, you’ll learn how to choose between an Audience and a Journey for a number of marketing use cases across the customer lifecycle.
+
+## Back to basics
+
+First, consider the following definitions for an Audience and a Journey.
+
+### Audience
+
+In Engage, an [Audience](/docs/engage/audiences/) is a group of users that share certain characteristics. When you create an Audience, you group users who meet certain conditions, like having performed an event or having a [Computed Trait](/docs/engage/audiences/computed-traits/).
+
+Once you’ve created an Audience, you can sync it to [marketing automation tools](/docs/connections/destinations/catalog/#marketing-automation), [ads platforms](/docs/connections/destinations/catalog/#advertising), [analytics tools](/docs/connections/destinations/catalog/#analytics), or [data warehouses](/docs/connections/storage/warehouses/). Depending on the Audience’s conditions and [connected Destination(s)](/docs/connections/destinations/), Segment syncs the Audience’s users in batches or in real time, as they meet the Audience’s conditions.
+
+### Journey
+
+A [Journey](/docs/engage/journeys/) is a logic-driven workflow that progresses users through steps based on conditions and time delays. You add users to a Journey with an entry condition, then users progress through [the Journey’s steps](/docs/engage/journeys/step-types/) based on conditions you define during Journey setup.
+
+As with Audiences, Segment can sync users to Destinations at designated points in the Journey. Unlike an Audience, a Journey can send users to Twilio Engage’s [native email and SMS channels](/docs/engage/campaigns/).
+
+## Engage and the customer lifecycle
+
+The customer lifecycle provides a helpful framework for thinking about Audiences and Journeys.
+
+![A flow chart of the digital marketing lifecyle](images/digital_marketing_lifecyle.png "Digital Marketing Lifecycle Funnel")
+
+Engage Audiences tend to be most effective at the top of the customer lifecycle funnel, where brand awareness and discovery occurs.
+
+A Journey becomes a better option as customers progress down the funnel, where a more complex strategy involving messaging, social ads, and newsletters helps move customers closer to conversion.
+
+## Choosing between an Audience and a Journey
+
+With the customer lifecycle in mind, use the following table as a starting point for selecting an Audience or Journey for common marketing use cases:
+
+| Use Case                                        | Audience or Journey |
+| ----------------------------------------------- | ------------------- |
+| I want to send email and SMS campaigns.         | Journey             |
+| I only have one intended touchpoint.            | Audience            |
+| I need branching logic.                         | Journey             |
+| I want to run A/B tests.                        | Journey             |
+| I want to re-target customers with the same ad. | Audience            |
+
+While these suggestions will work for most use cases, you may need to consider other factors before you implement your own campaign. Asking the following questions will help you identify the right approach.
+
+### Over the course of a campaign, how many touchpoints do I want to create?
+
+Audiences work best for single, one-off messages or touchpoints. If you need a campaign with time delays and branching logic, opt for a Journey.
+
+For example, an Audience works well if you want to show a single ad when a user abandons a cart. If, however, you want to show an ad, wait several days, then send the user an email if they’ve not completed their purchase, go with a Journey.
+
+### Do I want to use Engage Premier Channels like SMS and email?
+
+All messaging through [Engage Premier Channels](/docs/engage/#market-to-customers-with-engage-premier-and-channels) takes place in Journeys. If you’d like to send an SMS or email campaign to a customer, use a Journey.
+
+### Do I need branching logic?
+
+Create a Journey if you want to incorporate branching logic into your campaign.
+
+### Do I want to conduct an A/B test or create a holdout group?
+
+A number of Journeys step types, like [randomized splits](/docs/engage/journeys/step-types/#randomized-splits), let you run experiments and test your campaigns. If you want to experiment with different groups, use a Journey.
+
+### Do I want my customers to receive the same campaign more than once?
+
+With Journeys, you can allow customers to [re-enter a Journey they’ve exited](/docs/engage/journeys/build-journey/#exit-and-re-entry-times) or restrict them to a one-time Journey.
+
+Audiences, on the other hand, admit users whenever they meet the Audience’s criteria. For example, you may want to retarget a user with an ad whenever they view a page on your website. In this case, an Audience works well since the user can re-enter the Audience regardless of how many times they’ve already done so.
+
+## Putting it together
+
+With this guidance in mind, take your next steps with Engage by learning [how to build a Journey](/docs/engage/journeys/build-journey/) and [work with Engage Audiences](/docs/engage/audiences/).
diff --git a/src/guides/images/digital_marketing_lifecyle.png b/src/guides/images/digital_marketing_lifecyle.png
diff --git a/src/protocols/apis-and-extensions/typewriter.md b/src/protocols/apis-and-extensions/typewriter.md
@@ -51,9 +51,10 @@ Typewriter also helps teams adopt [analytics best practices](/docs/protocols/tra
 
 To get started, check out one of the quickstart guides below:
 - [Browser Quickstart](#browser-quickstart)
+- [Kotlin Quickstart](#kotlin-quickstart)
 - [Node.js Quickstart](#nodejs-quickstart)
+- [React Native Quickstart](#react-native-quickstart)
 - [Swift Quickstart](#swift-quickstart)
-- [Kotlin Quickstart](#kotlin-quickstart)
 
 > info ""
 > For use with the Analytics-iOS and Analytics-Android SDK, use [Typewriter v7](/docs/protocols/apis-and-extensions/typewriter-v7).
diff --git a/src/protocols/faq.md b/src/protocols/faq.md
@@ -13,13 +13,15 @@ You can subscribe to a variety of Protocols specific alerts through the workspac
 
 ### How can I get notified when someone makes a change to my tracking plan?
 
-You can forward notifications from Protocols to a new Segment Source, which can then send them to notification tools such as Slack webhook.
+You can forward notifications from Protocols to a new Segment source, which can then send them to notification tools such as Slack webhook. 
 
 You can also forward these Protocols alerts to any (cloud-mode) Segment destination that accepts Track calls, including data warehouses. Most customers record these activity feed events to a data warehouse for analysis.
 
 ### How do I get notified when new violations are generated? Can I create custom violation notifications?
 
-You can enable [violation event forwarding](/docs/protocols/validate/forward-violations/) to start delivering violations as Track calls to a Segment Source. From there, you can forward the events to any Segment destination that accepts Track calls.
+You can enable [violation event forwarding](/docs/protocols/validate/forward-violations/) to start delivering violations as Track calls to a Segment source. From there, you can forward the events to any Segment destination that accepts Track calls. 
+
+You can also use the Slack Actions destination to set event triggers for context fields, meaning events with violations are sent as Track calls directly from the source.
 
 
 ## Protocols Tracking Plan
