Delivery receipt

Delivery receipt is a feature that indicates whether a message has successfully been delivered to all the intended recipients by Sendbird server. With the implementation of delivery receipt, Sendbird not only provides the timestamp of when each user has last read the messages in each channel, but also the timestamp of when each user has the message last delivered to each user in each channel.

To view the image in full screen, click on the

Note: Delivery receipt is only applicable to group channels.

Delivery receipt provides the following benefits.

Most popular messaging apps, such as WhatsApp and Facebook Messenger, provide this feature. Users who have experienced them expect to see if the message they sent has been successfully delivered when using a new chat service. Delivery receipt is a feature in high demand that today’s users are accustomed to using.

Previously, a sender had no way of knowing whether their message was unread because the server is in the process of delivering or failed to deliver the message due to the unreliable internet connection, or simply because the recipients haven’t yet read the message. This feature enables users to become better-informed, thus improving the Sendbird user experience.

Delivery receipt works in a similar way to read receipt. The server stores the timestamp of the message last delivered as delivered_ts. The timestamp is recorded per user, per channel.

Each SDK provides methods to make the Chat API's mark all messages as delivered action calls. If required, each SDK also makes necessary changes to handle the new response key, delivery_receipt, for APIs that return a group channel resource.

When a user sends a message to a group channel by calling the SDK’s sendUserMessage() method, it is considered a delivery event for Sendbird server.

To mark messages as delivered when an online group channel member receives the message from Sendbird server, the markAsDelivered() method should be called. For offline group channel members, the markAsDelivered() should be called when they come back from the background or go back online.

var sb = new SendBird({appId: APP_ID});
...

sb.markAsDelivered(CHANNEL_URL);

var sb = new SendBird({appId: APP_ID});
...

sb.GroupChannel.getChannel(CHANNEL_URL, (channel, error) => {
    if (error) {
        // Handle error.
    }

    channel.markAsDelivered();
    ...
});

When a message is delivered to an online group channel member, it is automatically marked as delivered and the other online members are notified of delivery receipt through the onDeliveryReceiptUpdated() method in the channel event handler. However, when it is delivered to an offline group channel member as a push notification, the message can be marked as delivered through the groupChannel.markAsDelivered(), and other online members are notified of the delivery receipt through the onDeliveryReceiptUpdated().

const channelHandler = new sb.ChannelHandler();
channelHandler.onDeliveryReceiptUpdated = channel => {
    // console.log(channel);
};

sb.addChannelHandler(UNIQUE_HANDLER_ID, channelHandler);

You can retrieve the number of members who haven’t received a specific message in a group channel. If zero is returned, it means that the message has been delivered to all the other members.

const param = new sb.GroupChannelParams();
param.addUsers([USER_2, USER_3]);

sb.GroupChannel.createChannel(param, (channel, error) => {
    if (error) {
        // Handle error.
    }

    channel.sendUserMessage('Hi Sendbirdians!', (message, error) => {
        if (error) {
            // Handle error.
        }

        int numberOfUndeliveredMembers = channel.getUndeliveredMemberCount(message);    // The number of members who haven’t received the message.
        ...
    });
});