Quick Reference - Mark messages and listen for receipts:
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 read using themarkAsDelivered() method. This method takes the below parameters as input:
| Parameter | Information |
|---|---|
messageId | The ID of the message above which all the messages for a particular conversation are to be marked as read. |
receiverId | In case of one to one conversation message’s sender UID will be the receipt’s receiver Id. In case of group conversation message’s receiver Id will be the receipt’s receiver Id. |
receiverType | Type of the receiver. Could be either of the two values( user or group). |
senderId | The UID of the sender of the message. |
- 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.
- 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.
- To User
- To Group
- TypeScript (User)
- TypeScript (Group)
.then(successCallback, failureCallback) of the markAsDelivered method.
- To User
- To Group
- TypeScript (User)
- TypeScript (Group)
- JavaScript
- TypeScript
.then(successCallback, failureCallback) of the markAsDelivered method.
- JavaScript
- TypeScript
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 themarkAsRead() method. This method takes the below parameters as input:
| Parameter | Information |
|---|---|
messageId | The ID of the message above which all the messages for a particular conversation are to be marked as read. |
receiverId | In case of one to one conversation message’s sender UID will be the receipt’s receiver Id. In case of group conversation message’s receiver Id will be the receipt’s receiver Id |
receiverType | Type of the receiver. Could be either of the two values( user or group) |
senderId | The UID of the sender of the message. |
- 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.
- 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
- To User
- To Group
- TypeScript (User)
- TypeScript (Group)
.then(successCallback, failureCallback) of the markAsDelivered method.
- To User
- To Group
- TypeScript (User)
- TypeScript (Group)
- JavaScript
- TypeScript
.then(successCallback, failureCallback) of the markAsDelivered method.
- JavaScript
- TypeScript
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 a message as unread? You can mark the messages for a particular conversation as unread using themarkAsUnread() method. This method takes the below parameters as input:
| Parameter | Information |
|---|---|
| message | To mark a message as unread, pass a non-null BaseMessage instance to the markMessageAsUnread() function. All messages below that message in the conversation will contribute to the unread messages count. 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. |
You cannot mark your own messages as unread. This method only works for messages received from other users.
- JavaScript
- TypeScript
.then(successCallback, failureCallback). On success, this method returns an updated Conversation object with the updated unread message count and other conversation data.
- JavaScript
- TypeScript
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
onMessagesDelivered()- This event is triggered when a message is delivered to a user.onMessagesRead()- This event is triggered when a message is read by a user.onMessagesDeliveredToAll()- This event is triggered when a group message is delivered to all members of the group. This event is only for Group conversations.onMessagesReadByAll()- This event is triggered when a group message is read by all members of the group. This event is only for Group conversations.
- JavaScript
- TypeScript
MessageReceipt objects. The message receipt contains the below parameters:
| Parameter | Information |
|---|---|
messageId | The Id of the message prior to which all the messages for that particular conversation have been marked as read. |
sender | User object containing the details of the user who has marked the message as read. System User for deliveredToAll & readByAll events. |
receiverId | Id of the receiver whose conversation has been marked as read. |
receiverType | type of the receiver (user/group) |
receiptType | Type of the receipt (read/delivered) |
deliveredAt | The timestamp of the time when the message was delivered. This will only be present if the receiptType is delivered. |
readAt | The timestamp of the time when the message was read. This will only be present when the receiptType is read. |
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 thegetMessageReceipts() method.
- JavaScript
- TypeScript
MessageReceipt objects.
The following features will be available only if the Enhanced Messaging Status feature is enabled for your app.
onMessagesDeliveredToAllevent,onMessagesReadByAllevent,deliveredAtfield in a group message,readAtfield in a group message.markMessageAsUnreadmethod.
Best Practices
When to mark messages as delivered vs. read
When to mark messages as delivered vs. read
Mark messages as delivered as soon as they are received by the device — typically when fetching messages or receiving a real-time message while the app is open. Mark messages as read only when the user actually views the conversation or message. This distinction gives senders accurate insight into whether their message reached the device versus was actually seen.
Batch delivery receipts efficiently
Batch delivery receipts efficiently
Rather than calling
markAsDelivered() for every individual message, pass the last message in a fetched list. The SDK marks all prior messages in that conversation as delivered automatically, reducing unnecessary API calls.Always clean up message listeners
Always clean up message listeners
Remove message listeners when a component unmounts using
CometChat.removeMessageListener(listenerId). Failing to do so can cause memory leaks, duplicate callbacks, and unexpected behavior — especially in React Native navigation flows where screens may mount and unmount frequently.Use the message object overload when possible
Use the message object overload when possible
Prefer passing the full
BaseMessage object to markAsDelivered() and markAsRead() instead of individual parameters. This is simpler, less error-prone, and ensures the SDK has all the context it needs.Troubleshooting
Receipts are not being received in real-time
Receipts are not being received in real-time
Ensure you have registered a
MessageListener with CometChat.addMessageListener() before the receipt events are dispatched. Verify the listener ID is unique and that you haven’t accidentally removed the listener elsewhere. Also confirm the user is logged in and the WebSocket connection is active.markAsRead or markAsDelivered calls are failing
markAsRead or markAsDelivered calls are failing
Check that you are passing valid parameters —
messageId, receiverId, receiverType, and senderId must all be correct. For group messages, receiverId should be the group GUID, not a user UID. Use the .then() error callback to inspect the CometChatException for details.onMessagesDeliveredToAll or onMessagesReadByAll not firing
onMessagesDeliveredToAll or onMessagesReadByAll not firing
These events require the Enhanced Messaging Status feature to be enabled for your app in the CometChat Dashboard. Verify this setting is turned on if you rely on group-level delivery and read tracking.
markMessageAsUnread is not working
markMessageAsUnread is not working
You cannot mark your own messages as unread — this method only works for messages received from other users. Additionally, the
markMessageAsUnread method requires the Enhanced Messaging Status feature to be enabled.Next Steps
Send a Message
Learn how to send text, media, and custom messages to users and groups.
Receive Messages
Set up real-time message listeners and fetch missed messages.
Retrieve Conversations
Fetch and display the user’s conversation list with unread counts.
Typing Indicators
Show real-time typing status in one-on-one and group chats.