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
• Filters (detailed in the next guide section)

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:

• 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 Fyno’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.

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

Understanding the Log Schema Columns

To further analyze this page, let’s look at what data each column contains:

Timestamp

Shows the exact date and time details of when the notification request was initiated from your application.

Template

Displays the specific template name and unique content layout structure utilized when the notification request was fired.

Notification Event

Displays the corresponding core Event configuration name triggered with the notification API request made to Fyno.

Destination

Provides a concise snapshot of the target recipient endpoint routing address, alongside the primary communication Channel utilized to complete the payload delivery.

Provider

Identifies the exact integrated downstream provider gateway service instance deployed to route and transmit the message payload.

How to download sent logs

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.