Meiro Mobile SDK

The Meiro Mobile SDK is a powerful tool designed to enhance the capabilities of client iOS and Android applications. Integrated with Firebase, it also facilitates the delivery of push notifications.

Key functionalities:

Event Tracking: The Meiro SDK supports a wide range of predefined event tracking options, allowing developers to track various user interactions within the app. Additionally, the SDK enables the collection of custom events tailored to individual client requirements, providing a comprehensive view of user behavior.
Communication Activation: The Meiro SDK integrates with Firebase Cloud Messaging (FCM) to enable the sending of mobile push notifications to users. This feature empowers clients to effectively engage with their app users and deliver targeted content or updates.

The Meiro SDK provides a robust foundation for comprehensive tracking and the future enhancement of mobile activation channels, such as in-app messages and content blocks.

Implementation Steps

~~Planning:~~Planning: you should identify the key events and data points that you want to track. The Meiro team can provide guidance and suggestions to ensure the tracking is tailored to the specific needs.

2. App Code ~~Implementation:~~Implementation: incorporate the SDKs into the application’s codebase and implement the necessary event tracking and data collection points.

Learn more: how to integrate Meiro SDK for Android and iOS devices.

Testing: after implementing the SDK, thoroughly test the integration by checking the incoming events in the Meiro Events dashboard.

4. App ~~Deployment:~~Deployment: Once the testing is completed, you can prepare the app for deployment and submit it to the respective app stores (App Store or Google Play Store).

5. Mobile Push Setup: System entities are automatically created based on known events' structures. Custom events require individual settings by analysts.

SDKs testing process

1. Plan Your Testing Process
Establish Testing Environments: Ideally, use a separate testing or staging environment to validate the SDK implementation before deploying to production.

2.1 Testing in a Staging Environment

Setup Staging Environment: Ensure that your staging environment closely mirrors your production environment in terms of configuration.
Deploy SDK: Integrate the SDK into your staging environment.
Generate Test Events: Perform various actions within the app to trigger events tracked by the SDK.
Monitor Events: Use the Meiro Events dashboard to verify that events are flowing into the system as expected.

2.2 Testing in a Production Environment (if no staging is available)

Limited Release: Consider releasing the updated app with the new SDK to a small subset of users.
Generate Real-World Events: Encourage these users to interact with the app and generate events.
Monitor in Real-Time: Continuously monitor the events in the Meiro dashboard to ensure they are being tracked and reported accurately.

3. Verification and Validation
Cross-Check: Compare the events recorded in Meiro with the actions performed in the app to ensure accuracy.

4. Final Deployment

Full Deployment: Once the SDK implementation is verified and validated in the staging environment, or the limited release in production is successful, proceed with the full deployment to all users.

Post-Deployment Monitoring: Continue to monitor events post-deployment to catch any issues early.

Mobile Push Initial Setup

Remember: The Meiro SDK is required to enable and run Mobile Push notifications in your application.

Enable the mobile push channel: This action installs system entities relevant to push notifications, such as sources, events, attributes, and stitching rules.
Configure System Events for Analytics: add the system source "Meiro Mobile Apps" into the CDP. This will include the necessary sources, events, attributes, and stitching rules aggregated for all potential applications.
Define Events and Attributes: Predefined events and attributes are automatically created by the system based on known schemas, requiring no additional configuration. For custom events, you must manually create the events and any necessary attributes, tailoring them to specific use cases.

Meiro SDK and Firebase Integration

The Meiro SDK and Firebase work together to provide a comprehensive solution for mobile push notifications. The Meiro SDK handles the tracking of user activity and the display of push notifications, while Firebase Cloud Messaging (FCM) enables the sending of these notifications across multiple platforms (iOS and Android).

Remember: Firebase provides a unified suite of tools to streamline the development process, improve app performance, and enhance user engagement. In that order, Firebase SDK has to be implemented on the client's side.

This is the way how Meiro SDK and Firebase SDK work together:

Integration with Existing Mobile Measurement Partners

Mobile Measurement Partners (MMPs) are platforms that help marketers track mobile app installs, user engagement, and other key metrics. They provide comprehensive analytics to understand the performance of mobile marketing campaigns. Examples of popular MMPs include Appsflyer and Adjust.

If a client uses an MMP like AppsFlyer or Adjust and wants to continue using it for app event tracking, they can integrate the Meiro SDK solely for mobile push notifications.

By setting the automaticTrackingEnabled configuration to false, the Meiro SDK will collect only events related to mobile push, such as token registration, message received, and message click events.

This allows the client to benefit from Meiro’s mobile push capabilities without duplicating event-tracking efforts already handled by the MMP.

Tracking Events

Understanding user behavior and enhancing app performance can be achieved by tracking events with the Meiro SDK and the Mobile Push channel.

Tracking events with Meiro SDK

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.

Tracking events with Mobile Push

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).
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.

SDK updates

How Updates Work

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.

Expected Frequency

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.

Requirements for Clients

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.