Merge pull request #19 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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.                        |