LeadEngine marketing automatizáció
firebase

Firebase Cloud Messaging – Mautic 3 plugin

Fast Reliable Well documented Mautic plugin

You wish to send push notifications, but you don't trust OneSignal? Use our Google - 'Firebase Cloud Messaging' push notification sending solution and retain the data of your contacts for yourself.
Excluding 27% tax

Billed once per year until cancelled

version:3.1.0

Version history

Purpose

The OneSignal push messaging service offered officially by Mautic does not necessarily meet the GDPR requirements defined as an EU norm in many respects. To compensate for this, a solution that is ‘compatible’ with the OneSignal push messaging service, but is technically based on Google – Firebase Cloud Messaging (hereafter: FCM), has been implemented, with which we can send push notifications to the Mautic managed contacts of our web- or mobile applications, with a constantly expanding range of functions.

How does it work?

The plug-in provides the same capabilities as the well-known OneSignal plugin, where GDPR-compliant Google – FCM is responsible for sending messages and storing related user data. The affected user data is thus stored in a completely isolated environment and used for messaging.

* Connected to a private Google Account, and free from any external data traffic, thus complying with EU – GDPR regulations.

For its usage we need:

  1. A Mautic with the contacts of the corresponding web-, or mobil application.
  2. A Google – Firebase project, which in general generate and store the Push IDs (‘FCM registration token’) at the registration process.
  3. And furthermore we have to manage to register the corresponding users to the push notification service with our application.
    • In case of web application it is very simply with the embedding of the plugin offered .JS script (with Mautic Focus element, or with Google – Tag Manager, or with any other comfortable solution).
    • In case of native mobile application an application developer have to put some extra lines into the code of the application.
  4. To show the notifications there is no special requirement in case of web applications, but with mobile applications an application developer has to parse and show the message data sent to the application by Mautic  through FCM.

At any push notification registration the corresponding push ID is stored also in Mautic, therefore notification can be sent by it.

What can it be used for?

With the usage of our plugin the contacts of a web- or even a mobile application could be able to subscribe to a push notification service, which could be managed by automatic campaigns of our Mautic (like in case of email communications).

If our contacts allow sending push notifications, we may also communicate with them via short direct messages (in our multi funnel marketing/multi channel marketing solutions).

Dependencies

A bővítmény használatához szükség van:
  • a phpbolt nevű php kiterjesztés futtatási környezetbe való beépítésére
  • a plokko/firebase-php nevű composer csomag telepítésére
Detailed manual

Mautic LeadEngine plugins

Excluding 27% tax

Billed once per year until cancelled

Plugins
© 2018-2020 leadengine.hu 1.2
Designed and Powered by ReachMedia
  • Your cart is empty.

Verziótörténet

3.1.0

  • new function Accepting any unique ID in the ‘appcallback’ URL (controller) to identify the corresponding contact.
  • new function At first optional, but from 2023 mandatory ‘access key’ based authentication with the usage of the ‘appcallback’ URL (controller).
  • bugfix Correcting the sometimes wrong entries in the contact’s event history: termination of the usage of ‘short open tags’.

3.0.0

  • optimization Further more optimized manual for totally clear usage.
  • optimization New version numbering logic aligned to the major Mautic versions.
  • bugfix 3 character browser version handling.
  • bugfix Licence handling.

2.4.1

  • Bugfix Correction of the wrong type definition (array ???? ?array)  at the data of the messages.
  • Bugfix Hibásan megadott alapértelmezett üzenet lejárat korrekciója.

2.4.0

  • Optimization Separated ‘web’ and ‘mobile’ notifications int the reports for clearer analisises.
  • NEW FEATURE From now in segments but also in campaigns there are direct targeting possibility only to ‘web’ and only to ‘mobile’ ‘Push ID’s (also with keep the older heterogeneous solution), more precisely their owners (contacts with only ‘web’ or only ‘mobile’ ‘Push ID’s), therefore the event histories – generated by the sent messages – will not contain those notifications ‘which could not be sent on the corresponding channel’.

2.3.2

  • Bugfix SendErrorException.

2.3.1

  • Bugfix Critical reporting error (KernelSubscriber).

2.3.0

  • New funcion Now there is a possibility in few clicks to clone a web, or a mobile push message.
  • New function In case of a message sent to a contact with more ‘Push ID’s, now the administration interface shows the details of the event by each discrete ‘Push ID’s.
  • New function In case of unsuccessful message sendings, now the  administration interface differentate the corresponding ‘Push ID’s at the ‘Push ID’s tab.
  • New function In case of temporary unsuccessful message sendings – when the plugin is trying to resend the push notification – the administration interface at the event details shows the current state of the push notification of the corresponding ‘Push ID’ (where this state continuously refresh itself until a successful finish).
  • New function Expansion of the documentation with the plugin’s error handling.
  • Optimization Correction of the version history link at the plugin’s update notifications and also at its settings.

2.2.5

  • BUGFIX Normalization of the inconsistent (and problematic because the file encoding) PHP open tags.

2.2.4

  • Optimization Display all ‘Push ID’s of a contact at its profile data on a separate tab
  • Optimization Display the version number of the plugin itself at its settings

2.2.3

  • Optimization Error message expansion/correction

2.2.2

  • Optimization Detailed event error messages

2.2.1

  • Bugfix Correcting ‘Web push notification’ subscription in mobile browsers

2.2.0

  • Bugfix Consolidation of core Mautic code independency

2.1.1

  • Bugfix

2.1.0

  • New function License handling

2.0.0

  • Optimization Mautic 3.x compatibility

1.0.0

  • New function First version
  • Your cart is empty.

Version history

3.1.0

  • new function Accepting any unique ID in the ‘appcallback’ URL (controller) to identify the corresponding contact.
  • new function At first optional, but from 2023 mandatory ‘access key’ based authentication with the usage of the ‘appcallback’ URL (controller).
  • bugfix Correcting the sometimes wrong entries in the contact’s event history: termination of the usage of ‘short open tags’.

3.0.0

  • optimization Further more optimized manual for totally clear usage.
  • optimization New version numbering logic aligned to the major Mautic versions.
  • bugfix 3 character browser version handling.
  • bugfix Licence handling.

2.4.1

  • Bugfix Correction of the wrong type definition (array ???? ?array)  at the data of the messages.
  • Bugfix Hibásan megadott alapértelmezett üzenet lejárat korrekciója.

2.4.0

  • Optimization Separated ‘web’ and ‘mobile’ notifications int the reports for clearer analisises.
  • NEW FEATURE From now in segments but also in campaigns there are direct targeting possibility only to ‘web’ and only to ‘mobile’ ‘Push ID’s (also with keep the older heterogeneous solution), more precisely their owners (contacts with only ‘web’ or only ‘mobile’ ‘Push ID’s), therefore the event histories – generated by the sent messages – will not contain those notifications ‘which could not be sent on the corresponding channel’.

2.3.2

  • Bugfix SendErrorException.

2.3.1

  • Bugfix Critical reporting error (KernelSubscriber).

2.3.0

  • New funcion Now there is a possibility in few clicks to clone a web, or a mobile push message.
  • New function In case of a message sent to a contact with more ‘Push ID’s, now the administration interface shows the details of the event by each discrete ‘Push ID’s.
  • New function In case of unsuccessful message sendings, now the  administration interface differentate the corresponding ‘Push ID’s at the ‘Push ID’s tab.
  • New function In case of temporary unsuccessful message sendings – when the plugin is trying to resend the push notification – the administration interface at the event details shows the current state of the push notification of the corresponding ‘Push ID’ (where this state continuously refresh itself until a successful finish).
  • New function Expansion of the documentation with the plugin’s error handling.
  • Optimization Correction of the version history link at the plugin’s update notifications and also at its settings.

2.2.5

  • BUGFIX Normalization of the inconsistent (and problematic because the file encoding) PHP open tags.

2.2.4

  • Optimization Display all ‘Push ID’s of a contact at its profile data on a separate tab
  • Optimization Display the version number of the plugin itself at its settings

2.2.3

  • Optimization Error message expansion/correction

2.2.2

  • Optimization Detailed event error messages

2.2.1

  • Bugfix Correcting ‘Web push notification’ subscription in mobile browsers

2.2.0

  • Bugfix Consolidation of core Mautic code independency

2.1.1

  • Bugfix

2.1.0

  • New function License handling

2.0.0

  • Optimization Mautic 3.x compatibility

1.0.0

  • New function First version