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

# Engagement conversion

Track message performance from send to conversion across push, widget, popup, in-app, SMS, email, and WhatsApp — in one view.

**Path**: `Engagement Conversion` (below **Dashboard** in the main menu)

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FoxzIDcAK2zPlJfZhOlJB%2FEkran%20Resmi%202026-10-15%2015.19.01.png?alt=media&amp;token=52e64c14-7f30-401d-992a-3c4aa27ddefc" alt="Engagement Conversion in the main menu, below Dashboard" width="268"><figcaption><p>Engagement Conversion in the main menu</p></figcaption></figure>

**Engagement Conversion** shows how your messages perform across the full journey from send to conversion: how many messages were sent, how many reached users, how many were clicked, and how many led to a conversion or revenue. It covers push, widget, popup, in-app, SMS, email, and WhatsApp in a single view.

Use this page to answer three questions:

* How are my messages performing overall?
* Which message, channel, or label drives the most clicks and conversions?
* Where do I lose users between send and conversion?

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FrXK5NBfRQQ9dPeDZzzi6%2FEkran%20Resmi%202026-10-15%2015.19.31.png?alt=media&amp;token=dabb9b35-6b35-420d-8c01-03cad1e9ddb4" alt="Engagement Conversion page with filters and KPI cards"><figcaption><p>Engagement Conversion: filters and KPI cards</p></figcaption></figure>

The page is organized into four areas, from top to bottom:

1. **Filters**: date range, label, channel, conversion event, and conversion window.
2. **KPI cards**: Sent, Reach / Shown, Click, Conversion, and Revenue for the selected date range.
3. **Daily Trend**: a line chart of daily Clicks and Conversion.
4. **Performance tables**: the same metrics grouped by Message, Channel, or Label.

The **Export** button in the top-right corner of the page downloads the data in the performance table currently selected.

### Before you begin

Sent, Reach, and Click work as soon as you send messages. Conversion and Revenue need a small amount of setup first.

* **Conversion** counts the conversion event and conditions defined in the campaign. If you select a different event in the **Conversion event** filter, that event is counted instead. When no conversion event is measured, the Conversion card shows **—** and CR shows **CR: —**.
* **Revenue** is calculated from a revenue event. Until a revenue event is defined, the Revenue card shows **—** with **Not defined** below it. To set one up, see [Events](/netmera-user-guide/customer-data/events.md).
* **Click** is available for push, popup, and in-app messages. Widget is the only channel without clicks, so Click and CTR stay empty for widgets.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FQ5HRivFV5K0qyxjxaV4d%2FEkran%20Resmi%202026-10-15%2015.05.12.png?alt=media&amp;token=ab2577d3-4aa3-49a9-a8f9-e36789d26153" alt="KPI cards with no conversion event and no revenue event defined"><figcaption><p>KPI cards before conversion and revenue setup: Conversion and CR show —, Revenue shows Not defined</p></figcaption></figure>

### Filters

The filters at the top of the page control what appears in the KPI cards, the Daily Trend, and the tables.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FXq9URSv7ONRYHkAminYo%2FEkran%20Resmi%202026-10-15%2015.05.35.png?alt=media&amp;token=c2f48250-b2cc-412d-8484-3401de81fa98" alt="Filter bar with date range, label, channel, conversion event, and conversion window"><figcaption><p>Filters in their default state</p></figcaption></figure>

<table><thead><tr><th width="235.00390625">Filter</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Date range</strong></td><td>Sets the period shown. Select <strong>Yesterday</strong>, <strong>7D</strong>, or <strong>30D</strong>, or pick start and end dates in the <strong>Custom</strong> field. The range can be up to 30 days.</td></tr><tr><td><strong>Label</strong></td><td>Limits the page to messages that carry the selected label. Default: <strong>All labels</strong>.</td></tr><tr><td><strong>Channel</strong></td><td>Limits the page to the selected channel. Default: <strong>All channels</strong>.</td></tr><tr><td><strong>Conversion event</strong></td><td>Selects the event used to count conversions. The default is <strong>Campaign setting</strong>: each message is measured by the conversion event defined in its campaign. If you select another event, all messages are measured by that event.</td></tr><tr><td><strong>Conversion window</strong></td><td>Sets how long after the send a conversion is counted. See <a href="#conversion-window">Conversion window</a>.</td></tr></tbody></table>

### Conversion window

The conversion window defines how long after a message is sent a conversion is still attributed to that message. The default option is **Campaign setting**. To choose another option, open the **Conversion window** dropdown at the top of the page. Hover over the filter to see a short reminder of how the window is counted.

| Option                         | How conversions are counted                                                                                                                                                      |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Campaign setting** (default) | Push, popup, and widget: no time limit. Every subsequent matching event by a user who came from the message is counted. Email and SMS: the duration set in the campaign applies. |
| **24 hours**                   | Conversions that occur within 24 hours of the send are counted.                                                                                                                  |
| **72 hours**                   | Conversions that occur within 72 hours of the send are counted.                                                                                                                  |
| **7 days**                     | Conversions that occur within 7 days of the send are counted.                                                                                                                    |

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fr1GXvzhyqxcoLJvk1R0q%2FEkran%20Resmi%202026-10-15%2015.06.06.png?alt=media&amp;token=803079e9-bb3e-461a-892f-943fe9540f90" alt="Conversion window dropdown open with Campaign setting, 24 hours, 72 hours, and 7 days"><figcaption><p>Conversion window options and tooltip</p></figcaption></figure>

The window starts at the moment the message is sent, not at the moment it is clicked.

{% hint style="info" %}
**Example**: A push is sent on Monday at 10:00. The user clicks it on Tuesday at 09:00 and converts at 11:00. The conversion happens 25 hours after the send, so it is counted in the **72 hours** and **7 days** windows, but not in the **24 hours** window.
{% endhint %}

Keep the following in mind when you change the window:

* The window changes only **Conversion** and **CR**. **Revenue** always comes from campaign counters and does not change.
* Fixed windows do not apply to continuous messages such as automations. Conversions for these messages are counted until the end of the selected date range.
* When you select **24 hours**, **72 hours**, or **7 days**, values are calculated in the background and **Calculating…** may appear briefly.

{% hint style="success" %}
To compare messages on equal terms, select the same fixed window for all of them.
{% endhint %}

### KPI cards

Five cards summarize the selected date range. Hover over the ⓘ icon on any card to read its definition.

<table><thead><tr><th width="174.69921875">Card</th><th width="360.75390625">What it shows</th><th>Shown below the value</th></tr></thead><tbody><tr><td><strong>Sent</strong></td><td>Number of messages sent</td><td>Failed rate (Failed ÷ Sent)</td></tr><tr><td><strong>Reach / Shown</strong></td><td><ul><li>Push: Sent minus Failed.</li><li>Email and SMS: Sent minus Failed minus Bounce.</li><li>WhatsApp: Delivered count reported by Meta.</li><li>Widget, popup, and in-app: number of impressions.</li></ul></td><td>—</td></tr><tr><td><strong>Click</strong></td><td>Number of clicks</td><td>CTR (Click ÷ Reach)</td></tr><tr><td><strong>Conversion</strong></td><td>Number of times the campaign's conversion event (with its conditions) occurred</td><td>CR (Conversion ÷ Reach) and the Measured event names</td></tr><tr><td><strong>Revenue</strong></td><td>Revenue attributed to messages through the revenue event</td><td><strong>Not defined</strong> if no revenue event exists</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FpyY0Rjf0XXLoztXXH4tG%2FEkran%20Resmi%202026-10-15%2015.12.55.png?alt=media&amp;token=b75a7150-a02d-4a6a-8a67-3677bce02cbf" alt="KPI cards measured with the OpenPush event and a 24-hour window"><figcaption><p>KPI cards with Conversion event set to OpenPush and a 24 hours window</p></figcaption></figure>

{% hint style="info" %}
**Example**: A push campaign sends 1,000,000 messages and 9,000 fail. The Failed rate is 0.9% and Reach is 991,000. With 26,000 clicks, CTR is 2.6%. With 14,900 conversions, CR is 1.5%.
{% endhint %}

A few details to keep in mind:

* The arrow and percentage on the Sent, Reach / Shown, Click, and Conversion cards show how the metric changed compared with the previous period.
* **Measured event** on the Conversion card lists the event names counted as conversions.
* Widgets have no clicks, and their Sent value equals their Shown count.
* Conversion counts events, not users. Because a user can convert more than once, CR can theoretically exceed 100%.
* **Delivered** is not a separate card; it appears as a column in the tables. The column is hidden when delivery data covers less than 5% of Reach. Delivered counts device-confirmed receipts over all time and is not the same as Reach.

### Daily Trend

**Daily Trend** plots Clicks (blue) and Conversion (green) for each day in the selected date range. Use it to see when engagement peaks and whether it is rising or falling.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FocuszFRXsxNfxS47rY8K%2FEkran%20Resmi%202026-10-15%2015.13.30.png?alt=media&amp;token=40e4ba1b-0a3d-4006-b68f-95d11dc548bb" alt="Daily Trend chart with Clicks and Conversion lines over 30 days"><figcaption><p>Daily Trend over a 30-day range</p></figcaption></figure>

* Click an item in the legend at the top left of the chart to hide its line. Click it again to bring it back. This is useful when one line is much larger than the other.
* Both lines share a single vertical scale, shown on the left.
* Peaks usually follow a large send. On some days Conversion can rise above Clicks, because Conversion counts events (a user can convert more than once) and widgets have no clicks.
* Conversion values for campaigns can arrive a few seconds after the rest of the page. Values for automations arrive immediately.
* The most recent days can look low, because data is still flowing in and, with a fixed window, the conversion windows for those days have not closed yet.

### Performance tables

The performance table below the Daily Trend shows the same metrics grouped in three different ways. Switch between groupings with the **Message**, **Channel**, and **Label** buttons in the top-right corner of the table; the table title changes accordingly (**Performance by Message**, **Performance by Channel**, **Performance by Label**).

Each view lists Sent, Failed, Reach / Shown, Click, CTR, and Conversion, followed by CR and Revenue. When delivery data covers at least 5% of Reach, a **Delivered** column is also added. If the table is wider than the screen, scroll right.

| View        | Each row                                                                               | View-specific columns                             |
| ----------- | -------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Message** | One message                                                                            | Title, Channel, Start Date                        |
| **Channel** | One channel (for example Push Android, Push iOS, Widget, Popup, In-app, SMS, Email)    | Messages (number of messages sent on the channel) |
| **Label**   | One label assigned to messages, plus an **Unlabeled** row for messages without a label | Messages (number of messages with the label)      |

Rows are sorted by Sent, from highest to lowest, by default. To sort by another column, click the arrows next to its header. The column used for sorting is highlighted.

In the tables, **—** means the value is not measured for that row (for example, Conversion and CR for a message without a conversion event, or Revenue when no revenue event is defined). **0** means the value is measured and no event occurred.

#### Message view

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FfjQrg01KdlyASyN9Lo1z%2FEkran%20Resmi%202026-10-15%2015.28.57.png?alt=media&amp;token=35031161-2656-41ee-b435-4613393170c6" alt="Performance by Message table sorted by CTR"><figcaption><p>Performance by Message, sorted by CTR</p></figcaption></figure>

* The view lists the 1,000 messages with the most sends. Click a message title to open that message's own report.
* If the selected range contains more than 5,000 messages, only the most recent 5,000 are included and a warning appears.
* Each message is counted once.

#### Channel view

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FtC78n2k044RMT1O9mglt%2FEkran%20Resmi%202026-10-15%2015.29.18.png?alt=media&amp;token=06df9bf9-7294-44a3-8bec-a6f0a883001e" alt="Performance by Channel table with Push Android, Push iOS, and Popup rows"><figcaption><p>Performance by Channel</p></figcaption></figure>

* Each message is counted once.
* The Widget row shows **—** for Click and CTR, because widgets have no clicks.
* Compare the Failed values across rows to spot a platform with noticeably more failed sends.

#### Label view

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FbEK4eryuiv8bPqfVO45i%2FEkran%20Resmi%202026-10-15%2015.30.48.png?alt=media&amp;token=b53d4443-b8f5-4186-a14b-45b241758c17" alt="Performance by Label table with a label row and the Unlabeled row"><figcaption><p>Performance by Label</p></figcaption></figure>

Click **+** next to a label to expand it and **−** to collapse it. The expanded row has two tabs: **Channels** lists the label's results by channel, and **Messages** lists the messages that carry the label.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FYIK3P67MO2PFd5Wy92RW%2FEkran%20Resmi%202026-10-15%2015.31.15.png?alt=media&amp;token=60c134b7-e1e0-49c8-8cc7-5ea2663a16d9" alt="Expanded label row showing the Channels tab"><figcaption><p>Expanded label row with the Channels tab</p></figcaption></figure>

* The **Label** button appears only when the app has labeled messages.
* Messages without a label are grouped under **Unlabeled**.
* A message can have more than one label, so label rows can overlap and do not necessarily add up to the totals. A note below the table repeats this.

### Reading the numbers correctly

* **Rates are based on Reach, not Sent.** CTR is Click ÷ Reach and CR is Conversion ÷ Reach. This means CR does not show what share of clickers converted.
* **CR can exceed 100%.** Conversion counts events, and a user can convert more than once.
* **Compare on the same basis.** If campaigns are measured differently, select a single fixed window to make Conversion and CR comparable.
* **Give conversions time.** A message whose window has not yet elapsed since the send can still earn conversions. Wait for its window to close before evaluating it.
* **Check Failed rate by channel.** If one platform shows a noticeably higher Failed rate than another in the Channel view, it is worth investigating the cause.
* **See the big picture with Label.** Label groups messages from the same campaign family into a single row, and the expanded row shows which channel or message drove the result. Because a message can have more than one label, do not add up label rows.

### FAQs and troubleshooting

<details>

<summary>Why does the Revenue card show "Not defined"?</summary>

No revenue event is defined, so revenue cannot be attributed to your messages. Once you define a revenue event, the card is populated.

</details>

<details>

<summary>Why does the Conversion card show "—"?</summary>

No conversion is being measured for the selected messages. This usually means the campaigns have no conversion event defined. Define a conversion event in the campaign, or select an event in the **Conversion event** filter to measure all messages by that event.

</details>

<details>

<summary>Why is Reach lower than Sent?</summary>

For push, Reach is Sent minus Failed. For email and SMS, it is Sent minus Failed minus Bounce. For WhatsApp, it is the Delivered count reported by Meta. Every message that fails, bounces, or is not delivered lowers Reach. The Failed rate below Sent shows this share.

</details>

<details>

<summary>Why do widgets show "—" for Click and CTR?</summary>

Widgets have no clicks. Their Sent value equals their Shown count, and their results are tracked through Conversion and CR.

</details>

<details>

<summary>Why does a message with many clicks show 0 conversions?</summary>

Either the message has no conversion event defined, or no matching event occurred after the message (within the window, if you selected a fixed window). Check the campaign's conversion event, the **Conversion event** filter, and the selected window.

</details>

<details>

<summary>Why did Conversion and CR change when I changed the conversion window?</summary>

The window determines which conversions are counted for each message. A longer window counts more, so numbers usually go up. Revenue does not change, because it always comes from campaign counters.

</details>

<details>

<summary>Why does the Conversion line rise above the Clicks line on some days?</summary>

Conversion counts events, and a user can convert more than once. Widgets also have no clicks at all.

</details>

<details>

<summary>Why do the most recent days look low?</summary>

Data is still flowing in, and the conversion windows for recent messages have not closed yet.

</details>

<details>

<summary>Why do I see "Calculating…" after changing the conversion window?</summary>

When you select **24 hours**, **72 hours**, or **7 days**, values are calculated in the background. They appear shortly after.

</details>

<details>

<summary>Why can't I see the Label button?</summary>

The Label button appears only when the app has labeled messages.

</details>

<details>

<summary>What is the Unlabeled row?</summary>

It groups all messages in the selected range that have no label, so you can compare labeled and unlabeled messaging side by side.

</details>

<details>

<summary>Why is there no Delivered column?</summary>

The column is hidden when delivery data covers less than 5% of Reach.

</details>

<details>

<summary>Why doesn't the Message view list all my messages?</summary>

The view lists the 1,000 messages with the most sends. If the date range contains more than 5,000 messages, only the most recent 5,000 are included and a warning appears.

</details>


---

# 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://user.netmera.com/netmera-user-guide/engagement-conversion.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.