Merge branch 'master' into thomas/screeb_new_integration

Author: tcgilbert

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

@@ -114,6 +114,42 @@ If you use Segment's React Native source library, you must explicitly bundle the
 
 <!-- LR Mar 2021: We didn't use the react-dest include here because Firebase needs the extra build.gradle step.-->
 
+## Setting up Firebase with Analytics-Kotlin
+If you're using the [Analytics-Kotlin library](/docs/connections/sources/catalog/libraries/mobile/kotlin-android), follow these steps to set up Firebase with Analytics-Kotlin:
+1. In your top-level `build.gradle` file add these lines:
+    ```kotlin  
+    buildscript {
+        ...
+        repositories {
+            google()
+        }
+        dependencies {
+            ...
+            classpath 'com.google.gms:google-services:4.3.5'
+        }
+    }
+    ```    
+2. In your app-module `build.gradle` file add these lines:
+    ```kotlin
+    ...
+    plugins {
+        id 'com.google.gms.google-services'
+    }
+
+    dependencies {
+        ...
+        implementation platform('com.google.firebase:firebase-bom:28.2.1')
+        implementation 'com.google.firebase:firebase-analytics-ktx'
+    }
+    ```
+3. Copy the [FirebaseDestination.kt](https://github.com/segmentio/analytics-kotlin/blob/main/samples/kotlin-android-app-destinations/src/main/java/com/segment/analytics/destinations/plugins/FirebaseDestination.kt) file into your project's codebase.
+4. Copy your `google-service.json` file to your app-module.
+5. Go to your project's codebase and add these lines where you intialize the analytics client:
+    ```kotlin
+    val Firebase = FirebaseDestination()
+    analytics.add(Firebase)
+    ```
+
 ## Identify
 
 When you call `identify` Segment will map to the corresponding Firebase Analytics calls:

src/personas/journeys/faq-best-practices.md

@@ -80,3 +80,7 @@ The data type you send to a destination depends on whether the destination is an
 
 ### Which roles can access Journeys?
 For Personas Advanced customers, users with either the Personas User or Personas Admin roles can create, edit, and delete journeys. Users with the Personas Read-only role are restricted to view-only access.
+
+### Why am I seeing duplicate entry or exit events?
+
+Journeys triggers audience or trait-related events for each email `external_id` on a profile. If a profile has two email addresses, you'll see two Audience Entered and two Audience Exited events for each Journey step. Journeys sends both email addresses to downstream destinations. 

src/personas/journeys/key-terms.md

@@ -38,5 +38,18 @@ Keep the following terms in mind as you begin to explore Journeys.
 | Draft Journey            | A Journey which is not yet computing nor sending data to destinations. <br /><br />For more information, see [Draft Journeys](#draft-journeys). |
 | Published (live) Journey | A Journey that is computing and sending data to destinations. <br /><br />For more information, see [Published Journeys](#published-journeys).                  |
 
+## Steps with Audiences
 
+| Step             | Audience definition                                                                                                           |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| Entry condition  | All users who fulfill the entry condition criteria. "Use Historical Data" evaluates events before Journey publication.        |
+| Condition        | All users who fulfill condition criteria, at one point fulfilled preceding step criteria, and have met any step wait conditions. |
+| Destination Sync | All users who, at one point, fulfilled parent step criteria and have met any following wait conditions.                        |
 
+## Steps without Audiences
+
+| Step                | Details                                                                                                            |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| Delay               | No audience. Segment appends the wait duration as a condition to the following step’s audience.                    |
+| T/F split           | The split's resulting conditions contain two mutually exclusive audiences.  The split node itself has no audience. |
+| Multi-branch splits | The split's resulting conditions contain audiences.  The split node itself has no audience.                        |