US data export specifications: CSV/TXT listing, encoding and downstream import guide

When you complete the US number filtering on the KK‑DATA platform and export the cleaned US data, the column name meaning, encoding format and delimiter selection of the file directly affect whether the downstream tools can be loaded correctly. A standardized export can avoid problems such as garbled CRM import, identification errors by mass sending tools, and failure to remove duplicates. This article explains in detail the definition of US data export fields, format settings, downstream import steps and common pitfall avoidance methods to help the overseas customer acquisition team smoothly integrate the cleaned US customer acquisition data into the business system.

What are the US data export specifications? Why is it important?

Export specification refers to the field column name definition, character encoding and delimiter standard of the sieve number result file. Lack of specifications, such as:

• Field column names are not uniform and cannot be automatically mapped when imported into CRM;
• The encoding is not UTF‑8, and Excel opens Chinese garbled characters;
• The delimiter is ambiguous (such as a comma in the number), resulting in column misalignment.

Standard export can ensure that downstream systems (CRM, EDM, mass sending tools) correctly parse each row of data, avoiding duplication of work and data failure. For teams that process US number data in batches, standardized export is the foundation for efficient operations.

Detailed explanation of core column names for KK‑DATA US data export

Taking the “US Number Filtering” task on the official website https://kkdata.cc/ as an example, the exported CSV usually contains the following common fields. Note: There are differences in the field sets returned by different detection platforms (Telegram, WhatsApp, Line, etc.). The final listing is subject to the preview of the console task results page.

Platform and status fields

Column name	Meaning	Example values
phone	US number in international format	+14155551234
country	Country code (ISO 2 digits)	US
platform	Detection platform (such as tg, wa)	tg
detect_type	Detection type (activated/active)	status
status	Whether the number is activated/valid on the platform	Activated/invalid

• status Determination logic: For Telegram, “activated” means that the number has been registered with Telegram; for WhatsApp, it means that the number has been registered with WhatsApp and may be able to send messages.
• platform Values: tg (Telegram), wa (WhatsApp), line (Line), zalo (Zalo), etc.

Activity and gender fields

Column name	Meaning	Example values
active	Active status (time window can be specified)	Active / inactive in the past 7 days
gender	Gender (detectable on some platforms)	male / female
age	Age group (only for crowd trend interpretation)	30

• active: You can select “Active in the past 7 days”, “Active in the past 30 days”, etc. during task settings, and the window will be accurately reflected when exporting.
• age: From platform public information or behavioral inference, reflecting age group trends (such as “about 30 years old”), non-ID card level accurate data. Suitable for rough screening of crowd portraits.
• Some platforms also return tgid (Telegram user ID), wsid (WhatsApp identification code), etc. for deduplication or additional docking.

Export format settings: CSV vs TXT, encoding and delimiter

When performing an export in the KK‑DATA Console https://app.kkdata.cc/ there are two formats to choose from. Core differences:

Properties	CSV	TXT
Content	Complete field (including column name row)	Pure number list, one number per line
Column name	The first line is the column name line	None
Encoding	UTF‑8 with BOM (recommended)	UTF‑8
Separator	Comma	None (one number per line)
Applicable scenarios	Import CRM, database, Excel analysis	Directly import mass sending tools, number pools

Be sure to confirm: It is recommended to select UTF‑8 with BOM (Byte Order Mark) for the output encoding, which can help Excel recognize Chinese. The delimiter is fixed to comma.

CSV format (recommended) and field order

• The first line of CSV is the column name line, and each subsequent line corresponds to one record.
• Field order remains consistent with console preview. Unnecessary columns can be unchecked before exporting to reduce file size and downstream cleaning costs.
• Suitable for structured analysis: pivot tables and formulas can be used after importing into Excel; tables can be quickly created when importing into a database.

TXT format (pure number list) and applicable scenarios

• TXT One number per line, without any additional information.
• Suitable for directly injecting third-party mass sending bots (such as Telegram sending plug-ins) to avoid the field mapping step.
• Note: Some mass sending tools require that the number does not contain the + number, which can be replaced in batches with a formula or text editor before exporting.

How to import US data export results into downstream tools?

According to different business scenarios, the import operation is slightly different.

Import CRM (such as HubSpot, Salesforce) - Field Mapping Steps

1. Log in to the CRM backend and select “Import Contacts/Customers”.
2. Select CSV file upload, CRM will automatically recognize the column names (such as phone → mobile phone number, country → country).
3. Manually correct the mapping: for example, map status to the custom field “whether to activate TG”.
4. Handle duplicate numbers: Most CRMs provide deduplication options, with phone as the unique identifier.
5. Confirm the import rules (update existing records or only add new ones).

Import email marketing platform - CSV cleaning and segmentation

• The US data export may contain non-email fields such as phone, gender, etc. Delete irrelevant columns before importing (only email required for B2C scenarios will be retained, but phone can be retained for SMS/WhatsApp marketing).
• If the single import volume exceeds the platform limit (such as 100,000 rows), import in batches.
• Check the email format (if there is an email field): Some platforms require that the email field column name be Email and be unique for each email.

Import Telegram/WhatsApp group messaging tool—number column extraction

• After exporting from CSV, copy the phone columns and paste into a new TXT file (one number per line).
• Check the requirements for mass sending tools: some tools require pure numbers (without country code prefix, such as 14155551234), and you can delete the beginning + in batches; some tools support the international format +14155551234, so keep it.
• If tgid or wsid is required, export CSV directly and copy the corresponding columns into the request body of the tool API.

Common mistakes in US data export and how to avoid them

Common Errors	Phenomenon	Solution
The encoding is garbled	When Excel opens the CSV, it displays “锟斤拷” in Chinese	Select UTF‑8 encoding when importing; or save it as UTF‑8 with BOM in Notepad
Fields are missing	After importing into CRM, the gender column is empty	Before exporting, confirm that the detection platform supports gender recognition; preview whether the column name is checked
Wrong delimiter	Number contains , causing misaligned columns	Check CSV for unexpected commas in numbers; wrap them in quotes if necessary
Null value rows are redundant	There is a blank row at the end of the CSV	Use a text editor to delete the last blank row after exporting; or skip the blank row when importing

CHECKLIST:

• Preview the column names before exporting and confirm that the required fields are checked.
• After exporting, use a text editor to open the first row and confirm that the column names are correct and there are no BOM garbled characters.
• Test the import with Excel (Data → From Text/CSV, encoding 65001) to verify the format.

Best Practices for US Data Export: Complete Process from Screen Number to Export

1. Generate US Number: Use KK‑DATA’s “Global Number Generation” module, select the country United States, and generate a prefix or random number segment. Generate for free.
2. Select country/platform filter number: Specify platform (such as Telegram), country US in the filter number task, and submit a task of no more than 100,000 lines per day (balance efficiency and time-consuming).
3. Set export columns: On the task results page, uncheck unnecessary columns (such as country if it is clear that it is US data), and retain phone, status, active, gender, age, etc.
4. Select format: If subsequent analysis is required, select CSV (UTF-8 with BOM); if it is only for mass sending tools, select TXT.
5. Download Verification: First download 100 samples, and use Excel or Notepad++ to verify the column names, encoding, and delimiters. Download the complete file after confirming it is correct.

Daily Batch Recommendation: It is recommended that a single task should not exceed 100,000 lines to avoid slow processing of large files. After exporting, do a sample verification first and then merge it into the final data set.

FAQ

**Q: What should I do if the CSV file exported from the US data is garbled in Chinese when opened in Excel? ** A: The reason is that the default encoding of CSV is UTF‑8 (no BOM). Solution: First open the CSV with Notepad and save it as “UTF-8 with BOM” format; or enter Excel and use “Data → From Text/CSV” to import, and select 65001 encoding.

**Q: Does the TXT export only contain numbers? Can I customize the delimiter? ** Answer: Standard TXT export has one number per line, no extra fields. If additional delimiters (such as tabs) are required, it is recommended to select the CSV format and split by columns in downstream tools.

**Q: Is the age field in the US data accurate? Can it be regarded as the real age? ** Answer: The age field comes from the platform’s public information or behavioral inference, and reflects the age group trend (such as “about 30 years old”), which is not accurate data at the ID card level. It is recommended to only be used for rough screening of crowd portraits.

**Q: Are the country codes included in the export results unified into an international format? ** Answer: Yes. All numbers are stored in an international format (e.g. +1xxxxxxxxxx) to ensure consistent parsing across platforms. If the business system requires pure numbers, the + numbers can be deleted simply through batch processing.

**Q: Are the export fields the same on different platforms (Telegram/WhatsApp/Line)? ** A: Field sets vary by platform. For example, Telegram may return tgid, WhatsApp may return wsid, and Line may return uid. Please refer to the console preview for details. It is recommended to reference documentation to understand the field descriptions of each platform.

---

I hope the above specifications can help you efficiently complete the export and downstream import of US data. If you want to start screening numbers immediately, please log in to the console:

👉Log in to the console to start screening numbers Or contact customer service through two-way https://t.me/kkdata_robot to obtain operation guidance.