Product Overview

EngageLab MA (Marketing Automation) omnichannel marketing automation platform enhances enterprise marketing efficiency and user conversion rates through contextual and personalized user journey design, precise omnichannel reach, AI strategy optimization, and insights analysis capabilities.

Product Usage Path

Create a Project

Use projects to carry out your business

Data Requirement Planning

Before designing event tracking, first understand the business scenarios, sort out and confirm the business processes, user operation paths, and various different segmented scenarios. Define user behavior paths based on the specific operational methods and processes of users on the product.

Scenario decomposition strategy: Understand the business, set standards, plan goals, determine strategies, and create plans.

Data requirement planning is the foundation of business development and directly affects subsequent data applications and business operations. We should try to avoid the following common problems:

• Waste of invalid tracking: Sometimes, for long-term goals or concerns about incomplete tracking affecting business analysis, tracking is planned with a "better too much than too little" approach. We often find a large number of historical tracking points that no one queries, leading to an increasing number of events in the environment. When designing the tracking system, we need to repeatedly confirm whether these tracking points are related to the core business metrics. Otherwise, it wastes not only storage and traffic costs but also the more valuable time of product and development personnel.
• Missing key information in tracking: As product operation personnel, when using tracking events or event attributes for business analysis, it is often discovered that key events are missing, or the key event attributes of tracking events are missing, resulting in inaccurate analysis results and hindering business operations. Therefore, it is worth spending more time thinking and planning about which tracking events are needed and what event attributes are required for those tracking events.
• Missing tracking documentation: When creating tracking points, try to standardize naming and clearly document the triggering timing of the tracking points. This information is an important basis for other colleagues to understand and use the tracking events.

Data Collection Plan Design

Design tracking points based on your industry scenarios and general business scenarios. You can contact EngageLab technical support for guidance.

Data Collection and Tracking Implementation

EngageLab MA provides Android, iOS, Web SDKs, and REST API interfaces to support reporting user data and behavior events.

1. Add Data Sources

• Data Source Setup Guide

2. Create Events and Attributes (Optional)

• Event Management
• Attribute Management

3. Report Data via SDK or API

• Android SDK Integration Guide
• iOS SDK Integration Guide
• Web SDK Integration Guide
• Rest API Event Reporting

Build a User System

• Understand the generation of unique user IDs
• Set user identifiers on Android, iOS, and Web

Add Reach Channels

Currently, EngageLab MA supports five channels: AppPush, WebPush, Email, SMS, and WhatsApp.

If you have additional channel requirements or wish to integrate the above messaging channels from other service providers, you can contact our sales team.