Merge branch 'develop' into 3427-content-IG

forstisabella · forstisabella · commit d0b3b19ccf26 · 2022-12-08T13:02:44.000-05:00
diff --git a/src/connections/destinations/catalog/pendo/index.md b/src/connections/destinations/catalog/pendo/index.md
@@ -28,7 +28,9 @@ To add the Pendo destination using Cloud-mode, use the [Webhooks](/docs/connecti
 
 1. From the Segment web app, click **Catalog**.
 2. Search for **Webhooks** in the Catalog, select it, and choose which of your JavaScript sources to connect the destination to.
-3. Add the following as your Webhook URL: `https://pendo-io.appspot.com/data/segmentio/YOUR_PENDO_API_KEY` and replace `YOUR_PENDO_API_KEY` with your actual Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key.
+3. Webhook URL configuration will vary based on which Pendo environment you use and your API key:
+  * For US customers, add the following as your Webhook URL: `https://segment.us.pendo.io/data/segmentio/YOUR_PENDO_API_KEY` and replace `YOUR_PENDO_API_KEY` with your actual Pendo API Key, which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key.
+  * For EU customers, add the following as your Webhook URL: `https://segment.eu.pendo.io/data/segmentio/YOUR_PENDO_API_KEY` and teplace `YOUR_PENDO_API_KEY` with your actual Pendo API Key, which you can find in the Pendo UI under [Site Settings](https://app.eu.pendo.io/admin) > Basic Information > API Key.
 4. Headers are not required in Webhook configuration. Once you're done adding in your URL, save changes.
 5. Using Track method also requires a setting enabled on your Pendo subscription. contact Pendo to enable this feature flag for your account.
 
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md
@@ -499,6 +499,7 @@ If you use a Java codebase, please refer to the [Java Compatibility docs](https:
 Segment currently supports these destinations for Analytics Kotlin and is actively adding more:
 * [Amplitude](https://github.com/segment-integrations/analytics-kotlin-amplitude)
 * [Appsflyer](https://github.com/segment-integrations/analytics-kotlin-appsflyer)
+* [Braze](https://github.com/braze-inc/braze-segment-kotlin)
 * [Firebase](https://github.com/segment-integrations/analytics-kotlin-firebase)
 * [Mixpanel](https://github.com/segment-integrations/analytics-kotlin-mixpanel)
 
diff --git a/src/engage/index.md b/src/engage/index.md
@@ -14,7 +14,7 @@ Engage Channels builds on top of these Audiences, helping you connect with and m
 #### Create unified customer profiles
 Engage uses [Segment Identity Resolution](/docs/profiles/identity-resolution/) to take event data from across devices and channels and intelligently merge it into complete user- or account-level profiles. This gives your organization a single view of your customer base. To learn more, read the [Identity Resolution documentation](/docs/profiles/identity-resolution/).
 
-{% include components/reference-button.html href="https://segment.com/customers/frameio/" icon="personas.svg" title="Personalizing customer interactions" description="Support teams rely on Segment's unified profiles to make real-time and informed decisions about customers when answering tickets or taking support calls. Read about how the support team at Frame.io reduced ticket response time by 80%." %}
+{% include components/reference-button.html href="https://segment.com/customers/frame-io/" icon="personas.svg" title="Personalizing customer interactions" description="Support teams rely on Segment's unified profiles to make real-time and informed decisions about customers when answering tickets or taking support calls. Read about how the support team at Frame.io reduced ticket response time by 80%." %}
 
 #### Enrich profiles with new traits
 Add detail to user profiles with new traits and use them to power personalized marketing campaigns. You can add new traits to your user or account profiles in Engage using:
diff --git a/src/profiles/profiles-sync/index.md b/src/profiles/profiles-sync/index.md
@@ -59,8 +59,9 @@ Follow these steps to connect your warehouse:
 5. If the connection test succeeds, Segment enables the **Next** button. Select it.
   * If the connection test fails, verify that you’ve correctly entered the warehouse credentials, then try again.
 6. Select **Next** on the **Sync schedule** page. Segment displays the Profiles Sync overview page.
+7. Select **Request sync to be enabled**.
 
-At this point, Segment enables live syncs for your account.
+Segment staff then receives and enables live sync for your account.
 
 #### Using historical backfill
 
diff --git a/src/profiles/profiles-sync/sample-queries.md b/src/profiles/profiles-sync/sample-queries.md
@@ -185,11 +185,9 @@ As a result, you can retrieve a customer’s complete event history by joining a
 
 For more information, view the [Profiles Sync tables guide](/docs/profiles/profiles-sync/tables/).
 
-#### Should I expect discrepancies between Profile data seen in Segment Profiles (or) UI vs. what’s exposed via Profiles in the Warehouse?
+#### Does Profiles Sync data ever differ from Profiles data?
 
-<!-- fix this header^^ -->
-
-Profiles Sync mimics the materialization performed by Segment Profiles. A user’s merges, external IDs, and traits should be expected whether they’re queried in the warehouse, Profile API, or viewed in the UI.
+Profiles Sync mimics the materialization performed by [Segment Profiles](/docs/profiles/). A user’s merges, external IDs, and traits should be expected whether they’re queried in the warehouse, Profile API, or viewed in the UI.
 
 The following edge cases might drive slight (<0.01%) variation:
 
diff --git a/src/profiles/profiles-sync/tables.md b/src/profiles/profiles-sync/tables.md
@@ -165,8 +165,10 @@ All these events were performed by the same person. If you use these tables to a
 
 ## Tables you materialize
 
-> info ""
-> To help with your table materializations, Segment hosts dbt code in a private GitHub repository. To request access, reach out to Segment support with your GitHub username and email address.
+> info "dbt model definitions package"
+> To get started with your table materializations, try Segment's [open-source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="_blank"}.
+
+With Profiles Traits materialized view, you can view all custom traits, computed traits, SQL traits, audiences, and journeys associated with a profile in a single row.
 
 Every customer profile (or `canonical_segment_id`) will be represented in each of the following tables.
 
diff --git a/src/protocols/faq.md b/src/protocols/faq.md
@@ -24,9 +24,9 @@ You can enable [violation event forwarding](/docs/protocols/validate/forward-vio
 
 ## Protocols Tracking Plan
 
-### Do I need to add a Page Viewed event to my tracking plan?
+### How do I add Page and Screen events to my tracking plan?
 
-Yes. To consolidate the views in the Schema tab, Segment automatically converts `page` calls into `Page Viewed` events that appear in the Schema Events view. Segment recommends adding a `Page Viewed` event to your Tracking Plan with any properties you want to validate against. At this time, you cannot validate that a specific named page (`analytics.page('Homepage')`) has a specific set of required properties.
+To consolidate the views in the Schema tab, Segment automatically converts `page` and `screen` calls into `Page Viewed` and `Screen Viewed` events that appear in the Schema Events view. Segment recommends adding a `Page Viewed` or `Screen Viewed` event to your Tracking Plan with any properties you want to validate against. At this time, to validate that a specific named page/screen (`analytics.page('Homepage') | analytics.screen('Home')`) has a specific set of required properties, you will need to use the [JSON Schema](/docs/protocols/tracking-plan/create/#edit-underlying-json-schema).
 
 ### How can I see who made changes to my Tracking Plan?
 
