Skip to main content

Mark Messages as Delivered

You can mark the messages for a particular conversation as read using the markAsDelivered() method. This method takes the following parameters as input: Messages for both user & group conversations can be marked as read 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 ID of that 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 ID of the message and pass it to the markAsDelivered() method.
This method will mark all the messages before the messageId specified, for the conversation with receiverId and receiverType(user/group) as read. 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:
Another option the CometChat SDK provides is to pass the entire message object to the markAsDelivered() method.
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:
Starting v3, the messages will not be marked delivered internally by the SDK. You will have to use the markAsDelivered() method. You will either have to use one of the above method signatures to mark the messages as delivered.

Mark Messages as Read

You can mark the messages for a particular conversation as read using the markAsRead() method. This method takes the following parameters 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 ID of that 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 ID of the message and pass it to the markAsRead() method
This method will mark all the messages before the messageId specified, for the conversation with receiverId and receiverType (user/group) 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:
Another option the CometChat SDK provides is to pass the entire message object to the markAsRead() method.
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:
Starting v3, the markAsRead() method working with v2.x is deprecated and will not work. You will either have to use one of the above method signatures to mark the messages as read.

Mark Messages as Unread

Use markMessageAsUnread() to mark a message as unread. All messages below that message in the conversation will contribute to the unread count. On success, returns an updated Conversation object.

Receive Delivery & Read Receipts

Real-time events

  1. onMessagesDelivered() - This event is triggered when a message is delivered to a user.
  2. onMessagesRead() - This event is triggered when a message is read by a user.
  3. onMessagesDeliveredToAll() - This event is triggered when a group message is delivered to all members of the group. This event is only for Group conversations.
  4. onMessagesReadByAll() - This event is triggered when a group message is read by all members of the group. This event is only for Group conversations.
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.
You will receive a list of MessageReceipt objects in the onSuccess() method.
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.
Always remove message listeners when they’re no longer needed (e.g., in onDestroy() or when navigating away). Failing to remove listeners can cause memory leaks and duplicate event handling.

MessageReceipt Payload Structure

The MessageReceipt object contains information about message delivery and read status:Sample MessageReceipt Object:
The nested User object in sender contains:

Next Steps

Typing Indicators

Show when users are typing

Receive Messages

Handle incoming messages with listeners

Retrieve Conversations

Fetch conversation list with unread counts

Real-Time Listeners

Learn more about event listeners