Skip to content

Commit f3a31b2

Browse files
authored
Clarify Audience Real-Time Computation Rules
Remove info on time windows going to batch as now real-time has support for time windows
1 parent 8802cb0 commit f3a31b2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/engage/audiences/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ While Engage is computing, use the Audience Explorer to see users or accounts th
178178
> [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) impose rate limits on how quickly Segment can update an Audience. Segment syncs at the highest frequency allowed by the tool, which is between one and six hours.
179179
180180
> info "Real-time and batch computation"
181-
> By default, Segment creates all audiences as real-time computations. However, some conditions require batch computation. For example, [funnel audiences](#funnel-audiences) and audiences with time-window conditions can only be computed in batch mode. The Audience builder determines whether an audience is real-time or batch based on the conditions applied.
181+
> By default, Segment creates all audiences as real-time computations. However, some conditions require batch computation. For example, [funnel audiences](#funnel-audiences) can only be computed in batch mode. The Audience builder determines whether an audience is real-time or batch based on the conditions applied.
182182
183183
### Editing Realtime Audiences and Traits
184184

0 commit comments

Comments
 (0)