WhatsApp audience compilation exclusions
Open the page
Campaign delivery report → Audience exclusions. WhatsApp access and access to the campaign are required.
Investigate exclusions
- Review the summary counts for invalid numbers, no number, duplicates, opt-outs and hard bounces; these are compilation exclusions, not delivery attempts. The report fetches the first 20,000 evidence rows by audit ID. Its total and category cards count those fetched rows, so they can understate a larger set; missing template values may appear in the table but have no separate summary card. Review the compilation evidence table: Contact, Checked field, Compilation result, Stored reason and Evaluated. Contact links open the contact when available; phone values are masked. Use the stored reason and code to identify why an entry was excluded. Table search, sorting and pagination operate on the loaded rows. If the page says compilation evidence is unavailable, ask an administrator to check the audit table.
- Correct underlying data or consent only when appropriate, then follow the campaign workflow for a new preview. Do not assume excluded recipients were sent a message.
Read the evidence
Contact identifies the linked contact when available; Checked field identifies the evaluated endpoint or field; Compilation result shows the outcome; Stored reason includes the recorded explanation or code; Evaluated gives the audit time. A duplicate means the same endpoint was removed from this compiled audience, not necessarily that the contact has no other eligible endpoint. An opt-out or hard bounce is a sending safeguard; do not remove it merely to increase the count. For missing template values, correct the source data and build a fresh preview. Evidence is bounded to the first 20,000 rows, so inspect campaign totals and do not treat these displayed cards as an exhaustive audit above that limit.