# Push Reports

Push Reports shows how a push campaign performs from delivery to outcome. It helps you understand not only whether the push was delivered, but also whether it drove clicks, sessions, conversion, and revenue afterward.

Use it to answer four practical questions:

* Did the message reach the intended audience?
* Did users click and open the app?
* Did the campaign drive conversions or revenue?
* Which platforms, segments, or attributes performed best?

{% @arcade/embed url="<https://app.arcade.software/share/1xW1zpafx6O5Lf02ChkF>" flowId="1xW1zpafx6O5Lf02ChkF" %}

### Push notification summary

The summary section gives you the campaign context before you inspect the numbers.

* **Campaign name** and **Message ID** — the campaign title and its unique system identifier. Use them to confirm you are reviewing the correct message.
* **Message type** — the category of push message being sent. This helps identify how the campaign is configured and delivered.
* **Message text** — the push content shown to users. Use it to verify the exact message and call to action.
* **Creator** — the user who created the campaign. This is useful when you need ownership or setup context.
* **Method** — how the audience was selected, such as broadcast or targeted delivery. Use it to understand whether the campaign was sent broadly or to a defined audience.
* **Campaign status** — the current delivery state, such as sending or finished.
* **Create**, **Start**, and **End** times — the timestamps for when the campaign was created, when sending started, and when sending ended.

<figure><img src="/files/xdrXAWlXt2vEyeBjSPk2" alt=""><figcaption></figcaption></figure>

Use this area to confirm you are reading the right campaign and targeting setup. This becomes especially important when several similar campaigns ran in the same period.

### Core metrics

The overview cards show the main delivery and engagement metrics for the campaign.

<figure><img src="/files/ivWJMA5x5dDpbru3NMrW" alt=""><figcaption></figcaption></figure>

Key metrics:

* **Target Audience** — the total audience selected for the campaign. This is the intended reach before delivery starts.
* **Users** — the number of unique users who received the push. Use this to compare intended reach with actual reach.
* **Sent** — the total number of push notifications dispatched. This shows message volume entering the delivery pipeline.
* **Success** — the number of notifications delivered successfully. Low success usually points to delivery or token issues.
* **Clicked** — the click rate for the notification. Use it to measure message relevance and call-to-action strength.
* **Avg. Time In App** — the average time users stay in the app after clicking. This shows post-click engagement quality.
* **Hot Conversion** — the number of users who completed the campaign goal after clicking.
* **Hot Revenue** — the revenue generated by users who converted after clicking.
* **Push Clicks** — the total number of push clicks for the campaign. This counts interaction volume, not just unique converters.

Read these metrics together rather than in isolation. For example, high delivery with low clicks often points to message relevance or timing, while strong clicks with weak conversion usually points to what happens after the click.

{% hint style="warning" %}
To see **Hot Conversion** and **Hot Revenue**, define a conversion event during campaign creation. Set it in [Notification Content: What](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/what.md) while building the push campaign.
{% endhint %}

### Push clicks chart

The hourly chart helps you measure impact over time. It is useful when you want to understand whether the push created an immediate spike, a delayed response, or almost no reaction at all.

You can switch between:

* **Push Clicks**
* **Sessions**
* **Revenue**

The vertical marker shows when the push was sent.

Use it to compare activity before and after delivery. In many cases, this is the fastest way to see whether the campaign changed user behavior meaningfully.

<figure><img src="/files/qxBEgK6Mgey8QqbtekxX" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The chart uses the app session duration configured in **Developers App Info → Session Expire Interval**. The default value is **180 seconds**.
{% endhint %}

{% hint style="success" %}
Click **Export to Excel** to download the hourly chart data.
{% endhint %}

### View message details

The message details section shows exactly what was configured for the campaign.

<figure><img src="/files/mdAOl6sDnG7sm7fEEPkR" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/zgZKK4QxIdH9vhlp8YBu" alt=""><figcaption></figcaption></figure>

Review this section to verify:

* target platforms,
* notification content,
* schedule and delivery speed,
* click action,
* sound or vibration settings,
* and conversion tracking setup.

This section is especially useful when the numbers look unexpected. Before you investigate performance deeply, it is worth checking that the delivery logic and campaign settings match what you intended to send.

### Performance breakdowns

These sections help you compare performance by platform, audience definition, and downstream behavior. This is where campaign analysis becomes more diagnostic and less top-line.

#### Push clicks by platform

This table breaks results down by **Total**, **iOS**, and **Android**.

<figure><img src="/files/WJJvQah9H1x62NzqaC74" alt=""><figcaption></figcaption></figure>

It includes:

* **Sent**, **Success**, and **Failed**
* **Clicked** and **Not-Clicked**
* **Conversion**
* revenue windows for **1 hour**, **3 hours**, **12 hours**, and **24 hours**

Use it to spot platform-specific delivery or engagement gaps. For example, if iOS clicks strongly and Android lags, the issue may be related to audience quality, rendering, timing, or platform-specific behavior.

#### Inbox stats

Inbox stats shows how users interact with pushes stored in the inbox.

<figure><img src="/files/gplxhHswdPXsX2F6WkSG" alt=""><figcaption></figcaption></figure>

Field definitions:

* **Read** — the number of inbox messages users opened.
* **Unread** — the number of inbox messages that remain unopened.
* **Deleted** — the number of inbox messages users removed.

Use these fields to understand whether stored push messages were viewed, ignored, or dismissed. This matters when inbox visibility is part of the campaign strategy, not only the initial notification.

Review this section when inbox visibility matters for your campaign.

#### Events in push session

This section shows actions users took during sessions started by the push. It helps you move beyond the click and understand what users actually did after entering the app.

<figure><img src="/files/RoQAl0MnGEIZPWDmBcvk" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This section stays empty when no tracked events exist for the selected campaign, or when the SDK is not sending those events.

It can also stay empty when the selected time range has no qualifying activity.
{% endhint %}

#### Push clicks by profile attributes

This table compares performance across a selected profile attribute.

<figure><img src="/files/aDrBsXa4MxsxBJLVL4Ff" alt=""><figcaption></figcaption></figure>

Field definitions:

* **Sent** — the total number of notifications associated with that profile attribute value.
* **Success** — the number of notifications delivered successfully for that group.
* **Failed** — the number of notifications that could not be delivered for that group.
* **Clicked** — the number of delivered notifications clicked by users in that group.
* **Not-Clicked** — the number of delivered notifications not clicked by users in that group.
* **Conversions** — the number of users in that group who completed the selected conversion event.
* **Revenue Total** — the total revenue generated by users in that group after the push.
* **Revenue Per User** — the average revenue generated per user in that group.

Use it to find which customer traits respond best. For example, one membership tier or one city may convert better even if overall click performance looks average.

#### Push clicks by segment

This view compares push performance across segments.

{% hint style="info" %}
If the campaign audience is not tied to segment data, this report may stay empty.
{% endhint %}

<figure><img src="/files/9O2objKVzpK7ZoFeJqES" alt=""><figcaption></figcaption></figure>

Field definitions:

* **Sent** — the total number of notifications associated with that segment.
* **Failed** — the number of notifications that could not be delivered to users in that segment.
* **Clicked** — the number of delivered notifications clicked by users in that segment.
* **Not-Clicked** — the number of delivered notifications not clicked by users in that segment.
* **Conversions** — the number of users in that segment who completed the selected conversion event.
* **Revenue Total** — the total revenue generated by users in that segment after the push.
* **Revenue Per User** — the average revenue generated per user in that segment.

These fields show delivery, engagement, conversion, and revenue by segment. This is useful when the same campaign performs differently across lifecycle or value groups.

#### Heatmap

The heatmap shows where delivery density is highest. It gives you a visual summary of where successful delivery concentrated, which can help when you review time-based or distribution-based patterns.

Warmer colors show higher successful delivery volume.

Cooler colors show lower delivery volume.

<figure><img src="/files/UbZQkwdzB9GNKnPwsatm" alt=""><figcaption></figcaption></figure>

### Conversion and revenue

These sections show whether the campaign drove the outcome you care about. In other words, they help answer whether the push created business value, not only interaction.

For broader campaign analysis, also see [Revenue & Conversion](/netmera-user-guide/reports-and-analytics/analytics/revenue-and-conversion.md).

#### Conversion

The conversion report breaks results down by user group and time window. This makes it easier to distinguish immediate campaign impact from delayed downstream behavior.

User groups:

* **Received Push** — users who received the push successfully. They may or may not have clicked it.
* **Clicked Push** — users who clicked the push. This is the most engaged exposed audience.
* **Control Group** — users intentionally excluded from the campaign and used as a baseline.
* **Not In Target** — users outside the campaign audience.
* **Total** — the aggregated result for the full report.

Time window definitions:

* **In Push Session** — actions completed during the session started by the push interaction.
* **1 Hour** — actions completed within one hour after the push.
* **3 Hours** — actions completed within three hours after the push.
* **12 Hours** — actions completed within twelve hours after the push.
* **24 Hours** — actions completed within twenty-four hours after the push.

<figure><img src="/files/UPK5e2kLkTH3oGkgijVQ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The conversion and revenue tables use the app session duration configured in **Developers App Info → Session Expire Interval**. The default value is **180 seconds**.
{% endhint %}

<figure><img src="/files/CZ1qrOyPBQfXGSsAsInX" alt="" width="563"><figcaption></figcaption></figure>

#### Revenue

The revenue report uses the same user groups and time windows.

The same group definitions apply here:

* **Received Push** shows revenue from delivered users.
* **Clicked Push** shows revenue from users who clicked.
* **Control Group** shows baseline revenue without campaign exposure.
* **Not In Target** shows revenue from users outside the target audience.
* **Total** shows the overall reported revenue.

<figure><img src="/files/uioIfDhB12S6hLEZZpmj" alt=""><figcaption></figcaption></figure>

Use it to compare immediate and delayed revenue impact after a push. For example, some campaigns produce quick revenue inside the push session, while others influence purchases later in the day.

{% hint style="warning" %}
Conversion and revenue data require a conversion event in [Create Mobile Push](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push.md). If no conversion event is set, these sections remain empty.
{% endhint %}

### Event insight

Event Insight helps you analyze specific actions after the push. Use it when you need more detail than the standard report tables provide.

You can also use the dedicated [Event Insight](/netmera-user-guide/customer-data/events/event-insight.md) page for broader event analysis.

<figure><img src="/files/n9ENvVfbt5ZgnKI3cAkm" alt=""><figcaption></figcaption></figure>

Use filters to narrow the analysis by:

* users who **received** the push,
* users who **clicked** the push,
* time window,
* and event name.

You can then break the result down by dimensions such as:

* **External ID**
* **Month**

This is useful when you want to identify which users clicked, which users converted, or which post-push events happened most often.

<figure><img src="/files/tWzRQvLmMsPsvSTCW9t7" alt=""><figcaption></figcaption></figure>

Click **Export to Excel** to download the result set.

### FAQs

<details>

<summary>How do I enable conversion and revenue data?</summary>

Set a conversion event while creating the push campaign. Configure it in [Notification Content: What](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/what.md). Revenue appears when the selected conversion event carries revenue data.

</details>

<details>

<summary>Why is a report section empty?</summary>

The most common reasons are:

* no data exists for the selected campaign,
* the SDK is not sending the required events,
* no segment or profile data is available for that view,
* conversion tracking was not configured,
* the selected campaign has no recipients in that segment or attribute group,
* or the selected time range has no qualifying activity.

</details>

<details>

<summary>What does the control group mean?</summary>

The control group contains users excluded from the push. It helps measure incremental lift by comparing exposed users with unexposed users.

</details>

<details>

<summary>Can I export push report data?</summary>

Yes. You can export data from the hourly chart and from Event Insight. Use **Export to Excel** where available.

</details>


---

# 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://user.netmera.com/netmera-user-guide/reports-and-analytics/reports/campaigns/push-reports.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.