> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/guides/campaigns/campaign-contacts.md).
# Campaign Contacts
Campaign Contacts is a tab in each campaign that lists the contacts belonging to that campaign.
Use it to see who has interacted with the campaign, review individual contact history, and remove unwanted contacts.
A contact is added to the Campaign Contacts list when it:
* Is addressed and sent an email that belongs to the campaign. Contacts excluded before sending are not added.
* Is addressed and sent an SMS that belongs to the campaign. Contacts excluded before sending are not added.
* Submits a form belonging to the campaign.
* Visits a webpage belonging to the campaign. Anonymous visits are not added.
* Is imported to the campaign using the Import Contacts feature in the campaign's left-hand menu.
## Campaign Contacts interface
Campaign Contacts interface
Click an individual contact to view the history of their interactions within the campaign. To find a specific contact, use Quick Search in the top right corner of the tab.
### Removing contacts from a campaign
You can use this tab to remove unwanted contacts from the campaign, and by extension from each component report within the campaign. This is useful for removing test contacts.
1. Select the contacts to remove using the checkboxes on the left of each row.
2. Click Remove selected from campaign above the list.
## All contacts in this campaign (Recipient Source)
You can address Campaign Contacts using the "All contacts in this campaign" option when sending an email or SMS. See the definition at the top of this article for what counts as a campaign contact.
The "All contacts in this campaign" option
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.emarketeer.com/guides/guides/campaigns/campaign-contacts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.