For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginTalk to us
DocumentationSDKsConnectAPI Reference
DocumentationSDKsConnectAPI Reference
    • Home
    • Release Notes
  • Getting Started
    • Quickstart
    • Dashboard
    • Alarms
    • Versioning
  • Core Features
    • Integrations
    • Templates
    • Routes
    • Notification Events
    • Requests/Go Live
    • Logs
      • Sent Logs
      • Log Details
        • Trace
        • Summary
        • Placeholders
        • Content
        • Response
        • Delivery
      • Inbound logs
  • Advanced Features
    • Workflows
    • Campaigns
    • User Profiles
    • Approval Request
  • Settings
    • Profile Settings
    • Workspaces
    • Workspace Settings
LogoLogo
LoginTalk to us
On this page
  • Delivery Status Sent, No Extra Configuration
  • Delivery Status can be Sent, Configuration Needed
  • Delivery Status Not Sent, Configuration not available
Core FeaturesLogsLog Details

Tracking Notification Delivery Status in Logs

Was this page helpful?
Previous

Tracking User Responses with Inbound Conversation Logs

Next
Built with

On the “Log Details” pop-up, the fifth tab on the ribbon menu you will see is “Delivery”.

The delivery tab is dependent on the information relayed from the providers. You will see a delivery status tab only for providers who send the Delivery Status.

The Delivery tab will show you the details of the delivery response that Fyno has received from the “Provider” that was used to send the notification.

This tab may not be visible in cases where Fyno has not received any information from the “Provider” about Delivery Status

On that note, let’s have a quick look at the types of Providers based on the Delivery Status

  • Delivery status sent, with no extra configuration needed.
  • Delivery status can be sent, configuration required
  • Delivery status not sent, configuration not available

Delivery Status Sent, No Extra Configuration

There are providers within some services that readily share the delivery status of the notification without having to configure webhooks or callbacks at their end. They are:

  • Messaging (SMS)
    • Exotel
    • Kaleyra Global
    • Kaleyra.io
    • MessageBird
    • Plivo
    • Twilio
    • ValueFirst
  • WhatsApp
    • Freshchat
    • MessageBird
    • Twilio
    • ValueFirst
  • InApp
  • Push
    • Expo
    • FCM
    • Mi Push
    • OneSignal

Delivery Status can be Sent, Configuration Needed

Some other providers need to be configured to send the delivery status. For these Providers, once configured the delivery tab will show up in logs. These are:

  • Messaging (SMS)
    • Gupshup
    • Karix
    • MSG91
    • RouteMobile
    • Syniverse
  • WhatsApp
    • Connectly
    • Kaleyra.io
    • Gupshup Enterprise
    • Meta (by Facebook)
  • Email
    • Mailchimp (Mandrill)
    • Mailgun
    • Netcore
    • PostMark
    • SendGrid
    • SES

However, there are a few providers that don’t provide the delivery status and we will be unable to fetch that data. We would request you to check with your provider for more details on the same.

Delivery Status Not Sent, Configuration not available

Some providers do not have the feasibility to share the delivery status, and thus this cannot be shared. For these providers, the Delivery tab will not be visible. They are:

  • WhatsApp
    • AiSensy
  • Email
    • Gmail
    • Outlook
  • Chat
    • Slack
    • Teams (by Microsoft)