Article summary
Choose LINE Registration or Gender/Age by the decision needed in Japan and Korea, while separating phone format, profile unknowns and language preference.
For Japan- and Korea-facing LINE work, ask which field changes a lawful, low-risk decision—not which task returns more columns. Choose LINE Registration when the question is the registration result. Consider Gender and Age only for an approved profile-field analysis. AIPUSH does not offer a LINE Activity task.
The two tasks return different schemas
| Task | Export | Suitable question |
|---|---|---|
| LINE Registration | Phone, registration result | Organizing platform registration state |
| LINE Gender and Age | Phone, user ID, nickname, gender, age, avatar, people count, avatar type, skin tone | Approved field-coverage analysis |
| LINE Activity | Not available | Do not promise activity time or active days |
Maintain separate Japan and Korea phone rules
Version +81 and +82 transformations independently while retaining phone_raw and country_evidence. Apply each country’s domestic-prefix rule when creating international notation. One global “remove zero and add code” formula is unsafe. A phone’s country also does not prove where a cross-border resident currently lives.
Do not infer language from a phone
+81 does not guarantee Japanese preference and +82 does not guarantee Korean. preferred_language comes from user choice, an evidenced service conversation or an explicit setting, with source and date. When unknown, ask neutrally rather than guessing from nickname characters or avatar.
When Registration alone is sufficient
Two fields are often enough to review platform state in an existing customer database, assess import quality or reconcile a properly permitted queue. A smaller task reduces access to profile observations and missing-data work. It also reduces the temptation to turn demographics into sales scoring.
Conditions for a profile task
| Question | Required condition | If absent |
|---|---|---|
| Is purpose specific? | Approved and low-risk | Use Registration |
| Are unknowns accepted? | Coverage and blanks are reported | Do not fill guesses |
| Is access restricted? | Role controls and retention period | Keep out of general CRM views |
| Does it affect rights? | No sensitive or high-risk decision | Stop use |
Put TXT and Excel in their proper places
AIPUSH accepts a one-phone-per-line TXT. contact_id, language, orders and permission remain internal. Download Excel into staging, add batch_id, checked_at and task_name, then reconcile to CRM. Preserve original returned values and unknown states.
User ID and nickname are not permanent identity
A returned user ID, nickname or avatar does not prove legal identity and may change, be shared or depict someone else. Store it as a dated observation. It should not replace customer-provided name or the CRM master key without review.
Do not average Japan and Korea into one audience
Report +81 and +82 input volume, format exceptions, registration results, field coverage and unknown rates separately. Acquisition sources, sample composition and usage context differ. A combined “average profile” is hard to act on and can hide a defect in one country’s phone rule.
Permission still controls contact eligibility
Registration state, user ID and profile observations do not show that a person expects marketing. A checked record still needs LINE-specific scope, message purpose and suppression evidence. An opted-out customer is not revived by a different task or newly returned fields.
The simplest selection rule
If removing the profile columns would leave the business decision unchanged, do not collect them. If the question requires LINE activity time, the current service cannot answer it; choose another evidence source or business metric rather than substituting registration. An explicit “not answerable” is more valuable than a wide but misinterpreted workbook.
