Tracking and Exporting Sent Notification Logs

Sent logs are where we help you track each and every notification sent from Fyno. Logs provide a detailed view of what has happened to each of your requests, supplying vital information for you to analyze, derive conclusions about your sent notifications, and continuously improve your communication strategies.

This section covers the logs visible on the Fyno platform, how to filter through the application to narrow down your searches, and a comprehensive breakdown of individual log schemas.

When you navigate to Sent Logs from the left navigation menu, you will see the following sections:

Logs
Test & Live Versions

Logs

The logs visible on the Sent Logs page give you a chronological overview of the latest interaction activity occurring on your Fyno account.

When you review your logs, the primary indicator is the Status indicator. This flag marks exactly where your request stands within the system lifecycle:

Status	Description
Attempted	Message request was successfully validated by Fyno and routing logic has been initiated toward the provider.
Sent	Message request was processed successfully by the provider and dispatched into the delivery network.
Dropped	Message was dropped internally due to preset rules (e.g., Suppression lists, Routing caps, or Subscription opt-outs).
Error	Message failed internally at Fyno’s layer before reaching the network provider gateway.
Failed	Message processing completely failed or validation checks were rejected at provider’s end.
Timeout	Downstream gateway/provider failed to respond or acknowledge the payload within the 5–10 second window.
Delivered	Message reached the destination device successfully.
Undelivered	A definitive undelivered event payload was reported back asynchronously by the carrier network.
Clicked	An embedded URL/Link or the action button in the message was clicked by the user.
Read / Open	Message container was explicitly opened or flagged as read by the recipient.
No DLR	Message was dispatched, but the network carrier did not return a Delivery Receipt acknowledgment.

Use the Status filter to narrow logs down to any of these statuses, or select All. This is particularly useful when investigating failed or delayed notifications.

You can read about the extensive multi-channel delivery matrices in detail here.

Understanding the Log Schema Columns

Each column in the logs table contains the following data, along with the filters you can use to narrow down results:

Column	What it shows	Filter by
Timestamp	Exact date and time when the notification request was initiated from your application.	Date Range: Today, Yesterday, Last 7 days, Last 28 days, or a custom range.
Template	Template name and content layout used when the notification request was fired.	Template for logs from specific templates. Placeholders for logs containing a specific placeholder value in the notification payload.
Notification Event	Name of the Event configuration triggered by the notification API request made to Fyno.	Event Name for logs of a specific event across all configured channels and providers.
Destination	Recipient’s address, along with the Channel used to deliver the message.	Destination for notifications sent to a specific recipient. Channel for SMS, WhatsApp, Email, Push, Chat, or In-App notifications.
Provider	Provider used to route and send the message.	Provider for notifications sent through a specific provider. Account Name for a particular account, if you have multiple accounts under a provider.

Make sure to configure your regional time zone within Settings so that log outputs display correctly in your local time format.

Search

Use the Search bar to look up a specific Message ID or Request ID to quickly locate an individual notification for debugging.

How to download sent logs

Open the report form

Click Request Report at the top right of the Sent Logs page.

Choose your targeted report parameters, API version scopes, and chronological boundary limits in the configuration modal.

Version: Select between Test or Live.
Timestamp: Quick-select fields (Yesterday, Last 7 days, Last 28 days) or select Custom (choose any 30-day window within the trailing 6 months).
Report Type: Select one of the 4 available structures based on audit requirements:

Report type	What it contains
All Logs	Comprehensive metadata dump of raw request strings.
Summary	Aggregated deliverability statistics.
Daily Summary	Day-over-day tracking charts.
SMS Delivery (mobile number-wise)	Destination-specific delivery data.

Data exports are capped at 30 days per report. If you need to export an extended sequence (e.g., 90 days), create multiple separate sequential reports (e.g., Day 1 to 30, Day 31 to 60, and Day 61 to 90).

You will see an InApp confirmation bubble processing banner status alert: “Your report request xxxxx_xx is processing!”

Most optimized reports finish compilation within a few seconds.

Wait for the report

When the report is ready, you’ll see a notification on the platform and receive an email with a Download Report link.

Open your reports

Click Download Report to open the list of your generated reports.

Download the file

Click the download link next to your report to save the file.

Be sure to download your compiled reports within 7 days, as download tokens auto-expire securely. For instance, a report file ready on March 1st at 1:00 PM will become unavailable on March 8th at 1:00 PM.

Test & Live Versions

The logs dashboard cleanly segments reporting data channels between Test and Live environmental pipelines. This prevents development testing records from inflating operational live production audit figures.

Can't find a notification log?

Check the environment. Notifications sent in Test don’t appear in Live logs, and vice versa.
Check the date. Logs are visible on this page for 7 days by default, or for the period set in your workspace’s Data Retention setting. For anything older, request a report.