Hi Filipe,
The steps I tested can be summarised as below, hope it helps in
anyway.
1. In Firebase console, create new project. Under Firebase project
settings, copy firebase initialisation snippet to be embedded into your web page
before other script tags.
2. During page visit load, the snippet will initialise and request for user
notification permission from user (see URL1 on getToken). If user grants the permission, a firebase
notification token will be provided. This token will then be used as recipient
to deliver web push notification
URL1: https://firebase.google.com/docs/cloud-messaging/js/client
3.The user interacting (click product etc.) on page can triggers marketing interaction API via server logic, and sends along the token as marketing custom field, this
interaction can be used to subsequently execute trigger-based
campaign.
4.Then campaign in turns, triggers Open Channel action to send notification token (custom field) to CPI. Other marketing
information like campaign detail and offers can be packaged along as
well via Open Channel custom logic implementation.
5. CPI is responsible to format
the Open Channel payload into Firebase notification data structure, and trigger
Firebase API call via HTTP call. Refer to documentation below for URL2 and
notification data structure.
URL2: https://firebase.google.com/docs/cloud-messaging/http-server-ref
6. In order to handle incoming notification while
web apps is in foreground or background, refer to URL3 below on how to receive and response to notification using JavaScript. Specifically, event handler is registered to
handle incoming foreground notification. While service worker is used to handle
background notification.
URL3: https://firebase.google.com/docs/cloud-messaging/js/receive
7. The notification handler
received notification along with data which can be useful to trigger subsequent
action. Typically, control shall be passed to server logic controller for
further processing like example below:
8. (Example 1) In
foreground browser, upon receiving notification data contain marketing
information like product discount. The handler passed data back to server logic
and navigate to update page with discount highlighted to engage customer in-moment.
9. (Example 2) When web
apps lose focus or even browser closed, background event handler can be
triggered responding to notification click and pass control to server logic to update further marketing interactions or launch sales order page etc..
10. Since the notification
data can carries along campaign details, we can also attach the campaign id to the
notification click interaction and sent to marketing as campaign success.
Thanks
PengSiong
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.