Article summary
Use order, address and provenance evidence to disambiguate Saint Martin market labels before processing phones and avatar visibility.
“Saint Martin” in a list is first a data-definition problem. If a business system mixes neighbouring territories, island names, language labels and free text into one value, avatar checking will not repair the geography.
Identify where the label came from
| Evidence | Use | Caution |
|---|---|---|
| Order service place | Where business occurred | Not necessarily residence |
| Customer address | Contact or fulfilment | Preserve the original |
| Phone number | Numbering plan | Does not decide market alone |
| Free-text label | Candidate clue | Needs human normalisation |
Build a territory dictionary and aliases
Store canonical_region, source_label and normalisation_reason. Preserve the raw label permanently so a mistaken normalisation remains traceable.
Let phone queues follow actual plans
Process every phone_raw under its own international code. A Saint Martin project name does not justify forcing an unsupported prefix onto national-looking strings.
Decouple avatar and geography
Image content cannot decide which side a contact belongs to, which language they use, their citizenship or where they live.
Use granular visibility states
Record avatar_observed, not_observed, visibility_limited and task_unknown separately. A blank is not proof that no avatar exists.
Keep geography guesses out of TXT
The execution file contains one phone per line. Orders, addresses and normalisation reasons stay in the internal crosswalk; connect Excel only to an established region dimension.
Sample high-conflict sources first
Prioritise free text, partner imports and historical spreadsheets for review. Structured orders often provide more stable business evidence.
Give the data team a refusal state
Allow region_unresolved when evidence is weak. Do not force a choice merely to eliminate dashboard blanks; an honest unknown is more useful than false certainty.
The unique value of this page
This is not a generic avatar tutorial. It explains how territory ambiguity contaminates phone screening and specifies the data-governance work required before profile review.
