# Tracking Events

Setting up a conversion event allows you to measure the target conversion rate and attributed purchase amount for sent messages, enabling a practical analysis of message performance. To set up a conversion event, event integration must be completed first.

***

## Tracking Conversions

<div align="left"><figure><img src="/files/IexKnzHxDqDXNC5NEIJS" alt=""><figcaption><p>Image by FlareLane</p></figcaption></figure></div>

Two values are required for tracking conversion events:

* **Type**: Set the event type that will serve as your conversion goal.
* **Window**: Specify the time frame within which conversions are tracked after the message is sent.

For example, if the conversion goal is set to the "purchase" event with a 3-day window, any purchase event triggered by the user within 3 days of receiving the message will count as a conversion.

Conversion events are divided into general or purchase events. If you wish to set the purchase event as a conversion goal, you can also track its amount. Here's an example:

<figure><img src="/files/32pK6GxBg0QU93w2kEZL" alt=""><figcaption><p>Image by FlareLane</p></figcaption></figure>

Go to Settings > Project > Purchase Event to configure the setting. If you enter data keys for the amount and quantity associated with the purchase event, the purchase amount will be calculated.

The purchase amount will be calculated as **Price × Quantity**.

***

## **Conversion Tracking Rules**

* A conversion event is counted when the **target event** occurs within the specified **window from the time the message was sent**.&#x20;
* Please note that only one conversion will be counted **per user ID**. For instance, if a message is sent to five devices under a single user ID and one of those devices converts, the total send count will be five, but the conversion count will be one, resulting in a 100% conversion rate.
* If multiple messages tied to the **same target event** are sent to a user within the specified time window, and a conversion occurs, all the messages will count as a conversion.


---

# 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://guide.flarelane.com/engagement-tools/tracking-events.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.