Skip to main content
This page covers Audience Boost — the Destination option that enriches your first-party (1P) audience with additional identifiers from Zeotap’s identity graph to increase match rates and addressable reach — and the outcomes you may see after enabling it: missing estimates, confusing size comparisons and the option not appearing for a Destination.
If your audience is stuck in an 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.
1
Check which audience you are reading. {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.
2
Compare like for like. Open Insights → Activation Metrics and compare the Boosted and Seed cards on the same field (User Count, Output Identifiers or — where the Destination reports feedback data — the Destination Metrics value, such as Estimated Audience Size). A destination-reported size for the boosted audience can legitimately sit below a Zeotap-side seed count, because the platform applies its own identifier match rate — that is a cross-system comparison, not a shrinking audience.
3
Confirm the boosted audience has completed a refresh since Audience Boost was enabled. Before the first refresh completes, its reported numbers are not yet meaningful to compare.
4
If the boosted {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.
To verify the fix worked: on a like-for-like comparison, the boosted {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

1
Confirm the date and time Audience Boost was enabled for this audience’s Destination. A boosted audience typically shows its estimate only after the audience’s next scheduled refresh completes and the records have been delivered to the destination.
2
Wait for the audience’s next scheduled refresh to complete before treating the empty estimate as an error. Re-open the audience to check whether the boosted audience’s estimate has populated.
Destination-platform counts (for example a DMP’s audience size or a CRM’s matched-user count) update on that platform’s own schedule after Zeotap delivers the records. Check the destination platform directly to see whether the boosted records have arrived there.
3
If the boosted audience’s status in the audiences list is still 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.
4
If the boosted audience reports a non-zero size but the destination platform reports a far smaller matched count, that is the destination’s identifier match rate at work, not a Zeotap-side failure. See Link an Audience to the Destination for how to manage the output identifiers sent to the destination.
To verify the fix worked: the boosted audience shows a non-empty estimate, and the destination platform’s count updates on its own schedule.

The Audience Boost Option Is Not Available for a Destination

Audience Boost is enabled per Destination, directly from the UI.
1
Open the Destination and go to its Destination Settings.
2
Go to the Enable Audience Boost section, select the Audience boost checkbox and save the Destination.

Destination Settings → Enable Audience Boost

3
If you cannot find the Enable Audience Boost section for this Destination, the feature may not be available for that platform — availability depends on the data acceptance policy of the specific Destination/Platform. Contact your Zeotap POC to confirm eligibility.
To verify the fix worked: the Audience boost checkbox is selected in the Destination Settings, and after the next refresh the Destination contains the boosted {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 Progress after 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.
For questions about whether a specific Destination/Platform’s data acceptance policy permits Audience Boost, contact your Zeotap POC. Include in your request:
  • Audience ID and name
  • Destination name and ID
  • Date and time Audience Boost was enabled on the Destination
  • The sizes of {audience_name} and do-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

No. The boosted {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.
No. That option only suppresses the separate 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.
The estimate typically appears after the audience’s next scheduled refresh completes. The destination platform then updates its own count on its own schedule after Zeotap delivers the records.
Audience Boost is enabled per Destination: open the Destination’s Destination Settings, go to the Enable Audience Boost section and select the Audience boost checkbox. If you cannot find that section, the feature may not be available for that platform — availability depends on the data acceptance policy of the specific Destination/Platform. Contact your Zeotap POC for any inquiries.
The destination platform reports on its own matched user base after applying its identifier match rate to the records Zeotap delivered. That count is independent of how Zeotap counts the audience, and a lower number there is not a Zeotap-side failure.
Last modified on November 18, 2026