> For the complete documentation index, see [llms.txt](https://user-help.runmags.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user-help.runmags.com/advertising-sales/organizations/client-engagement.md).

# Client engagement

Ever wondered if clients opened your email to click your links? Well now you'll know.

Under each advertiser client record, you'll see a tab called Engagement. In that tab you can see which email they opened (personal and mass email) and which link they clicked, as well as when.

The target column show which link that is clicked, followed by the url.

The referral column show which email that initiated the engagement. This can be a mass email or a personal email. This also includes email sent by your colleagues.

The last four columns will show which contact that engaged and when.

### Use with caution <a href="#use-with-caution" id="use-with-caution"></a>

While this new feature is perfectly legal and employs technology that is widely used by modern platforms, we advice that you use the information with caution.

Some people may be startled if you tell them you just noticed they clicked your links, so use the intel wisely.


---

# 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://user-help.runmags.com/advertising-sales/organizations/client-engagement.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.