Marketing Web Push Notifications

Redirect the user to the store by Web push notifications


This product is electronically distributed.


The Web Push Notifications add-on allows you to send notifications via the Google Firebase service, to devices that support Web Push technology. In the upcoming versions, we will add functionality for IOS and OS X devices.

As of April 2019, sending Web Push notifications is free.

Web push notifications have several advantages over other content delivery channels to customers:

  • The notifications spring up at the customers' desktop. Independently of any interfaces.
  • The notification redirects the buyer directly to the store page without distracting actions.
  • Subscribing to notifications requires only 1 click.


  • It's multilingual - notifications support content for all languages of the store, and tokens have a language identifier.
  • It supports multiple storefronts - different storefronts have separate sets of notifications, tokens, and automatic distribution settings.
  • Automatic permission requests to deliver notifications when the add-on is turned on and the settings are filled
  • Sending Web Push Notifications
  • Automatic distribution of new Web Push notifications (Cron must be configured)
  • Automatic distribution of Web Push notifications for abandoned carts (you need to configure the Cron)
  • Automatic distribution of Web Push notifications for new users (you need to configure the Cron)
  • Automatic shutdown of tokens for which there is no possibility to deliver a notification (you need to configure the Cron)
  • Statistics for the latest campaign
  • Statistics on the number of leads
  • Ability to send notifications by vendors whose pages have been visited.
  • Browsers that support Web Push API: Chrome 42+, Firefox 44+

Getting started with Firebase

Creating account

To create an account follow the link and click “Add project”


Getting Legacy Server key and Messaging sender id

After you have created a project (or if there is an existing one), go to the project settings: Project overview=>Project settings=>Cloud messaging


On this tab, we need Legacy Server Key and Messaging sender id, which will be needed later when configuring the add-on.


Managing admin panel

Setting the basic parameters of the add-on

First of all, after installation, you must fill in the basic settings of the module:


License key —Enter your License key to activate the add-on. You will receive this key in the letter with order confirmation. You can also see license keys for all add-ons you purchased in your HelpDesk account. Enter HelpDesk, and navigate to «License» area.

Legacy Server Key —Enter you Legacy Server Key (See the details in Getting Legacy Server key and Messaging sender id).

Messaging sender id —Enter your Messaging sender id (See the details in Getting Legacy Server key и Messaging sender id).

Note: Until you don’t enter Legacy Server key and Messaging sender id customers will not be offered to subscribe to Push notifications.

Creating and editing notifications

After the basic settings have been completed, you can start creating notifications.

Go to Marketing=>Web Push Notifications=>Notifications and push “+” in the top right corner.


A window will open to add a new notification:



Title notifications - 30 characters limit, message header (shown depending on the platform and browser version).

Text notifications - 120 characters limit, message body.

Url - а link to the landing page on which the customer will get after clicking on the notification.

Image - notification image.

Store/Vendor- storefront/vendor to which the notification is attached. For Multi-Vendor: if you select a separate vendor, messages will be sent to those customers who visited the vendor page after agreeing to deliver notifications, if you do not select a vendor, then all active tokens will be sent.

Status - notification status, there are 5 types:

New - A new notification will be sent by the cron task when the corresponding setting is turned on, after sending it will switch to the Executed status.

Service - The Service notification is available for selection in the add-on settings. It is used for sending out abandoned carts and sending to new users when the corresponding settings are enabled.

Deferred - Deferred notifications are used to create messages that do not yet need to be sent. In the future, for distribution, you'll have to transfer them to the status New.

Executed - The notifications with the New status get into this Executed status after the automatic distribution..

Reusable - Notifications for repeated use, these notifications will be sent every time you start the cron (it is recommended to use it with extreme caution as if the cron is incorrectly configured then customers will take it for spam).

Only registered users - mailing will be carried out only to tokens that are associated with registered users (in order for the token to link to an existing account, you must at least once authorize after you allow the delivery of notifications)

After filling in the fields, you have to click Create.

Since the add-on supports multilingualism, then at the time of creating the notification, versions are created for all the store languages, filling identically to the main notification. If you need to edit notifications for different languages, then switch to the desired language and make necessary changes. Fields supporting multilingualism: Title notifications, Text notifications, Url, Image.


Managing notifications

Notifications are managed in Marketing=>Web Push Notifications=>Notifications


On this page there are 3 main blocks:

Notifications list

This block displays the list of campaigns with the possibility of editing, forcing, deleting and changing status.


It also displays statistics on the latest campaign and the total number of transitions for all the time for notifications from this mailing (for the notifications sent out once, the statistics are displayed in the context of a campaign, while for Service campaign, the statistics are displayed in the context of periodic mailings and the total number of transitions will grow without dropping).


Multi-select control buttons and adding new notification

If you select multiple notifications, you can force to send and delete them.


Search block

The search for notifications is implemented by 3 fields: Title, Text and Status


Managing tokens

Tokens are managed in Marketing=>Web Push Notifications=>Tokens


On this page there are 3 main blocks:


Tokens list

This block displays a list of tokens with the possibility of their activation, deactivation and deletion.

Each token has a field “Failed amount” which shows how many notifications failed to get delivered. It's used to automatically disable the token when the corresponding setting is enabled.


Multi-select control buttons

When selecting multiple tokens, their activation, deactivation and deletion is available.


Search block

Search for tokens implemented by 2 fields User id and Status


Managing the permission of vendors to make mailings

The functionality of the module allows vendors to be able to send out notifications to customers who came to their page after being allowed to deliver notifications to them.

Collection of tokens for vendors is carried out only when the setting is enabled. Enable web push notifications for vendors:


After enabling this setting, the main administrator must configure the ability to send campaigns for certain vendors. Vendors=>Choose a Vendor=>Web Push notifications=>Allow Web Push notifications (It is recommended to provide the ability to send notifications only to trusted vendors, since if the customer forbids receiving notifications (as spammy), then notifications will not be delivered from the entire marketplace)


Setting Crons on the server

To automatically send notifications, you must configure the cron on the server. The command for the cron is in the module settings in the tab Cron:


In this command, you need to replace the password with the cron from the store settings

Settings=>Security settings=>Access key to cron script


The frequency of launching cron should be chosen on the basis of which campaigns will be executed (for the full range, the recommended frequency is every 20 min.)

Configuring Cron Mailing for New Notifications

After setting the cron, if you want the new notifications to be sent out automatically, without forced sending, you have to enable the New notification sent in the Cron tab.


When this setting is enabled, new notifications that the administrator will create will be automatically sent the next time the cron is executed.

Configuring Cron Mailing for New Subscribers

If you want to send notifications to new subscribers, you have to enable the setting Use notification for new subscribers in Cron tab and choose the message which will be sent. In order for the notification to appear in the list, you need to create a new notification with the status Service, see Creating and editing notifications).


Configuring Cron Mailing for Abandoned Carts

If you want to launch a campaign for abandoned carts, you have to enable the setting Use notification for abandoned carts in Cron tab and choose the message which will be sent. In order for the notification to appear in the list, you need to create a new notification with the status Service, see Creating and editing notifications).


Abandoned carts are sent 1 time, sampling is carried out in the last day. Subscribers are considered as new if their tokens, after allowing the delivery of notifications were not sent a notification for new subscribers.

Configuring Cron Mailing for automatic Bad Tokens Shutdown

It is recommended to enable the setting Use bad tokens shutdown, as disabling tokens for which it is impossible to deliver a notification will reduce the load on the server at the time of sending notifications..

After enabling this setting, you will need to configure the number of unsuccessful deliveries, after which the token will be disabled (default 20)


User guide

Learn more about the add-on in our User guide.

Product type:
  • CS-Cart
  • Multi-Vendor
  • 4.15.2
  • 4.15.1 SP1
  • 4.15.1 SP2
  • 4.15.1 SP3
  • 4.15.1 SP4
  • 4.15.1
  • 4.14.3
  • 4.14.2. SP1
  • 4.14.1 SP1
  • 4.14.2
  • 4.14.1
  • 4.13.3
  • 4.13.2
  • 4.13.1
  • 4.12.2 SP1
  • 4.12.1
  • 4.11.5
  • 4.11.4
  • 4.11.3
  • 4.11.2
  • 4.11
  • 4.10.x
  • 4.9.x


legend: [!] fixed  bug, [~] minor changes, [+] new functionality, [-] deleted functionality 


December 2022

v. 4.9.8

[changed] The add-on is adapted to the standard "CS.Cart: Vendor Panel Configurator" add-on

July 2021

v. 4.9.7

[fixed] PHP notifications occurred at web_cron_push launch are fixed

June 2021

v. 4.9.6

[fixed] The broken layout of the 404 page is fixed

[added] Cron for service notifications is added

August 2020

Version v4.9.0.4

[+] Graphic appearance for disabled tokens has been added

July 2020

Version v4.9.0.3

[!] The list of tokens for vendors displayed incorrectly. Fixed

June 2020

[!] The setting field Legacy server key was replaced with Server key

[!] The cron password wasn't automatically added to the cron command. Fixed

[+] The ability to auto-copy cron launching command from the add-on settings has been added

May 2020

[!] UTF characters in notifications were sent incorrectly. Fixed

April 2020


[!] The add-on's settings did not open when the add-on was disabled. Fixed.


June 2019


[!] The Upgrade Center returned an error. Fixed.