Merge pull request segmentio#171 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/personas/audiences/index.md

@@ -95,6 +95,19 @@ To create a new audience:
 > warning ""
 > [Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/), [Marketo Lists](/docs/connections/destinations/catalog/marketo-static-lists/), and [Adwords Remarking Lists](/docs/connections/destinations/catalog/adwords-remarketing-lists) have rate limits on how quickly we can update an audience. We sync at the highest frequency allowed by the tool, which is between 1 hour and 6 hours.
 
+### Editing Realtime Audiences and Traits
+
+Personas supports the editing of realtime Audiences and Traits, which allows you to make nuanced changes to existing Traits and Audiences in situations where cloning or building from scratch may not suit your use case.
+
+To edit a realtime Trait or Audience, follow these steps:
+
+1. In your Personas Space, select the **Computed Traits** or **Audiences** tab.
+2. Select the realtime Audience or Trait you want to edit.
+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.
+
 ## Accessing your Audiences using the Profiles API
 
 You can access your audiences using the Profile API by querying the `/traits` endpoint. For example, if you can query for the `high_value_user` with the following GET request:

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

@@ -37,13 +37,31 @@ To edit the steps within a published Journey, make a copy of the Journey you wis
 
 When you do this, the key used for syncing to destinations will be different from the copied Journey. Make sure you change the reference key used in the downstream destinations accordingly.
 
-### Use Traits for conditions based on historical data
+### Know how to incorporate historical data
 
-Aside from the entry condition, all Journey step conditions are triggered by future events and existing trait memberships. This means that event-based conditions evaluate events that have occurred *after* the Journey is published.
+Aside from the entry condition, all Journey step conditions are triggered by future events and existing trait memberships. Event-based conditions only evaluate events that occur *after* the Journey is published.
 
-As a result, if you want to include historical events that may have occurred *before* the Journey was published, create conditions based on traits, instead of events.
+When you [include historical data](/docs/personas/journeys/build-journey/#using-historical-data-for-the-entry-step) in a Journey's entry condition, Personas backfills entry with users who previously satisfied the entry condition. For example, to evaluate if a user has ever used a discount code mid-Journey, create and configure a [Computed Trait](/docs/personas/computed-traits/#conditions) to select for `discount_used = true` to use in your Journey.
 
-For example, to evaluate if a user has ever used a discount code mid-Journey, create and configure a [Computed Trait](/docs/personas/computed-traits/#conditions) to select for `discount_used = true` to use in your Journey.
+This historical backfill has no impact on any additional Journey steps, however. To include historical data in post-entry conditions, use the following table to identify which conditions will automatically backfill historical data:
+
+| Condition Type     | Automatic Historical Data Backfill |
+| ------------------ | ---------------------------------- |
+| Computed Trait     | Yes                                |
+| Audience Reference | Yes                                |
+| Event              | No                                 |
+| Custom Trait       | No                                 |
+
+
+To include historical data based on custom traits or events that predate the Journey, first build an Audience that includes the targeted data by following these steps:
+
+1. Create a standard Personas Audience **outside of the Journeys builder**.
+2. Add conditions that include the historical event or custom trait you want to include in the Journey.
+3. After you've created the Audience, return to Journeys and create a **Part of an Audience** condition that references the audience you created in Step 2.
+
+For example, to include `custom trait = ABC` in a Journey, create an Audience called `ABC` that includes that custom trait, then add the Journey condition **Part of Audience** `ABC`.
+
+Using the **Part of Audience** condition, Journeys then populates the custom trait as if it were a backfill.
 
 ### Use dev spaces and data warehouse destinations to test journeys