Understanding Segment Counts, Estimated Audiences, and the Segments API

What segment and list counts represent

Segment and list counts in Klaviyo represent the number of profiles that currently meet the conditions of that segment, or are currently present in that list, at the time the count is calculated. Dynamic segments recalculate automatically as people meet or no longer meet the conditions, while lists are static collections of profiles that you add via forms, integrations, or imports.

Why the campaign builder shows an estimated audience

When you select a list or segment in the campaign setup flow, Klaviyo shows an estimated audience instead of the raw list or segment size. This estimate applies additional rules on top of membership in the list or segment, such as:

• Suppression status (e.g., unsubscribed or bounced profiles)
• Consent status for the channel you are sending with
• Smart sending rules, if enabled for the campaign

Because of these filters, the estimated audience is often smaller than the list or segment size you see in the Lists & Segments view. The final send count is determined at send time, when Klaviyo takes a snapshot of everyone who still qualifies for the audience and is eligible to receive messages.

How often segment counts update

Dynamic segment counts update as underlying data changes, including:

• New events (e.g., opens, clicks, orders) that cause people to qualify or disqualify
• Profile property changes
• Subscription status updates and suppressions

Since segments are recalculated in near–real time, the count you see in the Lists & Segments tab can differ from:

• The estimated audience in the campaign builder, which accounts for send‑eligibility rules
• The final number of recipients on a sent campaign, which is a snapshot taken at the scheduled send moment

How suppression, consent, and smart sending affect counts

Even if a profile belongs to your chosen list or segment, Klaviyo will not send to them if:

• They are suppressed (e.g., unsubscribed, bounced, or otherwise marked as ineligible),
• They do not have valid consent for the channel (e.g., email or SMS),
• They are excluded by smart sending, when enabled, because they received another recent message within your smart sending window.

These exclusions are why your campaign’s estimated audience, and final send counts, can be lower than the raw size of your audience.

Getting segment counts with the Segments API

You can retrieve segment‑level information, including counts, using the Segments API.

A typical request will:

• Call the endpoint that returns your segments,
• Include metadata such as when the segment was created and the total number of profiles currently in the segment.

In the response, look for fields that indicate:

• The segment identifier, which you can use in other API calls,
• The current size of the segment, which represents how many profiles match the conditions at the time of the response.

Because segment membership is dynamic, API‑returned counts are a point‑in‑time snapshot and can change between calls.

Best practices for syncing counts to external tools

If you sync segment counts into a BI tool or external dashboard:

• Pull counts on a consistent schedule (e.g., daily at the same time) to make trend comparisons easier.
• Align your reporting time zone between Klaviyo and your external system.
• Document any additional filters you apply (e.g., removing suppressed profiles) so downstream users know why numbers may differ from what they see in the app.

When reconciling differences between segment sizes, estimated audiences, and send counts, always compare:

• The audience definition (list/segment conditions),
• The send‑eligibility rules (suppression, consent, smart sending),
• The time at which each count was taken.