This step is fundamental to
Posted: Mon Dec 23, 2024 6:23 am
Server-side data collection ( Profile API ): Server-side data collection is a secure and reliable way to send data, as it ensures a single, centralized source of truth. It is also very flexible, as it works independently of customer-related issues. This is how user profiles and behaviors can be collected, which is essential for creating and driving personalized customer experiences.
Client-side data collection (SDK): It allows capturing user interactions directly from their device. It is essential for capturing real-time data, such as clicks, views, and other interactions that provide insights into user engagement and preferences.
Step #2: Implementing the Mobile SDK
As mobile interactions continue to dominate user engagement, both basic and advanced SDK implementation steps remain crucial, enabling push notifications, in-app messages, user data collection, and a seamless transition between legacy and new systems.
capturing real-time data and ensuring that the mobile user experience is both comprehensive and personalized.
Stakeholders involved: mobile teams.
What's done: Basic and advanced mobile SDK implementations, data collection, and removal of legacy push notification SDKs.
Basic and Advanced Mobile SDK Implementation: Basic SDK installation covers fundamental features such as basic data gathering, push notifications and in-app messages, while Advanced accurate mobile phone number list SDK implementation may involve more complex features such as geolocation, notification center or integration with other data sources/destinations.
Data collection: This is the process of collecting data from the mobile environment, which is essential to understand user behavior on mobile devices and thus adapt the experience to mobile uses.
Removal of the legacy Push Notifications SDK: Replace the legacy SDK integration to ensure compatibility, streamline operations, and potentially take advantage of the improved features and reliability of the new versions. This can be done after an optional transition phase where both systems run concurrently.
Step #3: Implementing the Web SDK
The web experience is improved through the integration of a service worker as well as the implementation of JavaScript tags.
These tags are essential not only to track user interactions, but also to leverage the power of modern web applications, which allows to interact via web push notifications with all users, even when they are not logged in.
Stakeholders involved: web teams.
Client-side data collection (SDK): It allows capturing user interactions directly from their device. It is essential for capturing real-time data, such as clicks, views, and other interactions that provide insights into user engagement and preferences.
Step #2: Implementing the Mobile SDK
As mobile interactions continue to dominate user engagement, both basic and advanced SDK implementation steps remain crucial, enabling push notifications, in-app messages, user data collection, and a seamless transition between legacy and new systems.
capturing real-time data and ensuring that the mobile user experience is both comprehensive and personalized.
Stakeholders involved: mobile teams.
What's done: Basic and advanced mobile SDK implementations, data collection, and removal of legacy push notification SDKs.
Basic and Advanced Mobile SDK Implementation: Basic SDK installation covers fundamental features such as basic data gathering, push notifications and in-app messages, while Advanced accurate mobile phone number list SDK implementation may involve more complex features such as geolocation, notification center or integration with other data sources/destinations.
Data collection: This is the process of collecting data from the mobile environment, which is essential to understand user behavior on mobile devices and thus adapt the experience to mobile uses.
Removal of the legacy Push Notifications SDK: Replace the legacy SDK integration to ensure compatibility, streamline operations, and potentially take advantage of the improved features and reliability of the new versions. This can be done after an optional transition phase where both systems run concurrently.
Step #3: Implementing the Web SDK
The web experience is improved through the integration of a service worker as well as the implementation of JavaScript tags.
These tags are essential not only to track user interactions, but also to leverage the power of modern web applications, which allows to interact via web push notifications with all users, even when they are not logged in.
Stakeholders involved: web teams.