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 | How it got there |
---|---|---|---|
Donor has no matching gift opportunity – blocklisted for X more days | Donor indicated via matching gift emails that they’re not eligible. | Temporary; recommended 180 days (default is saved accordingly). | Via donor response in matching gift emails. |
Donor has no matching gift opportunity | Donor is not eligible (often because they reported being retired). | Permanent. | From donor’s indication of ineligibility. |
Donor unsubscribed from emails | Donor clicked the unsubscribe link in a matching gift email. | Permanent. | Donor action (unsubscribe). |
Donor marked as spam | Donor marked your email as spam. | Permanent. | Donor action (spam report). |
Email address bounced | Message was undeliverable (bounce). | Permanent. | System-added on bounce. |
Blocklisted by an admin user | Your team manually added the address to the blocklist. | Permanent. | Admin action. |
Double the Donation user manually unsubscribed donor | Admin unsubscribed the donor from the Donations table or via CSV bulk blocklist. | Blocklisted (admin-driven; used for individual or bulk unsubscribes). | Admin action (single or bulk). |
Imported from CRM | For customers with a direct CRM integration, the record is blocklisted from CRM data. | Permanent. | CRM integration. |
Blocklisted via an API call | The add_phone_blocklist or add_email_blocklist REST endpoint was used. | Permanent. | API action. |