> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/campaigns/email-reputation.md).
# Email Reputation
Your email reputation, or how mailbox providers judge your emails, is impacted by how your recipients react to your emails. If the emails you send trigger a lot of spam complaints, your email reputation will worsen and future emails will be harder to get to the inbox.
On the other hand, if recipients engage with your emails by opening them and clicking on CTAs, your email reputation will improve, and your emails will be more likely to make it to the inbox. Though there isn't a single value or score that goes into calculating your email reputation, we recommend following suggested marketing practices and monitoring your reputation score in your account dashboard.
To check your Email Reputation Score & suggestions to improve it:
* Click on Reports in the sidebar, then click on 'Email Reputation'
* Review your stats and suggestions to improve!
---
# 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://help.gleantap.com/campaigns/email-reputation.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.
