From cf738300e181367150a5e37e48b3b98f1cbc1572 Mon Sep 17 00:00:00 2001
From: Ashton Huxtable <78318468+ashton-huxtable@users.noreply.github.com>
Date: Mon, 30 Dec 2024 14:39:51 -0700
Subject: [PATCH] Add FAQ on difference in audience overview and preview count

---
 src/engage/audiences/index.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md
index 2217941a77..099503a490 100644
--- a/src/engage/audiences/index.md
+++ b/src/engage/audiences/index.md
@@ -278,3 +278,6 @@ This error occurs when creating audiences that reference each other, meaning aud
 
 ### How does the historical data flag work?
 Including historical data lets you take past information into account. You can data only exclude historical data for real-time audiences. For batch audiences, Segment includes historical data by default.
+
+### Why does the Audience Overview show a different count than the Audience preview?
+Segment uses two different systems to calculate the count for the Audience Overview and the Audience preview. The Audience Overview shows a count based on the lst successful run of the Audience, thus it is only updated every 16 hours or so. However, the preview will be more accurate to who fits the audience description at that exact moment in time.