Welcome to Fusion Docs!

Introduction

The Push Notification Module enables administrators and application teams to configure, manage, and monitor push notifications from a centralized platform. This module is designed to support both manual and programmatic notification delivery through Firebase Cloud Messaging (FCM) integration.
The feature provides complete notification lifecycle management, beginning from Firebase setup and configuration, continuing through API integration and notification creation, and ending with delivery monitoring and reporting. Through this system, organizations can deliver announcements, alerts, promotional campaigns, and targeted communications to users efficiently.
The Push Notification module includes four major areas:

• Dashboard Overview
• FCM Configuration
• API/Webhook Integration
• Notification Creation & Scheduling

Each area plays a critical role in ensuring reliable and scalable push notification delivery.

Push Notification Dashboard

The Push Notification Dashboard serves as the primary monitoring and control interface for the Push Notification module. It provides administrators with a consolidated view of notification activity, delivery trends, and system performance.
The dashboard is designed to help users quickly understand how notifications are performing and whether campaigns or alerts are being delivered successfully.

Dashboard Overview

The top section of the dashboard displays key notification metrics, allowing administrators to monitor overall activity at a glance.
These metrics include:

• Total Notifications: displays the overall number of notifications generated within the selected period.
• Sent to Masses: indicates notifications broadcast to larger audiences or subscribed topics.
• Sent to Individuals: represents notifications delivered to specific users or devices.

These indicators help administrators evaluate usage volume and notification reach.

Date-Based Filtering

To support reporting and performance analysis, the dashboard includes date range filters.
Users can switch between:

• Last 7 Days
• Last 15 Days
• Last 28 Days

These filters dynamically update dashboard statistics and graphs, enabling users to compare notification performance across different time periods.

Notification Trend Analysis

The dashboard includes a graphical representation of notification activity over time. This chart provides insight into sending patterns and notification trends.
The graph enables administrators to:

• Identify peak notification activity
• Compare mass and individual delivery
• Monitor engagement trends
• Detect unusual delivery behavior

Visual analytics improve operational visibility and simplify monitoring.

Notification Listing and Management

The lower section of the dashboard contains a searchable notification list. This table provides a detailed history of notifications and their delivery status.
Each record typically includes:

• Notification Title
• Creation Date
• Category
• Delivery Status

Status labels such as Completed, In Progress, and Scheduled help teams monitor delivery progress and identify pending actions.
The dashboard also provides quick access to additional actions including:

• Create New Notification
• Configuration
• Integration

This centralized design minimizes navigation and improves operational efficiency.

Configuration – Firebase Cloud Messaging (FCM) Setup

The Push Notification system relies on Firebase Cloud Messaging (FCM) as its delivery infrastructure. Before notifications can be sent successfully, the application must be properly registered and configured with Firebase.
This configuration establishes secure communication between the application and Firebase services.

Why Configuration Is Required

Push notifications cannot be delivered unless Firebase recognizes and authenticates the application requesting delivery.
The configuration process ensures:

• Application registration
• Secure authentication
• Message routing
• Platform-level notification permissions

Without proper configuration, push requests may fail or remain undelivered.

Step 1 – Create Firebase Project

The configuration process begins inside the Firebase Console.
Administrators must create a dedicated Firebase project that will manage notification services for the application.
During this stage, Firebase generates a unique project identity and provides access to messaging services.

Step 2 – Register Mobile Applications

After project creation, mobile applications must be registered.
Supported platforms include:

• Android
• iOS

Each application registration creates platform-specific configuration data that Firebase uses to identify the application.

Step 3 – Configure Firebase Messaging Services

Once applications are registered, Firebase Cloud Messaging must be enabled.
This enables Firebase to:

• Receive push requests
• Authenticate delivery
• Route notifications
• Manage device communication

Platform-level permissions and messaging settings must also be configured during this stage.

Step 4 – Generate Firebase Credentials

Firebase generates configuration credentials required by the Push Notification module.
These credentials may include:

• Service Account
• Firebase Project Keys
• Messaging Configuration
• Web Service Credentials

The configuration is typically exported as a JSON file.

Step 5 – Upload Mapping File

The Configuration panel inside the Push Notification module is used to upload the Firebase configuration file.
Administrators can upload:

• Android configuration
• iOS configuration
• Firebase JSON mapping file

Platform-level permissions and messaging settings must also be configured during this stage.

API Integration / Webhook Configuration

The API Integration section allows organizations to send notifications programmatically through backend systems and external services.
This feature is particularly useful for automated workflows where notifications are triggered based on business events.
Examples include:

• Order updates
• System alerts
• Marketing campaigns
• Workflow automation
• User activity notifications

Integration Components

The integration screen provides several important components.

Client ID

The Client ID acts as a unique identifier for API communication.
It ensures that requests are associated with the correct project and environment.

Access Token

The Access Token provides secure authorization.
Only authenticated systems can send notifications.
The token is included in API requests using:

• Execution progress tracking
• Pass and fail ratio
• Execution summary dashboard

Bearer Authentication

This prevents unauthorized notification delivery.

Webhook URL

The Webhook URL acts as the notification endpoint.
Backend systems submit notification requests to this URL.
The endpoint processes:

• Authentication
• Request validation
• Notification delivery

Sample API Request

The integration panel also provides a sample request.
This helps developers quickly implement backend integration without needing separate documentation.
Typical request payload includes:

• Device Token / Topic
• Notification Title
• Notification Body
• Client ID
• Authorization Token

Integration Workflow

The recommended integration workflow is:

• Generate Access Token
• Copy Webhook URL
• Configure backend request
• Authenticate request
• Send notification payload

This design enables secure and scalable notification automation.

Creating and Scheduling Notifications

The Create Notification screen allows administrators to manually compose and schedule push notifications.
This interface is designed to support both immediate communication and planned notification campaigns.

Category Selection

The first step involves selecting a notification category.
Categories help organize notifications and simplify reporting.
Examples may include:

• Promotions
• Alerts
• Maintenance
• Information

Categorization improves visibility and filtering.

Topic / Channel Selection

Notifications can be targeted through topics or channels.
This ensures that messages reach the intended audience rather than all users.
Channels support:

• Audience segmentation
• Subscription-based messaging
• Targeted campaigns

Notification Content

Administrators provide:

• Notification Title
• Notification Description

The title should be concise and attention-grabbing, while the description should clearly communicate the message.
Well-structured content improves user engagement.

Scheduling Notifications

The module supports flexible scheduling. Notifications may be:

Send Now

Delivered immediately.

Scheduled

Delivered at a future date and time.
Scheduling supports:

• Marketing campaigns
• Event reminders
• Planned announcements
• Time-sensitive alerts

Timezone selection ensures accurate delivery timing.

Expiry Configuration

Optional expiry settings prevent outdated notifications from being delivered.
This is especially useful for:

• Temporary offers
• Limited campaigns
• Time-sensitive alerts

After expiry, undelivered notifications become invalid.

Submission Process

Once all information is completed, users can submit the notification.
The system validates:

• Configuration
• Schedule
• Delivery settings

After validation, the notification enters the delivery queue.