> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/tracking-events-aka-high-value-actions.md).

# Tracking Events (aka High Value Actions)

Tracking Events enables you to inform Pulse Insights that an important event occurred, typically related to a website goal or action, so that you can later correlate survey responses with it.

{% hint style="info" %}
Tracking events is **optional**, but **highly recommended** because it unlocks the ability to quantify the impact of what is typically siloed qualitative data. 
{% endhint %}

## Example Use Case

By informing Pulse Insights that a purchase event occurred, you can correlate survey responses with a purchase event. This helps you understand how different survey responses affect the probability of a purchase. For example, you could learn the "cost" of missing information on your product pages in terms of lost sales.

## The two ways to track events

### Using JavaScript

On any page that has the Pulse Insights code snippet, you can push event data like so:

```javascript
pi('track_event', 'Purchase', {plan: "Gold", value: 50.00});
```

{% hint style="info" %}
The two key benefits of this method are that you can dynamically populate data (like the purchase plan and price in the example above) to aid in custom analysis, and that you needn't rely on an event being simply a visit to a URL.
{% endhint %}

### In Console, by watching for visits to certain URLs 

In Console, you can configure visits to a particular URL to create an Event. This method is described in the [Console Configuration](broken://pages/RyFxKKurREonxrMZIFpe) section. 

## Recommended Events or High Value Actions To Consider Collecting

| Event                   |
| ----------------------- |
| Conversion              |
| Add to cart             |
| Key feature enrollments |
| Lead submissions        |
| Cancellation            |
| Support ticket creation |

{% hint style="info" %}
Just a few events goes a long way. Think of the top 2-3 things that indicate success or a problem on your website and start there.
{% endhint %}

###


---

# 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.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/tracking-events-aka-high-value-actions.md?ask=<question>&goal=<user_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.