Article summary
Separate Aruba +297 phones, foreign visitor numbers, booking dates and WhatsApp activity observations without turning one-trip contacts into permanent audiences.
A customer list for an Aruba hotel or tourism operator may contain mostly phones that do not begin +297. Visitors commonly keep their home-country numbers. Filtering only +297 misses real customers, while labelling every phone “an Aruba user” creates false market data.
Decide which meaning of Aruba you are measuring
| View | Classification evidence | Question it answers |
|---|---|---|
| Numbering plan | +297 or another code | Formatting and routing |
| Service market | Hotel, itinerary or order location | Customer of an Aruba operation |
| Current residence | User self-report | Regional communication |
| WhatsApp activity | Dated observation | Queue ordering |
One trip is not a permanent relationship
Retain stay_start, stay_end or service_date. When the service period ends, redefine purpose and retention. A phone must not remain in a local promotion pool forever merely because its owner once purchased something in Aruba.
When an activity check has operational value
Pre-arrival reminders, same-day transfers or short service recovery may require time-based ordering. Annual brand promotion usually does not need a person’s recent activity. Without an action that depends on a time window, choose a smaller task or do not check.
Treat activity Excel as a queue, not a personality score
WhatsApp Activity checking may return phone, activity time, active days, business-account observation, avatar and mapped phone. Use it to order authorised service work. Do not convert “recently active” into purchase intent, wealth or a high-value-traveller score.
Quarantine format issues across country codes
Preserve phone_raw and country_evidence, then validate against the appropriate numbering plan. A +1, +31 or +57 phone must not be forced into +297. Rows with no defensible country enter country_unknown so one conversion error does not contaminate the source list.
Travel details stay outside the TXT upload
TXT carries one phone per line. Booking number, name, hotel, date and permission remain in an internal crosswalk. Reconnect returned Excel through batch_row. A mapped-phone disagreement needs human review and must not merge two guests.
Use a different expiry for each journey stage
Pre-stay, in-stay and post-stay work have different purposes and expiry dates. Once checked_at is stale, the old result should not continue under an “activity” label. A new purpose requires its own basis.
Opt-out must survive a change of country-code view
The same contact may have a foreign phone, a mapped phone or a later replacement. Maintain an auditable suppression relationship so an opt-out does not disappear when the analyst switches from the +297 view to the visitor-phone view.
The lesson an Aruba page should leave
Market, phone and activity are three different dimensions. Separating them lets a tourism operator serve real visitors without expanding a temporary service context into permanent marketing permission.
