> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/phishing/results.md).
# Results and performance
Once a campaign is launched, employee interactions are tracked automatically. Results are available at three levels: company, campaign and employee.
## Company results
A global view of phishing performance across all campaigns:
* Number of emails sent
* Open rate: % of emails opened
* Click rate: % of emails clicked
* Submitted rate: % of emails where information was submitted
## Campaign results
Open a campaign to see how employees interacted with it:
* **Funnel**: emails sent, opened, links clicked, credentials submitted.
* **Email list**: every email sent in the campaign, with interaction status, recipient, date sent, template and scenario. Use the filters to scan the activity.
## Employee results
Open an employee to see how they interacted with simulations across campaigns:
* **Funnel**: emails sent, opened, links clicked, credentials submitted.
* **Email list**: every email sent to the employee, with interaction status, campaign name, date sent, template and scenario.
## Email details
From a campaign or an employee, click an email to see its full details:
* Date and time sent
* Template and scenario used, with a preview
* Sender
* Language
* Interaction history (opened, clicked, etc.)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.stoik.io/human-security/phishing/results.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
