Skip to main content
CometChat Campaigns lets you deliver targeted, rich notifications to users via an in-app notification feed. Each notification is a Card Schema JSON — a structured layout rendered natively by the CometChat Cards library. The SDK provides APIs to fetch feed items, listen for real-time delivery, mark items as read/delivered, report engagement, and retrieve unread counts.
Before using the SDK, set up your channels, categories, templates, and campaigns in the CometChat Dashboard. See the Dashboard Setup Guide for step-by-step instructions.

Card Messages

A Card Message is a structured, interactive message rendered as a card bubble inside a conversation. Cards are receive-only on the SDK: they are created through the Platform REST API or the Dashboard Bubble Builder and delivered to clients like any other message — the SDK does not send them.
  • Type: CardMessage (cometchat_sdk)
  • Category: "card" (CometChatMessageCategory.card)

Properties

Listening for card messages

To be notified when a card message arrives, implement onCardMessageReceived on your MessageListener.
See Receive Messages → Receiving Card Messages for the full handling and rendering reference.

Key Concepts


How Cards Render in the Notification Feed

Each NotificationFeedItem has a content field containing a Map<String, dynamic> — this is the Card Schema JSON. This JSON is passed directly to the CometChat Cards renderer package (cometchat_cards). The rendering flow:
  1. Fetch feed items via NotificationFeedRequest
  2. For each item, extract item.content — this is the Card Schema JSON
  3. Convert to string: jsonEncode(item.content)
  4. Pass to the Cards renderer (CometChatCardView)
  5. The renderer produces a native Flutter widget from the JSON

Card Schema JSON Structure

The body array contains elements (text, image, button, row, column, etc.) rendered top-to-bottom. Interactive elements like buttons emit actions via a callback — the consumer handles navigation, deep links, or API calls.

Retrieve Notification Feed Items

Use NotificationFeedRequest to fetch a paginated list of feed items. Uses cursor-based pagination internally.

Build the Request

Builder Parameters

Fetch Items

Call fetchNext() repeatedly for pagination. When the server has no more items, subsequent calls return an empty list.

NotificationFeedItem Fields


Retrieve Notification Categories

Use NotificationCategoriesRequest to fetch available categories for filter chips.

NotificationCategory Fields


Real-Time Notification Feed Listener

Listen for new feed items arriving via WebSocket. This listener is independent from MessageListener, GroupListener, and CallListener.
Remove the listener when no longer needed:

Mark Feed Item as Read

Mark a single item as read. Idempotent — safe to call multiple times.

Mark Feed Item as Delivered

Mark a single item as delivered. Idempotent.

Report Engagement

Report that a user engaged with a feed item (e.g., viewed, clicked, interacted). Idempotent.
The interactionString parameter is a free-form string describing the engagement (e.g., "viewed", "clicked", "interacted").

Get Unread Count

Fetch the total number of unread notification feed items.

Fetch Single Feed Item

Fetch a specific item by ID — useful for deep linking from push notifications.

Push Notification Tracking

When a campaign push notification arrives via FCM/APNs, use these methods to report delivery and click engagement.

Mark Push Notification as Delivered

Call this when you receive the push notification payload:

Mark Push Notification as Clicked

Call this when the user taps the push notification:

PushNotification Fields


FeedReadState Enum


Rendering Cards

The content field of each NotificationFeedItem is a Card Schema JSON map. To render it natively, use the CometChat Cards library.

Add the Cards Dependency

Add the cards package to your pubspec.yaml:

Render a Card from a Feed Item

The Cards library is a pure renderer — it does not execute actions. Your code must handle action callbacks (opening URLs, navigating to chats, making API calls, etc.).

Supported Card Actions

When a user taps a button or link inside a card, the action callback receives one of these action types: