Comparison of Cards and Notification Centre

The following table provides you with a comparison of Cards and Notification Centre.

	Cards	Notification Center
Supported Platforms	Android, iOS, Web.	Android, iOS.
Delivery Mechanism	Delivered when the SDK syncs with Moengage Server or via Public Fetch API.	Delivered when the push notification is delivered via APNS/FCM or on every app open.
Reachability	Any user with a device	Any user eligible and opted in for Push notifications
Available Trigger Options	Bulk (one-time) - Send to target users reachable at the time of sending campaign, including future users Trigger Based Event-triggered Flow triggered Periodic	Bulk (one-time) - Send to target users who are reachable when sending the campaign. Trigger Based Event-triggered Device triggered Location triggered Business event triggered Flow triggered Periodic
Content Retention	Messages are retained on multiple devices, uninstalls, and logouts. Content can be updated and hidden if the campaign is updated. Every triggered notification is a separate entry.	Messages are not retained on multiple devices, uninstalls, logouts Content is static and cannot be removed in bulk before expiry Every triggered notification is a separate entry
Out of the box UI	Inbox Customization Configured from dashboard Cards Campaign Basic customization of the inbox appearance theme and fonts Categorize cards into different tabs, optional Message UI and text customization Templates Basic with optional icon Illustration Card Background Colour Title Message Image Default Action Additional CTA Pin Card to top	Inbox Customization Basic customizations of the inbox appearance around theme and fonts Message UI and text customization Configured from dashboard Push campaign or Push API, a replica of the push content Title Message Default Action
Self -handled	The payload of card notification Fetch Cards Fetch Unclicked card count Fetch Card Categories Track Statistics - Delivered, Impressions, Clicks Delete Card	Replica payload of push notification Fetch Messages Fetch Unclicked notifications count Track Statistics - Clicks Delete Message
Supported Campaign Options	Personalization - Attribute-based, Event-based Card expiry option Impression count based Days since delivery Days since impression	Personalization - Attribute-based, Event-based, DPM and Content API A/B testing Locales Notification Centre Expiry Option - Days since delivery

Frequently Asked Questions

arrow_drop_down My application is developed on a web platform. Which channel is suitable for building an inbox?

You should use Cards to build a message inbox as the Notification Centre is not supported for web platforms.

arrow_drop_down I want to send notifications to all users of my application, including opted-out users and those without a registered push token. Which channel should I use?

Cards can be used to reach out to any users who have a device, and the Notification Centre can be used to reach out to users who are eligible and opted in for push notifications.

arrow_drop_down I need to customize my notifications, including image and background colour. Can Cards be used for this?

Yes, Cards Out-of-the-box inbox supports customization of images and background colour. Additionally, you can customize the title, message, and default action.

arrow_drop_down I need my notification to be retained even after the user uninstalls or logs out of the application. Can a channel support this?

Yes, Cards retain messages across multiple devices, uninstalls, and logouts. However, if you use the Notification Centre, messages are not retained across devices, uninstalls, or logouts.

arrow_drop_down Which channel can be used to personalize my inbox messages?

You can use either Cards or the Notification Centre, depending on your requirements.

Cards support attribute-based and event-based personalization.
Notification Centre supports attribute-based, event-based, DPM, and Content API personalization.