Using Aliases and Tags: The Core Means for Precision Push

I. Core Concept Explanation

1. Alias: Binding Business ID with Push ID

Aliases are used to establish a one-to-one mapping between the user unique identifier (e.g., userID, phone number, email, etc.) in the business system and the registration ID (registrationID / UID) in the EngageLab push system.

Registration ID is a unique identifier generated by the WebPush or AppPush SDK for each user, used for push message identification. It is usually meaningless to the business side and is not strongly bound to the device.

Core Features:

• 🧩 One-to-one binding: Each registration ID can only bind to one alias.
• 🧠 Business recognizability: Uses the original user ID from the business system, facilitating business logic.
• 🔒 Persistent validity: The binding relationship remains valid unless explicitly unbound.

Application Examples:

• Order status change notifications (e.g., user123's order has been shipped)
• Account security notifications (e.g., user456's password has been changed)

2. Tag: Dynamic Grouping Based on Attributes

Tags are used to label users' attributes, behaviors, or statuses, enabling dynamic segmentation and group-based push notifications.

Core Features:

• 🔁 Many-to-many relationship: A registration ID can have multiple tags, and a tag can correspond to multiple users.
• 📈 Real-time updates: Supports dynamic addition and removal of tags to respond to user behavior changes.
• 🧱 Supports multiple dimensions: For example, "VIP member," "inactive for 30 days," "iOS user."

Application Examples:

• Push activation rewards to "VIP users inactive for 3 consecutive days."
• Send limited-time reminders to users with items in their shopping cart but not checked out.

II. Why Use Aliases and Tags?

🎯 Problems Solved

EngageLab's push registration ID is automatically generated by the SDK and is not directly related to the business system's users. To achieve business-level precision push, developers need to:

• ✅ Establish a binding between user ID → registration ID in the business system (using aliases).
• ✅ Segment users into different groups based on business needs (using tags).

✨ Summary of Core Value

III. Detailed Usage Instructions

1. Setting Aliases and Tags

✅ Server-side API Setup

• Documentation link: Set Alias and Tags

• Example Request:

              
              POST /v4/devices/{registration_id}
{
    "tags": {
        "add": [
            "VIP",
            "iOS user"
        ]
    },
    "alias": "user_5678"
}

            

✅ Client-side SDK Setup

• Web SDK: setTagsAlias
• Android SDK: Tags and Alias API
• iOS SDK: Tags and Alias API

2. Initiating Push Notifications

✅ Console Operation

• Select tag or alias user groups on the push creation page.

✅ API Method

• Documentation link: Create Push API

• Example Request:

              
              POST v4/push
{
    "from": "push",
    "to": {
        "tag": [
            "VIP"
        ],
        "tag_and": [
            "Inactive for 30 days"
        ]
    },
    "body": {
        "platform": "all",
        "notification": {
            "alert": "Hi, MTPush!",
            "android": {
                "alert": "Welcome Back Gift",
                "title": "Dear VIP user, welcome back! Claim your exclusive offer now."
            },
            "ios": {
                "alert": {
                    "title": "Welcome Back Gift",
                    "body": "Dear VIP user, welcome back! Claim your exclusive offer now."
                }
            }
        }
    }
}

            

IV. Best Practice Recommendations

✅ Three-tier Tag System Design Suggestions

V. FAQs and Notes

VI. Summary

By properly configuring aliases and tags, developers can:

• 🧠 Reduce development complexity and maintenance costs.
• 📊 Improve push precision, conversion rates, and ROI.
• 🔄 Cover the entire user lifecycle from activation to retention.

👉 For more information, please refer to the EngageLab Developer Documentation