Competitive Screening Platform Export Fields Comparison: Full Analysis of tgid, wsid, and CSV Output Formats

In the customer acquisition workflow for Telegram and WhatsApp in overseas marketing, the quality of export fields from screening platforms directly determines whether data can be efficiently reused. Many teams only focus on “detection accuracy” when selecting a platform, neglecting the completeness of export fields and format usability—the “last mile” that transforms raw phone numbers into actionable marketing leads. This article centers on tgid (Telegram ID) and wsid (WhatsApp ID), horizontally comparing major screening platforms (including 007data, thdata, and KK-DATA) in terms of export fields, CSV output formats, and data dimensions, helping operations teams find the best tool for batch lead generation exports.

---

Why Export Fields (tgid / wsid) Are “Hard Metrics” for Screening Platforms

Definition and Uses of tgid and wsid

• tgid: The unique numeric identifier of a Telegram account. With tgid, you can directly use the Bot API to send messages, detect if a user is in a group, or associate user profiles. It is more stable than a phone number (phone numbers may change, tgid does not), making it a core field for private message promotion and blacklist deduplication.
• wsid: The internal assigned ID of a WhatsApp user (similar to a mapping identifier between phone number and Business API). Once wsid is exported, you can build precise broadcasts via WhatsApp Business API, avoiding send failures due to phone number format issues.

If a platform only returns “valid/invalid” labels without providing tgid/wsid, you will have to perform secondary queries in subsequent marketing, increasing cost and time.

Risks of Messy Export Formats

Different platforms’ exported CSV files often face:

• Inconsistent column names (e.g., tg_id vs Telegram_ID vs TG-ID)
• Encoding errors (Chinese characters become garbled)
• Missing fields (only output “valid” and number, no tgid/wsid)
• Improper handling of quote characters (phone numbers truncated to scientific notation by Excel)

These issues force operations teams to manually clean data, severely impacting ROI. Therefore, before selecting a platform, it is a practical best practice to test export with a short task of 10 numbers to verify field completeness and format consistency.

---

Export Format Comparison: CSV vs TXT vs JSON

Format	Typical Platform Support	Column Structure Standardization	Applicable Scenarios
CSV	Most platforms support	Highly variable (different column names, order, null value filling)	Importing into CRM, Excel analysis, script batch processing
TXT	Some platforms only provide TXT	Usually one number per line or fixed delimiters	Quick export of a single field (e.g., only tgid)
JSON	Very few platforms support	Nested fields, complex parsing	API integration, custom processing, not suitable for non-technical users

Column Mapping of Key Fields (tgid, wsid, Gender, Activity Status) in CSV Format

The following is based on actual export performance of mainstream platforms (using Telegram number detection as an example):

Export Field	007data	thdata	KK-DATA
Phone column name	phone	phone_number	phone
tgid column name	telegram_id	tg_id	tgid
wsid column name	Not supported	whatsapp_id	wsid
Activity status column name	active (boolean)	is_active + last_active_days	active_level (7/15/30 days)
Gender column name	Not supported	Not supported	gender (avatar recognition)
Null value filling	Empty string	null	Empty string

From the table, it is clear that the inconsistency in field names increases downstream data processing costs. If your team needs to use data from multiple platforms simultaneously, it is recommended to create a unified field mapping table before importing.

Which Export Format is Better for Downstream Workflows?

• Importing into CRM / Customer Management Tools: CSV is recommended, but ensure column names are fixed, encoding is UTF-8 with BOM (to avoid garbled characters when opened in Excel).
• Integrating with Automation Scripts (e.g., Python batch sending): CSV or JSON are both acceptable; JSON is easier for programmatic parsing, but CSV is more universal.
• Manual Screening / Temporary Viewing: TXT or simple CSV is sufficient; too many fields are not needed.

---

Field Completeness Comparison: Only Output “Valid” or Output “Valid + ID + Activity Level”

Below is a comparison of data dimensions that different platforms can output for the same number (using Telegram detection as an example):

Dimension	007data	thdata	KK-DATA
tgid export	Supported	Supported	Supported
wsid export	Not supported	Supported	Supported
Activity (last online days)	Supported (precise timestamp)	Supported (last active days)	Supported (7/15/30 day preset levels)
Gender recognition	Not supported	Not supported	Supported (avatar recognition)
One-time export of multiple fields	Requires separate tasks (tgid and activity need separate tasks)	Can export all in one task	Can export all in one task

For teams that need to obtain both tgid and activity level, if the platform requires two separate tasks, it not only wastes time but also incurs duplicate charges. KK-DATA supports selecting all detection items in a single task and exporting all fields, reducing operational steps.

---

Export Process Convenience Comparison: How Many Steps to Get a Usable tgid File

Step	007data	thdata	KK-DATA
Upload numbers	Supports CSV/TXT paste	Supports CSV/TXT	Supports CSV/TXT and custom number range generation
Select detection items	Manually check each item	Optional detection combinations	Supports select all or custom
Task completion notification	Email notification	In-platform notification	Telegram bot notification
Download method	Download one by one from console	Download one by one from console	Batch download from console + export records
Need to split after export?	Sometimes (tgid and activity in separate files)	Usually not	No (single file contains all fields)

KK-DATA allows users to choose “fields to export” before export, and after task completion, they can directly receive download links via Telegram, suitable for mobile office scenarios.

---

Impact of Billing Models on Export Strategy

Platform	Billing Method	Export Fee	Suitable for Large Batch Export Strategy
007data	Recharge, pay per record	Some exports may incur secondary charges	Need to plan export times to avoid repeated downloads
thdata	Subscription + per-record surcharge	Free export, but fixed subscription fee	Suitable for high-frequency, small batch export
KK-DATA	No subscription, pay per record, free export	No additional charges	Suitable for exporting anytime, no fixed cost

For teams needing to export hundreds of thousands of tgid/wsid in one go, the pay-as-you-go model without subscription packages is more flexible, avoiding wasted monthly fees. KK-DATA’s export is free of extra charges, meaning you only pay for detection, and data can be downloaded unlimited times.

---

Data Quality Stability: Lifecycle and Update Frequency After tgid/wsid Export

Hidden Benefits of Cross-Task Deduplication for Export

If the platform has a built-in data deduplication warehouse, subsequent tasks will automatically exclude already detected numbers, and the exported file will not contain duplicate records. This directly reduces redundant data and duplicate charges.

• 007data: Not publicly disclosed support for cross-task deduplication.
• thdata: Supports within-task deduplication, but cross-task requires manual filtering.
• KK-DATA: Built-in cross-task number deduplication warehouse; exported files automatically exclude already detected numbers, avoiding duplicate charges.

Determining the “Validity Period” of Exported Fields

tgid and wsid are inherently long-term stable, but associated phone numbers may change (e.g., user changes SIM card). It is recommended to:

• Use data within 7 days after export for best results.
• Combine with activity fields: if the number corresponding to tgid has not been active in the last 30 days, it indicates low user activity and reduced marketing value.

KK-DATA’s activity field provides three granularities: 7/15/30 days. Users can choose to export the corresponding activity level based on promotion timeliness needs.

---

Differences in Export Fields Across Social Platforms (Telegram vs WhatsApp vs iMessage)

Telegram Export Fields: tgid, tg Activity, tg Gender

Field	007data	thdata	KK-DATA
tgid	✔	✔	✔
Activity (days)	✔ (precise timestamp)	✔ (last online days)	✔ (7/15/30 day levels)
Gender	✘	✘	✔ (avatar recognition)

WhatsApp Export Fields: wsid, Carrier Detection

Field	007data	thdata	KK-DATA
wsid	✘	✔	✔
Carrier detection	✘	Partially supported	✔ (inactive/operator/RCS)

Note: iMessage and RCS detection mainly return validity indicators, not tgid/wsid. If the acquisition channel is primarily WhatsApp, be sure to choose a platform that supports wsid export; otherwise, precise sending later will not be possible.

---

How to Choose Based on Export Fields for Different Lead Generation Scenarios

Scenario 1: Private Message Promotion (Telegram Mass Messaging)

Required fields: tgid + activity level (7/15/30 days)
Recommended platform: Prioritize platforms that support tgid export and have granular activity dimensions, such as KK-DATA (also supports gender recognition for further user profile filtering).

Scenario 2: Community Recruitment (WhatsApp Group Invitation)

Required fields: wsid + validity
Note: Some platforms only return “valid” without wsid, making it impossible to send via API; you can only add friends manually. Recommend thdata or KK-DATA that also export wsid.

Scenario 3: User Profile Filtering (Multi-dimensional Combination)

Required fields: tgid + gender + activity + wsid (if cross-platform)
Recommended platform: Only KK-DATA supports exporting all dimensions in one task; others either lack gender or require multiple tasks.

---

Frequently Asked Questions

Q: Why don’t some platforms have a tgid column in the exported CSV?

A: Some platforms only display detection results in the console; the exported CSV only contains numbers and “valid/invalid” labels. If you need tgid, you must explicitly check “Export Telegram ID” in the task parameters, or choose a platform that supports this field output.

Q: Can exported wsid be directly used for WhatsApp group messaging?

A: Yes. wsid is the standard field for identifying users via WhatsApp Business API. After obtaining it, you need to send template messages through the API. Note that it must be used in compliance with user authorization and WhatsApp business policies.

Q: How many numbers can a single task handle when exporting data using KK-DATA?

A: Currently, a single task supports approximately 1 million numbers. The export format is CSV (UTF-8 with BOM), with columns including phone number, tgid, wsid, activity level, gender, and other optional fields, requiring no additional processing.

Q: Do exported numbers expire?

A: tgid and wsid themselves do not expire over time, but user activity status can change. It is recommended to filter numbers that have been active recently using the activity field to ensure marketing effectiveness. KK-DATA attaches activity data during export.

Q: Are there additional charges for export?

A: KK-DATA does not charge for export; charges are only for screening detection counts. Other platforms may have different rules; please check each platform’s billing page. See KK-DATA Billing.

---

Summary: Export fields (tgid/wsid) are core metrics for measuring the practicality of screening platforms. By comparing CSV formats, field completeness, process convenience, and billing models, you can quickly find the tool that best suits your lead generation scenario. Log in to the KK-DATA Console to experience the export function, or refer to the Documentation for detailed steps. For custom requirements, feel free to contact official customer service via Telegram @kkdata_cc.