In Progress status without Audience Boost involved, see Audience Status and Activation Status.What Happened
You enabled (or tried to enable) Audience Boost and one of the following:- The boosted audience’s size appears smaller than the seed audience’s size.
- After enabling Audience Boost, no estimate populates and the connected destination platform’s count does not change.
- The Audience Boost option is not available in the Destination Settings of the Destination you are linking.
Why This Happens
When Audience Boost is enabled, Zeotap creates two audiences in the connected Destination:{audience_name}, which contains your 1P seed data plus the Audience Boost enriched data, and do-not-use-{audience_name}, a benchmark reference that never receives the Audience Boost enriched data (by default it contains the seed data only). Because the boosted {audience_name} contains everything the seed contains and more, it should be larger than the seed — the Audience Insights Activation Metrics tab shows the uplift (for example, 50%↑) it delivers over the seed baseline.
- Most “boosted is smaller than the seed” reports are a comparison mismatch, not a data loss: reading the
do-not-use-{audience_name}benchmark (which is the un-boosted baseline by design), comparing a destination-reported matched count against a Zeotap-side count, or reading sizes before the first refresh completes. A boosted audience that is genuinely smaller than its seed on a like-for-like comparison is an anomaly to escalate, not expected behaviour. - Enabling the Do not create/refresh seed audience option only suppresses the
do-not-use-{audience_name}benchmark audience. It does not remove seed records from the boosted audience —{audience_name}still contains seed plus enrichment. - A newly enabled boost typically shows its estimate only after the audience’s next scheduled refresh completes, and the destination platform reflects the new records on its own schedule after delivery.
- Audience Boost is enabled per Destination, from that Destination’s settings in the UI. Its availability depends on the data acceptance policy of the specific Destination/Platform.
- The destination platform’s matched count is governed by that platform’s identifier match rate against the records you sent — it is independent of how Zeotap counts the audience.
How to Resolve
Identify which of the three symptoms matches your situation, then follow that subsection.
Segment → Audiences
The Boosted Audience Looks Smaller Than the Seed Audience
The boosted audience is defined as seed plus enrichment, so it should never be genuinely smaller than the seed. Work through the comparison checks below; if the gap survives all of them, treat it as an anomaly and raise it with support.{audience_name} is the boosted audience; do-not-use-{audience_name} is the un-boosted benchmark and is expected to show the smaller, baseline size (it should not be used for targeting). Expected outcome: you have identified the boosted audience’s own numbers.{audience_name} is still smaller than the seed on the same metric from the same source, raise a support request with the audience ID, both sizes and where you read them, and the destination involved. This is not expected behaviour for any configuration — including Do not create/refresh seed audience, which only suppresses the benchmark audience and never removes seed records from the boosted output.{audience_name} reports a size at or above the seed, and its Activation Metrics card shows the uplift over the seed baseline.
No Estimate Populates or the Destination Does Not Change
In Progress after its scheduled refresh has completed, raise a support request with the audience ID, the destination, and the time the boost was enabled, and ask for the run to be re-triggered.The Audience Boost Option Is Not Available for a Destination
Audience Boost is enabled per Destination, directly from the UI.
Destination Settings → Enable Audience Boost
{audience_name} (plus the do-not-use-{audience_name} benchmark, unless you suppressed it with Do not create/refresh seed audience).
When to Contact Support
Raise a support request when:- The boosted audience’s status in the audiences list stays
In Progressafter its scheduled refresh has completed and a re-open shows no change. - The boosted
{audience_name}is smaller than the seed on a like-for-like comparison (same metric, same source) after the checks above — this is an anomaly, not expected behaviour.
- Audience ID and name
- Destination name and ID
- Date and time Audience Boost was enabled on the Destination
- The sizes of
{audience_name}anddo-not-use-{audience_name}as shown, and where you read them (Zeotap audiences list, Activation Metrics, or the destination platform) - The exact alert or status text shown on the audience
- Destination platform’s reported matched count, if you have it
FAQs
Can the boosted audience be smaller than the seed audience?
Can the boosted audience be smaller than the seed audience?
{audience_name} contains your seed data plus the Audience Boost enriched data, so it should be larger than the seed — that uplift is the point of the feature. If it looks smaller, first check that you are not reading the do-not-use-{audience_name} benchmark (the un-boosted baseline) or comparing a destination-reported matched count against a Zeotap-side count. If it is genuinely smaller on a like-for-like comparison, raise a support request.Does 'Do not create/refresh seed audience' remove seed records from the boosted audience?
Does 'Do not create/refresh seed audience' remove seed records from the boosted audience?
do-not-use-{audience_name} benchmark audience, so only the boosted audience is created and refreshed. The boosted {audience_name} still contains seed plus enriched data.How long does it take for the boosted estimate to appear after enabling Audience Boost?
How long does it take for the boosted estimate to appear after enabling Audience Boost?
Why is the Audience Boost option not visible for my Destination?
Why is the Audience Boost option not visible for my Destination?
Why does the destination platform report fewer users than the boosted size in Zeotap?
Why does the destination platform report fewer users than the boosted size in Zeotap?