Screening Source Export Standard: CSV and Universal Field Specifications for Seamless Integration with Downstream Systems

Overseas marketing teams process thousands of numbers daily through screening platforms that batch verify validity, activity, and gender. The results are exported as CSV or TXT files. But the problem arises: when exported directly into CRM, field names don’t match; imported into data analysis tools, formats are incompatible; sent to business colleagues, they ask “what is this tgid?” The core pain point is the lack of field specifications in the screening source export. This article uses KK-DATA as an example to detail data export standards for CRM, EDM, and private messaging tools, covering field mapping for CSV, tgid, and wsid, so you can use exports directly without repeated cleaning.

---

Why Is Field Standardization in Screening Source Export So Important?

Downstream systems (CRM, Marketing Automation, Data Middle Platform, Telegram broadcast plugins) have strict requirements for data formats. Slight deviations in field name casing, separators, or boolean representation require manual or script-based conversion. For a screening result of 100,000 records, cleaning often takes 2–3 hours. Some teams even give up using detailed gender/activity labels and only keep the simplest “valid/invalid,” wasting the deep capabilities of the screening platform.

Standardized export brings three direct benefits:

• Automatic mapping: When importing into CRM, field names and data formats match directly, eliminating the need for intermediate tables.
• Reduced manual work: Cleaning time drops from hours to minutes (only need to check file encoding and delimiter).
• Higher ROI: Every dollar spent on screening turns into directly usable structured data.

---

Common Export Fields from Screening Sources (csv, txt)

Regardless of the screening platform, export files contain a set of core fields. Below is a field list based on KK-DATA and industry common practices, along with their business meaning and format examples.

Field Name (Common English)	Business Meaning	Format Example	Common Issues
phone / phone_number	Full international number (with +)	+8613800138000	Some platforms omit +, downstream CRM may need to add it back
country_code	International dialing code (numbers, no +)	86	Used for country-based statistics
iso_country	ISO two-letter country code	CN	Distinguish nationality labels of data sources
tgid	Telegram internal unique ID (numeric)	1234567890	Used for TG private message SDK calls, not a phone number
wsid	WhatsApp internal ID	[email protected]	Used for WhatsApp Business API
status	Number status (valid/invalid/unknown)	valid / invalid / unknown	Some platforms output 1/0
active_days	Recent active days (Telegram)	15	Precise integer or range (e.g., 15-30)
gender	Gender identification based on avatar (Telegram)	male / female / unknown	Different platforms may use M/F/U
check_time	Detection timestamp (UTC+8)	2024-01-15 10:30:00	Ensure timezone alignment
platform	Detection platform	telegram / whatsapp / imessage	Differentiate in multi-platform tasks

Platform-Specific Fields: tgid, wsid – Positioning and Export Significance

• tgid: Telegram user’s unique numeric ID. It is not a phone number but can be used for the sendMessage interface of Telegram broadcast bots. Exporting tgid allows direct private messaging to users via API without storing phone numbers.
• wsid: WhatsApp internal ID, usually formatted as [email protected]. This is the standard identifier required by WhatsApp Business API for sending messages or querying status. When screening detects a valid number, exporting wsid allows direct connection to the sending system.
• These two fields are not needed in all scenarios. If you only need number validity verification without subsequent active push, you can skip them.

Number Status Fields: Export Label Specifications for Valid, Active, Gender

• Valid (Status): At minimum indicates the number is registered on the corresponding platform. It is recommended to use valid / invalid instead of yes/no, as downstream systems often have ambiguity about boolean values.
• Active (active_days): Reflects whether the user has been online recently. KK-DATA supports windows like 7 days, 15 days, 30 days. The exported value is usually an integer (e.g., 7 means active within 7 days). Some scenarios prefer interval labels (e.g., 7d_active), but the standard practice is precise days.
• Gender (gender): Based on avatar recognition, not 100% accurate, but useful for targeted profiling. It is recommended to export as male / female / unknown for easier analysis.

---

How to Plan Export Fields to Match Downstream Systems?

When creating a screening task, do not select all available fields. Instead, “streamline and match” based on the target system. Below are field recommendations for common scenarios:

Downstream Scenario	Recommended Export Fields	Reason
Telegram Broadcast (TG bot)	phone, tgid, status, active_days	tgid is needed for sending; activity determines whether to disturb
WhatsApp CRM Import	phone, wsid, status, country_code	wsid used for auto-matching WhatsApp contacts
Data Analysis / User Profiling	phone, gender, active_days, country_code, check_time	Needs multi-dimensional labels for cross-analysis
Bulk Marketing Email (EDM)	phone (as unique identifier), status, gender	Only need platform valid status and gender; reduce field burden

Common Field Format Requirements from Downstream Systems

• CRM (e.g., HubSpot, Salesforce): Mostly use CSV import. Field names must exactly match CRM object field names (case-sensitive). Empty values should be represented as empty strings or NULL.
• Databases (MySQL/PostgreSQL): Timestamps should be in YYYY-MM-DD HH:MM:SS format. Numeric fields should not have thousand separators. Boolean values use 0/1.
• Reporting Tools (Tableau, Power BI): Prefer wide table structure, one dimension per column, but avoid many repeated empty values. It is recommended to keep the original integer for activity fields and let visualization tools group them.

Avoiding Field Redundancy: How to Export Only Needed Columns

Core idea: Information not used during export is noise. KK-DATA allows you to customize export columns when creating a task. You can uncheck unneeded fields (including tgid, wsid, or even phone itself). For example, if you only need activity analysis, select phone + active_days + country_code and skip the rest. This results in a smaller file with fewer fields, making import into any system clearer.

Operation Suggestions:

1. In the console task creation page, go to the “Export Settings” tab.
2. Select and reorder fields as needed.
3. Preview the first 2 lines to confirm field order and format.
4. Save the export template for reuse next time.

---

Post-Export Data Cleaning and Field Mapping Practice

After obtaining the CSV file, you usually need two to three simple processing steps before direct import into downstream systems. Below is the standard workflow:

Step 1: Remove BOM and Special Characters
Use Notepad++ or VSCode to convert encoding to UTF-8 without BOM. Some CRMs (e.g., Zoho) will error due to BOM.

Step 2: Standardize Timestamp Format
If the downstream system requires ISO 8601 (2024-01-15T10:30:00Z) but the export is 2024-01-15 10:30:00, convert using Excel or a small script.

Step 3: Boolean Conversion
valid/invalid → 1/0 (use find & replace or formula =IF(A2="valid",1,0)).

Step 4: Field Name Mapping
Change screening platform field names to the downstream system’s expected names. For example, KK-DATA exports phone, but CRM requires Phone – modify the CSV header directly.

Step 5: Verify Data Integrity
Check for empty rows, misalignments, and garbled characters. Pay special attention to whether phone numbers include the + sign, and whether country codes are consistent.

---

Data Dedup Warehouse and Field Consistency: The Key to Unifying Multi-Task Exports

In batch screening, the same number may appear in different tasks (e.g., first screening Telegram, then WhatsApp). If the two exports have different field formats (e.g., first uses valid, second uses active), deduplication after merging becomes complex.

KK-DATA’s Data Dedup Warehouse ensures that the same number maintains consistent field standards across tasks. When you first export with a certain field name and format, that information is stored in the warehouse. Subsequent tasks containing that number will output according to the initial field structure. This means you only need to carefully design the field template in the first task; all later tasks will automatically align.

---

Screening Source Export Standard Best Practices Checklist

Following these steps ensures each export can be used directly:

• Confirm downstream system’s supported file format: CSV or TXT? Delimiter: comma, tab, or pipe?
• Determine if tgid/wsid export is needed: If only number validity statistics, these two fields can be unchecked.
• Match downstream system field names: Are column field names exactly the same (including case)? If not, manually modify the header after export.
• Preview the file: Use the console’s file preview function before exporting to check column order and format.
• Activate Data Dedup Warehouse: Enable dedup in KK-DATA personal settings, and ensure the first task’s fields are aligned.
• First test: Export 10 test numbers, import into the downstream system to verify no errors, then run the full task.
• Save export template: Save commonly used combinations as templates in the console for one-click application in subsequent tasks, avoiding repeated configuration.

---

Frequently Asked Questions

Q: What does screening source export standard mean? Why should I care?
A: It refers to the specification of field names, value formats, and lengths when exporting results from a screening platform (e.g., KK-DATA) to ensure they meet the requirements of downstream systems (e.g., CRM field library, API integration). Caring about it avoids manual mapping and conversion every time you receive screening results, reducing cleaning work by over 80%.

Q: Can I customize the export fields? For example, only export tgid and activity?
A: Yes. When creating a task in the KK-DATA console, you can check the fields you need (including tgid, wsid, gender, activity, etc.) in the “Export Field Options.” Unchecked fields will not appear in the CSV/TXT file, significantly reducing the burden of field mapping later.

Q: After exporting tgid and wsid, can they be directly used for Telegram broadcast and WhatsApp marketing?
A: tgid and wsid are typically used for private message SDK or API calls, not as “phone numbers” for sending. You need to import the exported tgid/wsid into a sending tool that supports these IDs (e.g., TG bot, WhatsApp Business API script). Screening itself does not handle sending.

Q: What is the difference between 007data and KK-DATA in terms of export field standardization?
A: 007data also provides similar CSV export, but field naming may differ between platforms (e.g., “gender” written as “gender” vs “sex”). KK-DATA has built-in field descriptions, mapping suggestions, and a data dedup warehouse in the console, ensuring consistent field naming across tasks and reducing cleaning costs. For specific pricing, please refer to the official website.

Q: My CRM only accepts “1/0” for user status, but the screening exports “active/inactive”. What should I do?
A: This is a common compatibility issue. It is recommended to use the field mapping function (if available) in the screening task export page, or convert text to integers using formulas/scripts after export. The conventional approach is to modify the CSV header and add a conversion column. If you can pre-select the boolean output format (some platforms support customization), set it to 0/1 in advance.

---

This article was written with reference to the KK-DATA official documentation and the latest version of the console. For real-time pricing and export effects, please log in to the application console or contact customer service @kkdata_cc.