logoDocument
Search
Login

EngageLab AppPush Feature Update Log

November 13, 2025

Support for More Multilingual Push Notifications

Newly added support for Lao, Ukrainian, European Portuguese, Argentine Spanish, European Spanish, Latin American Spanish, and Brazilian Portuguese.

👉 Multilingual Code

November 10, 2025

1. Push Alert Functionality

The push alert feature is now officially live, enabling timely notifications to relevant personnel before push anomalies impact business operations.

Current Capabilities:

  • Supports SMS and Email alert methods
  • Alerts for large target push task backlog
  • Helps identify peak-time push congestion in advance, reducing business delay risks

2. Multilingual File Upload for Push Notifications

To meet global operational needs, AppPush now supports batch uploading of multilingual text files.

Key Features:

  • Upload multiple language versions at once
  • Automatically match language fields
  • Reduce configuration costs for multilingual scenarios

3. Sensitive Word Filtering for Push Notifications

The system will automatically detect sensitive words when creating push tasks.

Purpose:

  • Prevent the accidental push of non-compliant content
  • Protect brand image and compliance safety
  • Improve the review quality of enterprise push operations

4. REST API Optimizations for Push Lifecycle Queries

1) Enhanced Lifecycle Query API

Newly added fields include:

  • Status update time
  • Attrition stage
  • Failure reason
  • Failure code

👉 Lifecycle Status Query Documentation

2) Push Creation API Supports User Segmentation Fields

  • Enables differentiated pushes to specific tags/user groups
  • Suitable for precise marketing, A/B testing, user segmentation alerts, etc.

👉 Push API Documentation

July 1, 2025

1. Batch Single Push API Released

A new batch single push interface is introduced to send one-to-one push messages to multiple users at once, suitable for high-concurrency personalized message scenarios.

  • Supports batch input of multiple CIDs
  • Server-side request merging reduces API call costs
  • Applicable to personalized touchpoints for operational activities, order notifications, etc.

👉 Usage Documentation

2. Push Creation API Adds cid Field

The push creation API now includes the cid (client identifier) field, enabling precise messaging to individual users and significantly enhancing synergy with the batch single push API.

Applicable to:

  • Precisely reaching a specific user
  • Supporting risk control and verification-related pushes

👉 API Documentation

3. Message Statistics API Adds planID and Other Fields

To enhance operational analysis capabilities, the statistics API now returns associated indicators for push plans, including:

  • planID
  • Subtask-level data association
  • Clearer multi-task link tracking capabilities

👉 API Documentation

4. Support for Push Fields to Avoid Duplicate Sends

Helps businesses reduce the risk of harassment caused by duplicate notifications.

👉 Usage Guide

April 18, 2025

1. Intelligent Time Sending Support (Free Trial)

Intelligent time sending is designed to significantly improve notification click-through rates (CTR). The system will:

  • Record users' recent active times based on their activity on EngageLab SDK-installed apps/websites
  • Automatically calculate the most likely successful contact time for users
  • Send notifications according to users' terminal time zones

Even for new users without historical data, the system supports:

  • Immediate sending
  • Sending at a specified time in the terminal time zone

Applicable Scenarios: Enhancing DAU, reactivating dormant users, reducing disturbance rates, and improving the efficiency of reaching multi-regional audiences.

2. Push Plan Released

Push Plan is a set of capabilities for managing multiple push tasks and providing unified performance analysis, particularly suitable for operational activities or promotional cycles.

Key Capabilities Include:

  • Centralized management of multiple tasks
  • Unified performance data analysis (delivery volume, display volume, click volume, etc.)
  • Cross-task performance evaluation for large-scale events like 618 and Double 11
  • Support for both API and WebPortal
  • Full-process management from push creation to execution and statistical analysis

Core Value: Enables operations teams to "get a clear view of the entire campaign's reach effectiveness."

👉 Usage Documentation 👉 Push Creation API Supports Push Plan 👉 Push Plan Management API 👉 Push Plan Statistics API

December 12, 2024

1. Push Validation Interface

Before client integration is complete, the server can pre-validate whether the push interface is available, allowing customers to verify server-side push capabilities in advance.

👉 Interface Documentation

2. OPPO Notification Message Classification Adaptation

OPPO has released new requirements for notification classification, controlled via the category and notify_level fields. This update includes:

  • Reusing the options.third_party_channel_category field in the Push API to adapt to the OPPO channel
  • Adding the notify_level field to meet the new requirements

Reference Documentation:

3. Optimization of Server-Side Alias Binding Logic

Optimized the binding logic between alias and RID: When a specific alias is already bound to an RID, binding the same alias to a new RID will update it to bind to the new RID.

October 21, 2024

1. Support for Tag and Alias Push

Newly added support for tag and alias push, enabling operations personnel to more flexibly reach target users.

alt text

2. Support for Push Test Mode

A new push test mode is introduced, suitable for development or debugging scenarios, reducing the impact on real users.

👉 Feature Description Documentation

September 21, 2024

1. Support for In-App Messaging

👉 In-App Messaging Operation Guide

2. Support for Setting Android Manufacturer Channel Features in Console

alt text

July 24, 2024

1. REST API Supports User Self-Cleanup

To meet data privacy compliance, maintain user data validity, and reduce data maintenance costs for both developers and the platform, new support is added for deleting users and their subscription information via REST API.

Common Deletion Scenarios Include:

  • Data Privacy Requirements: Terminal users request the deletion of their personal data.
  • Removal of Inactive Subscriptions: For example, users changing devices or long-term inactivity on the app or web.
  • Improved Push Efficiency: Reducing resource waste caused by invalid subscriptions.
  • Optimized Console Data Accuracy: Metrics such as cumulative user count and notification toggle on/off numbers become more precise.
  • Lower Maintenance Costs: Regular cleanup of inactive users reduces system redundancy.

👉 User Deletion API

2. Support for Viewing Push API Call Statistics

The console now displays push API call statistics, providing developers and operations personnel with clearer insights into push usage and business behavior.

This data can be used for:

  • Analyzing system and business call situations.
  • Assisting in assessing the health of the push link.
  • Providing data support for operational strategies (e.g., peak push periods, usage habits, etc.).
icon
Contact Sales