From e7a6c7541c1915e15bd8a7d1b102fa9581f252ac Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Wed, 23 Feb 2022 14:11:43 -0800 Subject: [PATCH 1/2] Batch-audience-compute-clarification --- src/personas/audiences/account-audiences.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/personas/audiences/account-audiences.md b/src/personas/audiences/account-audiences.md index efb66507ab..99e6903608 100644 --- a/src/personas/audiences/account-audiences.md +++ b/src/personas/audiences/account-audiences.md @@ -100,7 +100,7 @@ For example, you may wish to create an audience which selects all admin-level us ## Known limitations of account-level audiences -- Unlike user-level audiences which are [computed in real time](/docs/personas/audiences#realtime-compute-vs-batch), account-level audiences are computed on an hourly, batched basis. +- Unlike user-level audiences, which are [computed in real time](/docs/personas/audiences#realtime-compute-vs-batch), account-level audiences are computed on a batched basis. Segment computes account-level audiences roughly every hour, but it's important to note that compute times might fluctuate. - Account-level audiences do not respect the `context.groupId` property on track calls. If users are associated with multiple accounts (through multiple group calls), the entire collection of a user’s events is considered when evaluating user-level event conditions (not just those events which are tagged with a matching `groupId`). This can lead to unexpected results where a user’s events triggered in the context of one account lead to another account incorrectly matching an account-level audience. - The identity breakdown report (displayed in the audience builder for user-level audiences) is not available for account-level audiences. From e97c6c99c2bbeb42cf0c1dd1275e3eaf2f7591e9 Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Wed, 23 Feb 2022 16:03:08 -0800 Subject: [PATCH 2/2] Apply suggestions from code review --- src/personas/audiences/account-audiences.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/personas/audiences/account-audiences.md b/src/personas/audiences/account-audiences.md index 99e6903608..08cf236ce0 100644 --- a/src/personas/audiences/account-audiences.md +++ b/src/personas/audiences/account-audiences.md @@ -100,7 +100,7 @@ For example, you may wish to create an audience which selects all admin-level us ## Known limitations of account-level audiences -- Unlike user-level audiences, which are [computed in real time](/docs/personas/audiences#realtime-compute-vs-batch), account-level audiences are computed on a batched basis. Segment computes account-level audiences roughly every hour, but it's important to note that compute times might fluctuate. +- Unlike user-level audiences, which are [computed in real time](/docs/personas/audiences#realtime-compute-vs-batch), account-level audiences are computed on a batched basis. Segment computes account-level audiences roughly every hour, but it's important to note that compute times can fluctuate based on the load on the system. - Account-level audiences do not respect the `context.groupId` property on track calls. If users are associated with multiple accounts (through multiple group calls), the entire collection of a user’s events is considered when evaluating user-level event conditions (not just those events which are tagged with a matching `groupId`). This can lead to unexpected results where a user’s events triggered in the context of one account lead to another account incorrectly matching an account-level audience. - The identity breakdown report (displayed in the audience builder for user-level audiences) is not available for account-level audiences.