Article summary
Normalize Argentina +54 mobile phones across domestic 15 and international 9 conventions, then validate WS Full Format fields and mapping conflicts.
The hardest part of an Argentina WhatsApp Full Format run is not selecting the task. It is avoiding the direct concatenation of domestic notation after +54. Argentine mobile phones may appear domestically with an area code plus 15, while international mobile notation uses a 9 after +54 and removes the domestic 15. Apply a versioned rule with provenance; one global string replacement is unsafe.
One mobile phone can arrive in several forms
| Source notation | Processing concern | Typical defect |
|---|---|---|
| Domestic with 0 and 15 | Identify area code, remove domestic markers and create mobile international form | 15 retained as subscriber digits |
| Already contains +54 9 | Validate the whole structure; do not add another 9 | +5499… output |
| Local number only | Require geographic evidence | Guessed area code |
Preserve evidence before applying a rule
Keep phone_raw, province_hint, source, normalization_rule and contact_id in staging. Convert only records with sufficient evidence. Missing area codes, implausible lengths and country conflicts enter accountable review. Do not assign a Buenos Aires code merely to increase the apparent success rate.
TXT is the upload, not the working paper
AIPUSH accepts one phone per line as TXT. Customer details, addresses and orders remain in the company system; the file contains only final normalized phones. Save its hash and row count so the returned workbook remains attached to a particular transformation version.
Use Full Format only for a genuinely broad decision
Select WS Full Format only when one approved process needs the wider registration, activity, profile, avatar and business-account observations. WS Registration is smaller when the question is registration alone; WS Activity is more governable for activity time. More columns do not make an audience more valuable.
Interpret the export in field families
| Family | Fields | Boundary |
|---|---|---|
| Association | Phone, WhatsApp mapped phone | Supports reconciliation; collisions need review |
| Activity | Activity time, active days | Dated observation, not permission |
| Profile | Gender, age, skin tone | May be unknown; not identity verification |
| Avatar/account | Avatar, avatar type, business account | Does not prove holder or purchasing power |
Stratify Excel acceptance by Argentina rule path
Reconcile unique inputs and returned rows, then report records that already had +54 9, records converted from domestic 15 and records sent to manual review. Compare missing and collision rates across those paths. A whole-batch “match rate” can hide one area-code transformation that consistently failed.
Never overwrite the source phone with a mapped phone
Store the WhatsApp mapped phone in a relationship table with observed_at and batch_id. Pause promotion on one-to-many, many-to-one or structurally implausible +54 relationships. Portability, shared devices and historical entry defects can all produce differences; an automatic overwrite damages the customer master.
Restrict profile-field interpretation
Age, gender, avatar, skin tone and avatar type may be missing, stale or unrelated to the account holder. Reports disclose coverage and unknown rates. Never fill demographics from an image or use them for identity, credit, employment or sensitive targeting decisions.
What a qualified Argentina handover contains
Deliver the +54 transformation note, exception phones, TXT hash, task date, raw Excel, field dictionary, coverage table and mapping-collision list. Marketing eligibility still comes from provenance, channel permission and opt-out records. Formatting answers “how is this phone represented?” and Full Format answers “what observations returned in this run?” Neither answers “who may be messaged?”
