Skip to content

Commit 39c486c

Browse files
authored
Merge branch 'segmentio:develop' into develop
2 parents 87f10a8 + d533e13 commit 39c486c

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

src/engage/audiences/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,7 @@ To create a new Audience or Trait:
193193

194194
2. Configure and preview your Audience or Trait.
195195
- A lightning bolt next to `Realtime Enabled` indicates that the computation updates in real-time.
196-
- By default, Segment queries all historical data to set the current value of the computed trait and Audience. Backfill computes historical data up to the point of audience creation. You can uncheck **Include Historical Data** to compute values for the Audience or trait without historical data. With backfill disabled, the trait or Audience only uses the data that arrives after you create it.
196+
- Configure the **Include Historical Event Data** option to limit how far back event data is processed by setting a lookback window (for example, the “last 90 days”). Unchecking **Include Historical Event Data** computes values without historical event data, using only data arriving after audience creation.
197197

198198
3. Select destinations to connect, then review and create your Audience or Trait.
199199

@@ -375,4 +375,4 @@ The audience builder accepts CSV and TSV lists.
375375
This error occurs when creating audiences that reference each other, meaning audience X refers to audience Y in its trigger condition, and later you attempt to modify audience Y's trigger condition to refer back to audience X. To avoid this error, ensure that the audiences do not reference each other in their conditions.
376376

377377
### How does the historical data flag work?
378-
Including historical data lets you take past information into account. You can only exclude historical data for real-time audiences. For batch audiences, Segment includes historical data by default.
378+
The **Include Historical Event Data** option lets you take past event data into account and control how much of it is considered when creating real-time audiences. You can set a lookback window (for example, the “last 90 days”) to limit the processed event data, or disable it entirely to use only data arriving after creation. For batch audiences, Segment includes historical data by default.

src/segment-app/extensions/dbt.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ To set up the dbt extension, you'll need:
2828

2929
- an existing dbt account with a Git repository
3030
- for job syncs, dbt cloud with jobs already created
31+
- a user with Workspace Owner permissions in Segment
3132

3233
### Git repository and dbt Models setup
3334

0 commit comments

Comments
 (0)