Logs
Logs are a detailed view of what has happened on each of your requests, with vital information for you to further analyse and derive conclusions about the notifications sent, and to further improve your communication strategies.
Click Logs in the left navigation. It opens the Logs page, where we help you track each and every notification sent from Fyno. The other log types are listed under Logs in the left navigation, and you can open any of them from there.
This page covers the logs of every notification sent, how to filter them, and what each column contains.
The exact period depends on your workspace’s Data Retention setting. To review older notifications, request a report.
Logs
The logs visible on the 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:
Filtering by Status is especially useful when investigating failed or delayed notifications. For how statuses behave on each channel, see the Status Guide.
Using the logs table
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:
Search
Use the Search bar to look up a specific Message ID or Request ID to quickly locate an individual notification for debugging.
DND Period Logs report
To check which notifications went out during your Do Not Disturb (DND) window, request a DND Period Logs report. For how to generate it, which messages it includes, and how the DND window is selected, see the DND Period Logs section in Report Extraction.
Test & Live Versions
The Logs page keeps Test and Live data separate, so notifications you send while testing never inflate your live production figures.
- Check the environment. Switch to Test or Live, whichever the notification was sent from.
- Check the date. If the notification is older than your retention period, request a report instead.
Data Masking in logs
Logs can include sensitive information, such as destination details, header values, and data payloads. This information isn’t masked unless Data Masking is turned on for your workspace. An Owner or Super Admin can enable it from Workspace Settings > Security and choose a masking type. Once it’s enabled, sensitive values appear as masked text, such as xxxxx, across all log types, while Fyno keeps storing and processing the original values normally.
For more information, including masking types and how to enable or disable masking, see Data Masking.
Who can unmask data
- Owners and Super Admins can unmask data in logs by default.
- Team members with any other role see masked values and need the Unmask Sensitive Data add-on policy to reveal them.
- This add-on policy can be assigned from Workspace Settings > Team, either while inviting a team member or by modifying their access later.
For example, a Campaign Manager can access logs by default but sees sensitive values masked. If they need to unmask data, they should have the Unmask Sensitive Data add-on policy.
For details on roles and assigning this policy, see Unmask Sensitive Data.
Reveal or mask details
When Data Masking is enabled and you have permission to unmask data, you can switch between masked and visible values using the eye icon next to the title of a log page. The same icon appears next to the title in Log Details, so you can also do this while inspecting an individual log.
The icon shows whether details are currently masked. Hover over it to see a tooltip describing what clicking it will do.
To reveal masked details, click the eye with a line through it. The icon changes to an open eye and the original values are displayed. To mask them again, click the open eye.
Mask details again when you’ve finished reviewing a log, especially before sharing your screen or taking screenshots.

