# User Engagement Overview

The **User Engagement** section in PluginPulse helps you understand how users interact with your plugin, from overall adoption to version usage and feature-level behaviour. With the right insights, you can better track plugin performance, identify upgrade patterns, and pinpoint areas to improve user experience and retention.

### What's Included

The User Engagement section currently provides the following metrics. Click on the link to learn more about each:

1. [Active Users](https://plugin-pulse.gitbook.io/docs/user-engagement/active-users)
2. [Version Distribution](https://plugin-pulse.gitbook.io/docs/user-engagement/version-distribution)
3. [Default Page View Event](https://plugin-pulse.gitbook.io/docs/events/default-page-view-event)
4. [Custom Events ](https://plugin-pulse.gitbook.io/docs/events/custom-events)
5. [Server Actions](/docs/server-actions.md)

### Setup First

To use any engagement analytics, copy and paste the following snippet into your plugin's header:

```html
<script defer src="https://pluginpul.se/js/script.js" data-plugin-id="YOUR_PLUGIN_ID"></script>
```

You can copy a snippet specifically for your plugin on you **Plugin Dashboard -> Monitor User Engagement -> Copy Code**

### Privacy Considerations

* No personal information is collected
* All app IDs are one-way hashed for anonymity
* No cookies are used in the tracking process
* GDPR-compliant by design


---

# Agent Instructions: 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:

```
GET https://plugin-pulse.gitbook.io/docs/user-engagement/user-engagement-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.