Article summary
Compare Vietnam Zalo activity and age/gender tasks, including +84 preparation, five activity fields, profile columns, unknowns and analysis limits.
When a Vietnam Zalo project mentions both activity and age/gender, do not treat the services as basic and premium versions of the same task. Zalo activity checking answers activity and account-field questions; the gender-and-age service adds profile-related fields. Define the use before deciding whether both are necessary.
How the two schemas differ
| Service | Returned fields | Suitable question |
|---|---|---|
| Zalo activity | Phone, user ID, activity time, nickname, active days | Activity and account-field grouping |
| Zalo gender and age | Phone, user ID, activity time, nickname, gender, age, avatar, people count, avatar type, skin tone | Approved profile analysis |
Qualify +84 numbers from source evidence
Domestic trunk prefixes and +84 international forms should be transformed according to Vietnam’s numbering plan. Preserve raw phone, country evidence and rule version; never infer Vietnam from length alone in a mixed-country file. ITU’s Vietnam +84 numbering information can support current range rules.
Coverage comes before combined analysis
Report non-missing rates for activity fields, age, gender and avatar before calculating distributions. If one acquisition source has much lower age coverage, comparing its “25-plus” share directly with another cohort can create selection bias.
Do not fill demographics from the avatar
An avatar may not depict the user, may contain several people or may be old. Store gender, age, skin tone and avatar-type values according to the task definition. Do not use AI or visual guesses to fill unknowns.
Design a safe combined data view
Use the internal contact ID as the stable key. Store phone, Zalo user ID, activity observation and profile observation separately with batch ID and checking date. A view can select current approved observations without overwriting the source result.
A segment is not permission
“Recently active women aged 25-plus” may be an analytical label, but it does not prove marketing consent or guarantee field accuracy. Before communication, check source, permission, opt-out and message purpose.
When to run only one task
Activity grouping does not require gender and age. Registration cleanup should use Zalo registration checking. Process the broader profile schema only when it changes a defined and permitted decision.
Deliverable for the Vietnam team
AIPUSH accepts the +84 number list as TXT and exports Excel by task. The handoff should include coverage rates, unknown definitions, join results and permission filters alongside any segment counts.
High-quality Zalo analysis keeps activity, profile attributes and consent separate instead of compressing them into one “target user” label.
