> For the complete documentation index, see [llms.txt](https://emailpref.gitbook.io/emailpref-integration-with-esps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emailpref.gitbook.io/emailpref-integration-with-esps/integrations/keap/tags.md).

# Tags

Here's how it works:

1. **Automated Tag Retrieval**: Once your integration with Emailpref is successfully set up, the platform automatically retrieves your tags from Keap. This means you don't need to worry about manual list imports or data transfers.
2. **Effortless Management**: In the 'Lists' tab, Emailpref displays all your Keap tags. This intuitive interface allows you to view and manage your lists with just a few clicks. 
3. **Real-time Sync**: Emailpref's real-time synchronization ensures that all changes made on your preference page are instantaneously reflected in Keap. This guarantees that your subscriber's preferences are always up-to-date.

In summary, Emailpref's list integration process is designed to be intuitive and efficient, reducing manual work and ensuring that your email marketing efforts remain perfectly in sync with your Keap tags.


---

# 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://emailpref.gitbook.io/emailpref-integration-with-esps/integrations/keap/tags.md?ask=<question>&goal=<endgoal>
```

`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.