Suppression and data requests
Keep people and companies out of every campaign, and handle erasure and access requests for a lead.
Suppression
A suppressed lead is never contacted by a campaign, on any channel. Suppression is checked before every step, including while a lead waits, so adding a suppression stops leads that are already in a campaign at their next step.
A suppression names exactly one of:
| Type | Matches |
|---|---|
| A person, by channel identity | That identity on that channel. |
| A lead | Every identity of the lead, on every channel. |
| A company domain | Leads whose company domain, linked company domain or email domain matches, for example northwind.example. |
| A company name | Leads whose company name matches, ignoring case. |
Each suppression has a reason (opted out, customer, competitor, manual, bounced) and an optional note.
Scope
- Workspace suppressions apply to one workspace. Anyone who can import leads can add them.
- Organization suppressions apply to every workspace of the organization, for example an agency's own customers or a do-not-contact list shared by all clients. Only agency owners and managers can add them.
Suppressions are never shared between different customers of GraphKit.
Adding suppressions
- In the lead drawer, suppress the lead. It and every one of its identities are suppressed.
- In Lead Explorer, select leads and use the suppress bulk action.
- Open Lead Explorer → Suppressions to add a single person, domain or company, or choose Import do-not-contact CSV with a
valuecolumn (and optionaltype,reasonandnotecolumns). - Opt-outs add themselves: an opt-out keyword in the inbox, or an unsubscribe reported by a connected email platform, suppresses the lead on every channel with the reason opted out.
Every change is written to the audit log. Removing a lead-level suppression also removes the suppressions of that lead's identities.
Identity suppressions outlive the lead: if you delete a suppressed lead and later import the same person again, they are still suppressed.
Data subject requests
Your workspace is the controller of the lead data you put into GraphKit; GraphKit processes it on your behalf. These tools let you answer requests from the people you contact.
Erasure
Delete the lead (on the lead, or as a bulk action). In one step, GraphKit deletes the lead with its identities, list memberships, campaign enrollments and campaign activity, and unlinks it from conversations and from My Network. The deletion is audited as lead.deleted.
Two things are kept on purpose:
- Identity suppressions, so a person who asked not to be contacted is not contacted again after a re-import.
- Conversations, which mirror the connected account's own inbox on the network. Deleting them in GraphKit would not delete them there. To remove the message content from GraphKit too, delete the conversation in the inbox.
Access and portability
On a lead, choose Export data to download a JSON file with the lead, its identities and consent records, lists, enrollments, campaign actions, conversations with their messages, suppressions and network connections. Messages of private conversations are included only for people who can read private conversations. Exports need the team.manage permission (client admins and agency roles) and are audited as lead.data_exported.
Objections
When someone objects to being contacted, suppress the lead with the reason opted out. See Consent and opt-outs for what to tell people in a first message.