Meiro Mobile SDK

Meiro Events
1. Open your ME instance dashboard.

2. Open your app with the Meiro Mobile SDK integrated and make sure you have cleared the application data to start with a fresh state.

3. If your app includes consent management, the SDK should be initialized only after users give their consent. Subsequently, users must confirm the system prompt to grant permission to receive mobile push notifications.

4. After completing the above steps, you should see events coming into the ME instance dashboard under the meiro_mobile endpoint.

• There will be events like app_installed, app_foreground, and app_background (if you put the application in the background).
• There should also be an fcm_registration_token_registered event to enable receiving mobile push notifications. Save your user_id value somewhere so that you can later find your profile in the CDP.

• If developers have implemented link tracking in your app, you should see link_click events when you click on the links.
• The same rule applies to screen_view events.
• The last thing to check is whether you're receiving event_custom events if you have implemented custom events for specific use cases. Ensure that they contain your desired payload.
  

Meiro Business Explorer (CDP)

1. Open your MBE instance.

2. Go to the profiles search tab:

• Select the User ID dimension of the Mobile Push Subscription attribute and fill in your user_id value into the text field.

• You should be able to find your profile and validate that you can see values for some Meiro Mobile Push and Meiro Mobile Apps attributes. You should also see all the events received on the profile timeline, the same as you saw on the ME dashboard.
  

3. Create a segment containing only your profile. You can use the same attribute you used to filter your profile. Confirm that one profile is available to activate in the Mobile Push channel.

4. Create a Mobile Push campaign for testing and fill in the required details. Select the correct application from the dropdown menu.

5. Go to the activation tab of the Mobile Push campaign and select the segment containing your profile. Press 'Send now'.
6. You should receive a push notification on your device after the activation is finished. Tap on the received notification.

Meiro Events
Go back to the ME dashboard and check that you’ve received the fcm_message_received and fcm_message_click events.

Meiro Business Explorer

Return to the MBE instance and locate your profile again. You should see new attributes with values related to the recently sent push notification. The profile timeline should also display new events related to this push notification.

Create Meiro Mobile Apps system source

Start creating Meiro Mobile Apps source from the source create window in the Administration/Source tab. 

System entities relevant to mobile analytics (source, events, attributes, and stitching rules) will be aggregated for all integrated apps. System events are only created for known event structures; we cannot create system events for custom events or screen views with additional payload other than the screen name.

Integrate Meiro Mobile SDKs into desired apps

App developers have to follow our documentation and integrate mobile SDKs with properly configured tracking setup (enabled automatic tracking, configured tracking for screen views, tracking desired link clicks, custom events tracking implemented)

As a result, the CDP will start receiving desired events, and customer profiles will have the correct values of Meiro Mobile Apps attributes.

Custom events and attributes implementing specific use cases

Meiro cannot automatically create system entities for custom events and related attributes due to the lack of knowledge about the event payload structure. As a solution, analysts will manually create desired events and attributes.

Even if the Mobile Push use case is not activated, the SDK remains valuable for tracking user interactions within your app and collecting event data for analytics purposes.

The Meiro SDK tracks a variety of events, both default system events and custom events defined by the client.

Default System Events:

• Application Foregrounded - When the user brings the app to the foreground (i.e. when they open or switch back to the app from another app or the home screen).
• Application Backgrounded - When the user sends the app to the background (i.e. when they switch to another app or go to the home screen).
• App Install Event - When the app is installed on a user’s device for the first time.

These event tracking could be implemented on the client’s side:

• Screen Views - When a user views a specific screen within the app.
• Link Clicks - When a user clicks on a link within the app. This includes links to external websites, other parts of the app, or specific features within the app.
• Custom events - When specific actions (defined by the client) occur within the app. These can be tailored to track particular user interactions, such as completing a purchase, sharing content, or using a particular feature.
  

Mobile Push events are critical for understanding how users interact with push notifications and managing user data, such as tokens and IDs.

• MP Registered: This event is triggered when significant changes occur to the user’s data. It helps ensure that user identifiers and tokens are updated correctly.

  • When a user_id is generated or changed.

  • When a Firebase token changes (such as when the token is reset)

• FCM Registration Token Registered: Tracks the registration of a new Firebase Cloud Messaging (FCM) token, which is essential for enabling push notifications. This token is essential for enabling push notifications on a user's device.
  • When a user installs the app or re-installs it after uninstalling.
  • When the FCM registration token is refreshed (e.g., when it expires or is manually refreshed).

Warning: Developers must reset the FCM token if a user revokes consent. For detailed instructions, refer to the Firebase Token Management article.

• FCM Message Received: Tracks the delivery of push notifications sent via FCM. This does not necessarily mean that the user has seen or interacted with the notification.
  • When a new promotional offer or update is pushed to the user's device.
  • Tracking the delivery rate of push notifications.

Warning: The "Mobile Push Received" event might not be sent until the user opens the app. This behaviour depends on various factors, such as the system's state, battery optimisation settings, and whether the app is running in the background or closed. Once the user opens the app, any potentially received push notifications from the past will be sent, along with the correct timestamp of when the user received the notification.

• FCM Message Click: Tracks user interaction with push notifications, indicating engagement with the content.
  • Monitoring user interaction with in-app content and links.

Updating our SDK is a straightforward process that primarily involves changing the version of the SDK used in clients' applications. This ensures you always have access to the latest features, improvements, and bug fixes.

The frequency of SDK updates can vary. While we aim to provide a stable and reliable SDK, there may be instances where updates are necessary, such as:

• Hotfixes: If a bug is discovered, we will release a hotfix as soon as possible to address the issue.
• Feature Releases: When new features are developed and added to the SDK, we will release an update to make these available.

Currently, we do not anticipate frequent updates unless a critical issue arises or a new feature is developed. Meiro Devs will communicate updates as early or in advance as possible.

When an update is released, clients will need to upload the new version of the SDK into their application. This may require minor adjustments in your code to accommodate changes or new features.