US WhatsApp number export specifications: CSV/TXT column names, encoding, delimiters and downstream import recommendations

In B2B overseas customer acquisition, selecting high-quality US WhatsApp numbers is only the first step. How to export the screening results in a standard format and smoothly import them into CRM, EDM or mass messaging tools often determines the efficiency of data usage. Many teams have misplaced export fields, garbled encoding, or inconsistent delimiters, resulting in duplication detection and import failure, wasting valuable time and budget.

This article takes the US WhatsApp number export function of the KK-DATA sifting platform as an example to break down the column structure, encoding selection, escaping rules of CSV and TXT in detail, as well as the best practices for importing to downstream tools. After mastering these specifications, you can quickly put effective data into operation after each screening, and truly achieve “screening, accurate guidance, and usability”.

---

Why is the US WhatsApp number export specification important?

Whether it is North American e-commerce promotions, independent station cold starts, or Telegram/WhatsApp community recruitment, the screening results of US WhatsApp numbers usually need to be connected to multiple downstream systems:

• CRM system (such as Salesforce, HubSpot) is used for customer stratification and follow-up
• EDM platform (such as Mailchimp) is used for email marketing (the number can be used as a unique identifier of the user)
• Batch messaging tools (such as WABA API, Telegram Bot) for instant reach

If the export format is not standardized (column names are not uniform, encoding errors, fields are not escaped), at least Excel will display garbled characters, and at worst it will cause data column misalignment, import failure, and even repeated deductions for detected numbers. Therefore, understanding and unifying export specifications is the key bridge between screening and operations.

---

What core fields does the KK-DATA US WhatsApp number screening result include?

KK-DATA’s filter number results support multi-platform export. For US WhatsApp number, the typical fields returned by the console are as follows:

Basic fields: number, activation status, activity, gender

Field name (example)	Meaning	Typical values
phone_number	Full international format number (including country code)	+12025551234
status	WhatsApp registration status	yes / no
active_days	Last active days (7/30/90 day window)	7, 30, 90
gender	Gender identification results (based on social graph)	male, female, unknown

Explanation:

• status=yes means that the number has been activated for WhatsApp and is a valid US WhatsApp activated number.
• The active_days field can help you filter recently active users to avoid sending messages to silent numbers.
• The gender field can be used for gender-targeted marketing. For example, women’s clothing brands can only export records with female=yes.

Extended fields: WhatsApp ID, region identification, detection time

In addition to the base fields, the export file may contain:

Field name	Description
wsid	WhatsApp user unique ID (can be used for deduplication or API operations)
region	Number country/region (such as US)
detected_at	Detection completion timestamp (UTC)
task_id	The filter task ID to which it belongs

These fields can help with more granular stratification: for example, sending a message only once to a number with the same wsid, or marking the detection date in the CRM for scheduled reactivation verification.

---

CSV export specifications: detailed explanation of column names, encoding and delimiters

CSV is the most versatile data exchange format. The CSV file exported by KK-DATA by default follows the following specifications:

Column naming rules and examples

• The first line must be the column name, and all column names should be in English lowercase and underlined (snake_case), such as phone_number, status, active_days.
• Fields should be separated by commas , without extra spaces.
• Each line records the test results corresponding to one number.

Example CSV content (first 3 rows):

phone_number,status,active_days,gender,wsid,region,detected_at
+12025551234,yes,30,male,1234567890abc,US,2025-03-20T10:30:00Z
+12025551235,no,0,unknown,,US,2025-03-20T10:30:01Z

Note: The order of fields may be adjusted with the version, and the first column name is the basis for positioning.

Encoding selection: Why must UTF-8 BOM be used?

• UTF-8 BOM (Byte Order Mark) is the standard way for Excel to recognize Chinese characters in the Microsoft Windows environment. KK-DATA export adds BOM by default to ensure that Chinese column names (such as the “US WhatsApp Number” label) are displayed normally in Excel.
• If UTF-8 without BOM is used, Excel may display Chinese characters as garbled characters.
• Using UCS-2 or UTF-16 is not recommended because many Unix/Linux downstream tools do not support it and the file size is large.

Operation suggestions: If you encounter garbled characters when importing into Excel, you can choose “Data → From text/CSV → Select UTF-8 for source file encoding”. KK-DATA export files are already compatible and usually no manual operation is required.

The delimiter is unified and the field contains comma escaping processing

• Default delimiter: English comma.
• Escape rules: If a field value contains commas, double quotes or newlines, the entire field will be wrapped in English double quotes ", and the double quotes within the field will be escaped using "". For example:

  note,"User wrote: ""Hello, World""",other_field

• Users are prohibited from manually changing the delimiter (such as changing to semicolon or Tab), otherwise the structure will be destroyed and downstream import will fail.

Verification method: Use a text editor (such as Notepad++, VS Code) to open the CSV file and check whether the first row and column names are aligned and no fields cross rows.

---

TXT export specification: concise mode and compatible scenarios

When you only need a pure list of numbers (without extra fields), the TXT format is the most concise choice. KK-DATA’s TXT export rules:

• One number per line, no column name lines.
• The number format is the complete international format (+country code + number), for example +12025551234.
• Encoding is usually UTF-8 without BOM (easy for scripting).
• Empty rows and duplicate rows will be automatically deduplicated during export (but it is recommended to use a deduplication warehouse for pre-processing).

Applicable scenarios:

• Paste directly into the number list upload interface of WhatsApp Business API
• Import Telegram contacts (one tgid/phone per line)
• Simple Python script to remove duplicates or count

Note:

• If the downstream tool requires no BOM header, use a text editor to remove the BOM (three invisible bytes: EF BB BF).
• If there are blank lines in TXT, you can use regular expression ^\s*$\n to remove them first.

---

How to correctly import exported data into common downstream tools?

Take three typical scenarios as examples:

1. Import CRM (Salesforce/HubSpot)

• Field Mapping: phone_number is mapped to the “Phone” field; status=yes can be entered as the “WhatsApp Verified” custom field; active_days is mapped to “Last Active Days”.
• Format Check: The number must contain the country code, and remove spaces, dashes, and brackets; Salesforce usually requires pure numbers or E.164 format.
• Removal rules: Use phone_number or wsid as the unique key to avoid duplicate creation of contacts.

2. Import EDM system (Mailchimp)

• Number Storage: Mailchimp’s “Phone” field supports E.164 format and can be imported directly.
• Field segmentation: Other fields in the CSV (such as gender, region) can be stored in Mailchimp custom tags (Tags) for subsequent segmentation and mass sending.
• Encoding: CSV uses UTF-8 BOM, select “UTF-8” encoding when importing in Mailchimp.

3. Import batch messaging tool (Telegram Bot API/WABA)

• TXT format is the most direct: one number per line, pay attention to deduplication.
• Restrictions: The daily session limit of WhatsApp Business API, Telegram Bot restrictions, etc. need to be understood in advance.
• Activity Filter: First filter the numbers with active_days ≤ 30 in the filter number results to avoid sending invalid contacts.

---

Best Practices for Screening and Exporting US WhatsApp Numbers

1. Generate → Filter → Export in one go: In the [Global Number Generation] (https://kkdata.cc/) module, first generate the target number segment (such as +1202, +1310), submit the screening number task, and export directly after the task is completed, reducing manual handling in the middle.
2. Export in batches: The upper limit of a single task is about 1 million. If the number is huge, it is recommended to export in batches (100,000 to 200,000 each time) to avoid Excel crashing.
3. Check field integrity before export: Preview the first 10 results on the “Task Details” page of the console and confirm that fields such as status and active_days have values.
4. Clear the export cache regularly: The console export link is usually valid for 7 days and needs to be downloaded again after expiration. It is recommended to archive it locally after downloading.
5. Balance Monitoring: US WhatsApp Number detection unit price depends on the platform type. For details, please see [official website billing page] (https://kkdata.cc/billing/). Check the estimated cost before submitting a task to avoid running out of balance.

---

FAQ

**Q: What should I do if the exported CSV file is garbled when opened in Excel? ** Answer: Normal method: Open it with Notepad and save it as UTF-8 BOM format; or use data directly in Excel → Import from text and select UTF-8 encoding. KK-DATA exports BOM by default. If it is still garbled, please check whether the encoding in the import settings is UTF-8.

**Q: Can numbers exported in TXT format be used directly for WhatsApp group messaging? ** Answer: Yes. However, it is recommended to first confirm that the number status is “open” and “active” on the KK-DATA console to avoid invalid sending. The exported TXT has one number per line, no redundant formatting required.

**Q: What is the specific meaning of the “US WhatsApp activation number” field in the exported file? ** Answer: The value of this field is “yes” or “no”, indicating whether the number has been registered in WhatsApp. Used to distinguish valid and invalid numbers to ensure that only marketing information is sent to users who have subscribed.

**Q: How many US WhatsApp numbers can be imported at one time? ** Answer: The upper limit for a single task is about 1 million. It is recommended to export in batches to avoid slow loading of downstream tools due to large files. KK-DATA supports exporting task results in batches.

**Q: What should I do if the exported fields lack the “WhatsApp avatar” information I need? ** Answer: Currently, the filter number mainly returns fields such as activation, activity, and gender. Unstructured data such as avatars are not included in the export scope yet. It is recommended to supplement through other APIs. Please pay attention to Official Documentation updates for future features.

---

Through standardized export formats and rigorous import processes, you can directly transform the screening data of US WhatsApp numbers into executable customer acquisition actions, reducing the loss of intermediate links. KK-DATA provides two standard formats, CSV and TXT, and supports custom field selection, adapting to most downstream tools.

Now go to the console to experience US WhatsApp number filtering and exporting:

👉 Log in to the console to start screening numbers

If you have any questions about the export format or need immediate help, please contact us through two-way customer service:

📲 https://t.me/kkdata_robot

More references:

• Official website: https://kkdata.cc/
• Usage documentation: https://docs.kkdata.cc/