> ## Documentation Index > Fetch the complete documentation index at: https://kero.chat/help/llms.txt > Use this file to discover all available pages before exploring further. # Understand Campaign Delivery Reports > Learn how to view campaign results, understand delivery and fallback counts, investigate failed messages, and export your campaign report. After sending a campaign, you can track its delivery results, review individual message records, and investigate messages that were not delivered. Kero displays both a summary of your campaign's message statuses and a detailed list of sending attempts. ## View your campaign results **1. Open Campaigns** From the Kero navigation menu, select **Campaigns**. **2. Find your campaign** Locate the campaign in the list. Use the **Today**, **Yesterday**, **Week**, **Month**, **Year**, or **Custom** filters if needed. These filters use the date the campaign was created. **3. Open the campaign report** Click the campaign's **Created Time** to open its details. The report displays a status summary at the top and individual message records below. ## Understand the campaign summary The counters at the top of the report show the current message statuses and fallback activity. ![Campaign delivery report showing message status totals and individual message records](https://mintlify.s3.us-west-1.amazonaws.com/kerochat/images/campaign-delivery-report.png) | Status | What it means | | - | - | | **Sent** | Messages that have been sent but have not yet received a final delivery outcome. | | **Delivered** | Messages reported as delivered to the recipient. | | **Read** | Messages reported as read, where the messaging channel supports read receipts. | | **Failed** | Messages that could not be delivered successfully. | | **Fallback** | Original messages that triggered a fallback attempt through another configured channel agent. | > [!NOTE] > > **Fallback is not a delivery outcome.** It shows how many original messages triggered fallback, regardless of whether those fallback attempts were ultimately delivered. > > Do not add the Fallback count to Delivered or Failed when calculating successful deliveries. Delivery statuses can change as Kero receives updates from messaging providers. Click **Refresh** to retrieve the latest available results. For more information about individual statuses, see [Understand Message Delivery Statuses](https://kero.chat/help/understand-message-delivery-statuses). ## Understand campaigns with fallback If your campaign uses a template with fallback enabled, Kero may attempt delivery through more than one channel agent. For example, a WhatsApp message might trigger an SMS fallback attempt if the primary channel cannot deliver it. Each sending attempt appears as a separate record in the campaign report. ### Example: Four messages with fallback A campaign contains four original messages. All four trigger fallback to SMS. The campaign report might show: | Status | Count | | - | -: | | Sent | 0 | | Delivered | 3 | | Read | 0 | | Failed | 1 | | Fallback | 4 | In this example: * **4 original messages** triggered fallback. * **3 fallback attempts** were delivered. * **1 fallback attempt** failed. * **8 message records** appear in the report: four primary-channel attempts and four fallback attempts. The number of rows can therefore be greater than the number of original campaign messages. > [!NOTE] > > A record with the status `fallback_sent` indicates that fallback sending was triggered. It does not confirm delivery. > > Check the corresponding fallback-channel record for its delivery outcome. To learn how to configure the order of fallback agents, see [Configure Message Fallback](https://kero.chat/help/configure-message-fallback). ## Review individual message records Below the campaign summary, Kero displays the message records associated with the campaign. | Column | Description | | - | - | | **Sent Time** | When the message attempt was sent. | | **To** | The recipient's mobile number. | | **Brand Agent** | The channel agent used for that sending attempt. | | **Ref** | The message reference used to identify related records. | | **Updated** | When the message status was last updated. | | **Status** | The current status of the sending attempt. | | **Reason** | Additional information about a failed message, when available. | When fallback is used, related records can share the same **Ref** while showing different channel agents and statuses. This helps you follow the message from its primary-channel attempt to its fallback attempt. ## Investigate failed messages If your campaign contains failed messages: **1. Find the failed record** In the campaign report, look for a row with the status **failed**. **2. Check the reason** Review the **Reason** column for additional information. The information available depends on the response received from the messaging provider. **3. Check for fallback** If the campaign uses fallback, look for another record with the same **Ref**. Check whether the fallback-channel attempt was delivered or also failed. **4. Refresh the report** Click **Refresh** to retrieve any newer delivery status updates. A failed primary-channel attempt does not necessarily mean the recipient received no message. A fallback attempt may have succeeded. Similarly, a `fallback_sent` record does not guarantee successful delivery. For more detailed investigation of individual messages, see [Manage Your Sent Messages](https://kero.chat/help/manage-your-sent-messages). ## Export campaign results You can download the campaign's message records as a CSV file for further analysis or recordkeeping. **1. Open the campaign** On the **Campaigns** page, click the campaign's **Created Time**. **2. Download the report** Click the **download icon** above the message records table. Kero downloads the message records as a CSV file. > [!NOTE] > > The export contains message records, including individual fallback attempts where applicable. The number of exported records may therefore exceed the number of original campaign messages. ## Reports for scheduled campaigns If a campaign is scheduled but has not started sending, delivery results are not yet available. The campaign details page displays its scheduled sending date and time. Once the campaign has started sending, return to its details page to review the available results. For instructions on creating, cancelling, or replacing a scheduled campaign, see [Schedule a Campaign](https://kero.chat/help/schedule-a-campaign). ## Keep your campaign results up to date Message delivery information may not be available immediately after sending. To check for updates: 1. Open the campaign report. 2. Click **Refresh**. 3. Review the updated summary counters and message statuses. Click **Back** to return to the Campaigns list. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.