Article summary
Map AIPUSH LINE Registration and Gender/Age fields while stating plainly that no LINE Activity task is offered.
If a procurement brief asks for “LINE activity screening in Japan,” AIPUSH cannot satisfy it by substituting a similar-looking field. LINE Registration and LINE Gender/Age tasks exist, but AIPUSH does not offer a LINE Activity task. Saying that at the beginning is more useful than hiding the boundary under terminology.
What does “active” mean in the requirement?
It may mean recent login, recent reply, friend relationship, message reachability or marketing engagement. Those are five definitions requiring different evidence. Without a source and observation window, an activity rate is only a precise-sounding label.
Available task and field matrix
| AIPUSH task | Returned fields | Answers recent activity? |
|---|---|---|
| LINE Registration | Phone, registration observation | No |
| LINE Gender and Age | Phone, user ID, nickname, gender, age, avatar, people in avatar, avatar type, skin-tone observation | No |
| LINE Activity | No current AIPUSH service | No |
What registration observation can support
For a Japanese phone pool with documented provenance and purpose, LINE Registration may contribute a current registration observation to channel planning. A non-registration observation is not an empty-number verdict and does not show that a customer has left Japan.
Why avatar or nickname cannot stand in for activity
A visible avatar, populated nickname or returned user ID is a profile observation at task time. It does not report login, message interaction or reply behavior. Substituting profile completeness for activity systematically overstates old accounts that no longer interact.
Japanese phones may be reassigned
A LINE Help Center notice updated in 2026 explains that a cancelled phone may later be contracted by another person and registered to LINE. See the official registered-phone guidance. A phone-to-account observation is not a permanent identity relationship.
Three better questions when activity is unavailable
- Is the real requirement only registration observation?
- Can reply, order or service time in the company’s own systems provide interaction evidence?
- Without permission and a business event, should the list be operated at all?
Combining TXT with an internal event table
TXT contains one phone per line, without name, membership tier or order. Excel rejoins with batch_row. Store LINE registration as an event with checked_at while keeping first-party last_reply_at or last_order_at separate.
Limits of the Gender and Age task
Profile fields are not self-declarations and should not be used for identity verification, minor detection or high-impact decisions. Language and form of address should come from user choice. LINE itself treats phones, LINE IDs and messages as important private information in its privacy-protection guidance.
Write a procurement brief that cannot mislead
Rewrite the requirement as: “Observe LINE registration for Japanese phones; return phone and registration observation. Determine recent interaction from our internal event table.” Fields, provenance and responsibility are explicit, so an unrelated column cannot masquerade as activity.
The boundary is the answer
The absence of a LINE Activity task does not make the project impossible. It requires account observation and first-party behavior to remain separate. A clear “not currently supported” is more reliable than a complete-looking Excel file that cannot answer the decision.
