Article summary
Normalize Vietnam +84 numbers, then interpret Zalo phone number, user ID, activity time, nickname and active-days fields without confusing activity with consent.
Vietnam Zalo activity checking begins with two questions: are the +84 phone numbers prepared correctly, and can the five returned fields be interpreted without overclaiming? Formatting errors break reconciliation; interpretation errors turn an activity observation into supposed permission or buying intent.
Prepare +84 numbers for the TXT file
Vietnam uses country code +84. Domestic phone forms may contain a trunk prefix that must be handled according to the numbering plan rather than by blindly adding 84 to the original string. Keep the raw value and country evidence, then create one canonical digit-only key.
ITU publishes Vietnam numbering-plan and mobile-range updates; see the Vietnam +84 numbering information. Allocation rules can change, so version any prefix logic.
What the five Zalo fields answer
| Field | Useful role | Does not establish |
|---|---|---|
| Phone number | Reconciliation key | Verified identity |
| User ID | Zalo-related identifier | Permanent customer key |
| Activity time | Time observation returned by the task | Future online time |
| Nickname | Returned name field | Legal name |
| Active days | Relative cohort signal | Purchase intent |
Build thresholds inside comparable cohorts
Recent customers, old leads and service contacts naturally have different distributions. Split the population by source, acquisition period and relationship before reviewing active days. A threshold should reflect measured behavior in that cohort, not a convenient number applied to the entire database.
Reconcile one Vietnam batch
- Retain internal ID, raw phone and evidence that the record belongs to Vietnam.
- Normalize the number and send ambiguous rows to repair.
- Create a TXT file with one number per line.
- Choose Zalo activity checking and download the Excel result.
- Join with the canonical phone key.
- Count returned, missing, duplicate and unmatched rows separately.
- Apply permission and opt-out state before creating business segments.
A blank is not automatically inactivity
A missing value may arise from input quality, task processing, visibility or reconciliation. Keep an explicit unknown state and record the exception reason. Only values defined by the selected task should enter activity bands.
When another Zalo service is the better fit
Use Zalo registration checking when the question is only whether a number is registered. Choose the gender-and-age service only when the approved use needs its profile-related fields, including age, gender and avatar attributes. Wider output creates wider handling obligations.
The business handoff
AIPUSH accepts the number list as TXT and returns task-specific Excel columns. The analyst should deliver a reconciled table, field definitions, unknown-rate summary and permission filter—not merely the downloaded workbook.
+84 formatting, the five activity fields and company authorization are independent layers. Zalo activity becomes useful only when all three remain visible in the analysis.
