Mobile Push channel configurations
The Administration/Configurations/Channels tab in Meiro Business Explorer enables businesses to configure channels for running campaigns. This guide provides a step-by-step tutorial on configuring the Mobile Push channel in Meiro Business Explorer.
Learn from this article:
Generate Firebase JSON file
Before configuring the Mobile Push channel, it is required to set up a Firebase account and generate a Firebase JSON file. Below is the sequence of steps to follow for setting this up:
- Once you have created a Firebase project, you can set up an app in Firebase for iOS or Android.
- In the Firebase console, open Settings -> Service Accounts -> click ‘Generate new private key’.
3. Click on the ‘Generate key’ to download the ServiceAccount.json file. This file is required to allow Meiro Business Explorer to access your Firebase project.
Configure Firebase account on MBE
To set the Mobile Push channel, the user must first configure the Firebase account under the Administration/Configurations/Channels tab. To configure the Firebase account, please upload the ServiceAccount.json file from the previous step.
To activate the Mobile Push channel, you must add at least one mobile app. In this section, you can find a list of previously added mobile apps, each with the following details:
The name of the mobile app.
Android/ iOS icon
The icon appears if the mobile app is configured for Android, iOS, or both.
Edit / Delete
You can use these options to edit the app's settings or delete an application.
If no app is added yet, click the “add application” button, which will take you to the mobile application settings page. Fill in the information in a new window.
This is the name of your mobile application. Provide a unique and descriptive name for the application.
Android version / iOS version
(at least one is required, or both)
The App ID is a unique identifier for your mobile app. Applications are pulled directly from the Firebase project, and you need to select the relevant ones for your desired application based on the names you provide.
Set FCM registration token stitching category
At the next stage, choose the stitching category related to the FCM registration token, keeping in mind that it cannot be changed later on. This stitching category helps to associate push notification-related events with the correct registration tokens.
You can either pick an existing category or create a new one using the “add stitching category” button if a suitable category is unavailable.
Remember: Be sure to use stitching rules based on the shared identifier
registration_token to link push notification-related events.
Integrating Firebase SDK and Implementing Mobile App Changes
Begin by integrating the Firebase SDK into your mobile apps.
Remember: It is necessary to obtain user consent before initializing the SDK and sending events, as Meiro does not manage consent for the Mobile Push channel.
You need to implement sending the following two events from your apps to the
/meiro_mobile Mobile Events endpoint:
- FCM Registration Token Registered:
This event is used to initialize the user's Mobile Push channel. It registers the user's Firebase registration token within the CDP. This event needs to be sent whenever the registration token is initiated, as well as when the token changes. If you already have the Firebase SDK integrated into the apps and have access to the registration token, you only need to implement a one-time procedure to send the current users' registration tokens via this event.
You can use a framework such as WorkManager on Android or BackgroundTasks framework on iOS. You may also pass additional identifiers in the event payload, such as Adjust ID, Appsflyer ID, Google Playstore AdID, and IDFA. Including them makes it possible to stitch these analytical events mobile with mobile push events. Learn more about implementing this event and its payload example in this article.
FCM Registration Token Refreshed:
Once the FCM Registration Token Registered event has been sent, you should periodically send the Token Refreshed event once a month. This event ensures that the token is still active and not stale. It should be sent even when the application is not running, for example, via WorkManager (Android) or BackgroundTasks framework (iOS). Learn more about implementing this event and its payload example in this article.
What is a registration token, and where can I find it?
A Registration Token, also known as a Firebase Cloud Messaging (FCM) registration token, is a unique identifier assigned to each instance of a mobile app that registers with FCM. It is used by the FCM service to send push notifications to specific devices.
The registration token changes in three cases: when you uninstall and reinstall the app, when you clear app data, or when you restore the app on a new device.