Skip to main content
Delivery and read receipts allow you to track when messages have been delivered to and read by recipients, providing real-time feedback on message status.
Available via: SDK | REST API | UI Kits

Mark Messages as Delivered

In other words, as a recipient, how do I inform the sender that I’ve received a message? You can mark the messages for a particular conversation as delivered using the markAsDelivered() method. This method takes a BaseMessage object as input. Messages for both user & group conversations can be marked as delivered using this method. Ideally, you would like to mark all the messages as delivered for any conversation when the user opens the chat window for that conversation. This includes two scenarios:
  1. When the list of messages for the conversation is fetched: In this case you need to obtain the last message in the list of messages and pass the message to the markAsDelivered() method.
  2. When the user is on the chat window and a real-time message is received: In this case you need to obtain the message and pass it to the markAsDelivered() method.
This method will mark all the messages before the message specified, for the conversation with receiverId and receiverType (user/group) as delivered. In case you would like to be notified of an error if the receipts fail to go through you can use markAsDelivered() method with the callbacks as shown below:
On Success — A String message confirming the message has been marked as delivered:

Mark Messages as Read

In other words, as a recipient, how do I inform the sender I’ve read a message? You can mark the messages for a particular conversation as read using the markAsRead() method. This method takes a BaseMessage object as input. Messages for both user and group conversations can be marked as read using this method. Ideally, you should mark all the messages as read for any conversation when the user opens the chat window for that conversation. This includes two scenarios:
  1. When the list of messages for the conversation is fetched: In this case you need to obtain the last message in the list of messages and pass the message to the markAsRead() method.
  2. When the user is on the chat window and a real-time message is received: In this case you need to obtain the message and pass it to the markAsRead() method
This method will mark all the messages before the message specified, for the conversation with receiverId and receiverType (user/group) as read. Another option the CometChat SDK provides is to pass the entire message object to the markAsRead() method. If the message object is the last message, the entire conversation will be marked as read.
In case you would like to be notified of an error if the receipts fail to go through you can use the markAsRead() method with the callbacks as shown below:
On Success — A String message confirming the message has been marked as read:

Mark Messages as Unread

The Mark as Unread feature allows users to designate specific messages or conversations as unread, even if they have been previously viewed. This feature is valuable for users who want to revisit and respond to important messages or conversations later, ensuring they don’t forget or overlook them. In other words, how I can mark message as unread? You can mark the messages for a particular conversation as unread using the markMessageAsUnread() method. Example: When User B sends User A a total of 10 messages, and User A invokes the markMessageAsUnread() method on the fifth message, all messages located below the fifth message within the conversation list will be designated as unread. This results in a notification indicating there are 5 unread messages in the conversation list.
On Success — A Conversation object with the updated unread message count:

Receive Delivery & Read Receipts

In other words, as a recipient, how do I know when a message I sent has been delivered or read by someone?

Real-time Events

Register a MessageListener to receive delivery and read receipt events.
Always remove listeners when they’re no longer needed (e.g., in the dispose() method). Failing to remove listeners can cause memory leaks and duplicate event handling.
You will receive events in the form of MessageReceipt objects. The message receipt contains the following parameters:

Missed Receipts

You will receive message receipts when you load offline messages. While fetching messages in bulk, the message object will have two fields i.e. deliveredAt and readAt which hold the timestamp for the time the message was delivered and read respectively. Using these two variables, the delivery and read status for a message can be obtained. However, for a group message, if you wish to fetch the deliveredAt and readAt fields of individual member of the group you can use the below-described method.

Receipt History for a Single Message

To fetch the message receipts, you can use the getMessageReceipts() method. This is useful for group messages to see which members have received/read the message.
On Success — A List<MessageReceipt> containing receipt details for each group member:
You will receive a list of MessageReceipt objects in the onSuccess() callback.
The following features will be available only if the Enhanced Messaging Status feature is enabled for your app.
  • onMessagesDeliveredToAll event,
  • onMessagesReadByAll event,
  • deliveredAt field in a group message,
  • readAt field in a group message.
  • markMessageAsUnread method.

Next Steps

Receive Messages

Handle incoming messages in real-time

Typing Indicators

Show when users are typing

Retrieve Conversations

Fetch conversation list with unread counts

All Real-Time Listeners

Complete reference for all SDK event listeners