# Outgoing

The **Outgoing** tab is a detailed registry of individual notifications sent to specific devices. Unlike general campaign reports, this section allows you to verify the status of a message for a single user (e.g., to check if a specific token received the notification).

### Search engine

Above the results table, there is a filter panel that allows you to precisely locate specific events. You can filter the list by:

* **Select range**: The time interval during which the dispatch was executed.
* **Device token**: The unique ID identifying the subscriber (application user).
* **Campaign name**: Search by the name of the dispatch.
* **Application**: Display logs only for the selected mobile application.

After setting the criteria, click the **Search** button.

### Notification list

The table presents logs at the individual recipient level. Each row contains key information:

* **Device token**: The recipient's token.
* **Sending time**: The exact date and time of the delivery attempt.
* **Application**: The name of the target application.
* **Campaign name**: The campaign from which the message originated.
* **Delivered**: Information about the successful transfer of the notification to the device.
* **Opening time**: The date and time the user clicked (opened) the notification.
* **Click time**: The date and time of interaction with a button or link inside the notification.

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

#### Message details

Clicking on any row in the table expands a panel with detailed information about the selected message.

### Data export

To download detailed logs to a file, click the **Export** button in the top right corner. The ready file can be found in the Account -> Operations list tab. The `.csv` file contains, among others: Device token, sending time, campaign and application name, as well as delivery and open statuses.

> Note: Full data on individual dispatches are available for 40 days from the moment of campaign execution.


---

# 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://docs.messageflow.com/mobile-push/push-campaigns/outgoing.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.