Article summary
Read avatar head count separately from the age and gender values. Flag group images and missing data before using LINE results in individual-level reporting.
An example export shows an avatar head count of two and one value in each of the age and gender columns. Those are the values the task returned. The row does not establish which person uses the account or whether the demographic values can be assigned to a particular person.
Give the row a status you can trace
Keep the original export. On the working copy, label the row “group avatar, attribution unverified.” If the next step is an individual age summary, keep the row pending. The reason will be visible when someone asks why the number of age records is smaller than the input list.
Similar-looking rows may need different labels:
- Missing head count, age present. Record that head count is unavailable. If verified attribution matters for the report, keep this row separate.
- Head count of one, no age. Leave age blank. Keep the underlying phone and screening record.
- Head count of one, age present. You have a returned profile value. If your report requires a verified personal age, apply your own evidence standard. A single-person image could still be old or depict somebody else.
AppShai lists avatar, head count, avatar type, gender, and age as separate LINE age-and-gender fields.[1] Keep your own attribution review in a separate field so the task output and your reporting decision can be traced independently.
See what changes in the report
Suppose 42 of 50 rows meet the project's reporting criteria, five have no age, and three have group avatars with unverified attribution. Report the age distribution on 42 records and make the eight exclusions visible. If another team needs to evaluate the LINE contact channel, it can use the separate registration result. The original records stay available even when some profile values are excluded from the summary.
If a colleague later asks why a row was left out, the review note provides the reason and the source values are still on file.
Source
- AppShai LINE screening fields · Separate field sets for age and gender and for registration.
