This article explains what the Notes column means on your email and phone blocklists and how each note value is applied.
What the “Notes” Column Represents
The Notes column tells you how a donation record was added to the blocklist (for either email or phone). Different note values indicate whether the blocklisting is temporary or permanent and how it occurred.
Quick-Reference Table — Blocklist Notes & Meanings
Use this table to identify why a supporter was blocklisted and whether the status is temporary (time-limited) or permanent.
| Note value (as seen on the blocklist) | What it means | Duration / Effect |
| Donor has no matching gift opportunity – blocklisted for X more days | The donor is not eligible (the donor has identified this in the matching gift emails) and therefore their email is blocklisted for X days. |
Temporary; recommended 180 days (default is saved accordingly). To learn more about how long donors are added to the blocklist, view this article. |
| Donor has no matching gift opportunity | Donor is not eligible (often because they reported being retired). | Permanent. |
| Donor unsubscribed from emails | Donor clicked the unsubscribe link in a matching gift email. | Permanent. |
| Donor marked as spam | Donor marked your email as spam. | Permanent. |
| Email address bounced | Message was undeliverable (bounce). | Permanent. |
| Blocklisted by an admin user | Your team manually added the address to the blocklist. | Permanent. |
| Double the Donation user manually unsubscribed donor | Admin unsubscribed the donor from the Donations table or via CSV bulk blocklist. To learn more about blocklisting donors in bulk, view this article. |
Blocklisted (admin-driven; used for individual or bulk unsubscribes). |
| Imported from CRM | For customers with a direct CRM integration, the record is blocklisted from CRM data. | Permanent. |
| Blocklisted via an API call | The add_phone_blocklist or add_email_blocklist REST endpoint was used. | Permanent. |