Full Analysis of thshxt Export Fields: tgid, wsid, and CSV Export vs. KK-DATA Screening Platform

In batch number screening scenarios for Telegram and WhatsApp, users often encounter platforms like “thshxt” (e.g., 007data, thdata). These platforms detect number status and export results as CSV or TXT files. Among the export fields, tgid (Telegram ID) and wsid (WhatsApp ID) are frequently needed for subsequent precise direct messaging or CRM import. However, export fields, dimensions, and billing logic differ significantly between platforms; choosing the wrong solution may result in incomplete data or cost overruns.

This article starts from the actual content of thshxt export fields and compares the tgid/wsid export capabilities of the KK-DATA screening platform, helping you make the best choice.

What Are thshxt Export Fields? tgid and wsid Supported by Mainstream Platforms

thshxt-type platforms typically batch-detect number status via APIs, filtering and exporting device type, platform activation status, activity level, etc. For Telegram and WhatsApp, the two most commonly used export identifiers are:

• tgid (Telegram ID): The unique numeric ID of a Telegram user, used for group invitations, direct messages, and bot message routing. The export format is usually a pure number (e.g., 123456789) and sometimes includes @username.
• wsid (WhatsApp ID): A user identifier in the WhatsApp Business API, generally generated by Base64 encoding the country code and phone number. After exporting wsid, it can be directly used with WhatsApp marketing automation tools for targeted message delivery.

tgid Export: Purpose and Format

In thshxt platforms, tgid export usually appears in “Telegram screening” tasks. Detection results may contain tgid (if the number is a Telegram user) or null (if not registered). Common CSV export columns include:

Column	Description
phone	E.164 format phone number
tgid	Telegram numeric ID (supported by some platforms)
tg_username	@username (optional)
status	Registered / Not registered

In practice, the value of tgid lies in deduplication and precise reach—the same number may appear in multiple groups, but tgid is unique; messages sent via tgid are less likely to be blocked.

wsid Export: WhatsApp Business Identifier and Use Cases

WhatsApp’s wsid export is relatively rare because most thshxt platforms only detect whether a number is registered on WhatsApp, not provide a business-level ID. A complete wsid format resembles 58XXXXXXXXXc2VuZ*, which is a key for identifying users in the WhatsApp Business API. If a platform offers wsid export, it is typically used for:

• Integrating WhatsApp Cloud API
• Connecting third‑party marketing systems (e.g., WATI, ManyChat)
• Avoiding message failures due to incorrect number formatting

In‑Depth Comparison of KK‑DATA’s tgid/wsid Export Capabilities

KK‑DATA (kkdata.cc) is a professional lead data screening platform that offers richer fields and control options for tgid and wsid export compared to thshxt platforms. The following objective comparison covers detection types, field richness, export formats, batch limits, etc.

KK‑DATA’s tgid Export: Supports Registration, Validity, Activity Level, and Gender Recognition

KK‑DATA’s Telegram screening function, in addition to basic registration detection, supports:

• tg effective: Numbers registered on Telegram and recently logged in
• tg active: Configurable activity window (7 days, 15 days, 30 days, etc.) to filter users active within a specific period
• Gender recognition: AI‑based gender identification from profile photos; export includes a gender column
• tgid export: All successfully detected records include tgid, numeric format, ready for subsequent direct messaging tasks

A single task can handle up to 1 million numbers. After completion, download CSV/TXT with one click; results include phone number, tgid, detection status, active time, gender, etc. Compared to thshxt platforms that only return “registered/not registered” plus a tgid, KK‑DATA’s export data is more suitable for fine‑grained operations.

KK‑DATA’s wsid Export: Valid WhatsApp Numbers + Business ID in One Go

KK‑DATA’s WhatsApp screening capability is also outstanding:

• Validity detection: Confirms whether the number is registered on WhatsApp
• wsid export: Check “wsid” in the export fields; the CSV result will include this column
• Additional information: The same task can also export country, timezone, operator, etc. (for certain countries)

This is critical for teams using the WhatsApp Business API for automated marketing—with wsid, you can directly call the API to send template messages without manually constructing phone numbers.

Summary of Field Differences Compared to thshxt Platforms

Dimension	thshxt Platforms (Typical)	KK‑DATA
tgid detection	Only registration	Registration + Valid + Active + Gender
tgid output	Single column (may be missing)	Always included, with status labels
wsid export	Rarely supported	Supported, one‑click export
Additional filtering dimensions	Country, platform status	Activity window, gender, number segment matching
Batch limit	Usually ≤ 100,000 per task	1 million per single task
Export format	CSV / TXT	CSV / TXT (multiple formats)

thshxt Export Fields and CSV Format: Which Data Matters?

No matter which platform you use, the columns you choose for CSV export directly affect post‑processing efficiency. A typical thshxt‑platform CSV export includes:

• phone (phone number)
• country_code
• platform_status (activation status)
• check_time (detection time)
• Some platforms support extra columns like: tgid, gender, last_active

Fields that users often overlook:

• country_code: Used to differentiate international numbers; without it, you have to supplement later when grouping by country.
• Detection timestamp: Keep it to date precision (e.g., 2025-03-21) to trace data timeliness.
• Deduplication mark: thshxt platforms typically do not have built‑in deduplication, whereas KK‑DATA provides a “data deduplication warehouse” that automatically marks duplicate numbers across tasks, avoiding repeated charges.

Migrating from thshxt to KK‑DATA: Three Steps to One‑Click Export tgid and wsid

If you are currently using a thshxt‑style platform and want to migrate to KK‑DATA for more flexible data export, follow these three steps.

Step 1: Number Generation and Import

• In the KK‑DATA dashboard, select “Global Number Generation” to generate random numbers by country or number segment (free).
• Or upload your existing number list (CSV/TXT), and the system will import them into the “Number Warehouse.”
• Deduplication hint: KK‑DATA’s “Data Deduplication Warehouse” detects numbers that have already been screened, preventing duplicate charges.

Step 2: Configure Screening Task and Select tgid/wsid Export

• In the “Telegram Screening” or “WhatsApp Screening” module, upload the numbers to be detected (you can select from the warehouse).
• In the “Export Fields” settings, check “tgid” (Telegram) or “wsid” (WhatsApp).
• For more precise filtering, set activity window (e.g., 15 days) or gender detection.
• The estimated cost will be displayed before submission; confirm to execute.

Step 3: Export Results and Verify Data Quality

• After task completion, you will receive a Telegram notification (if bound).
• In the task details page, click “Export” and choose CSV or TXT format.
• Check field completeness: whether tgid/wsid, status labels, activity level, country, etc. are included.
• If data anomalies (e.g., missing tgid) occur, you can resubmit with adjusted screening conditions (only new detections are charged).

Billing Model Comparison: thshxt vs. KK‑DATA – Which Is Better for Batch Export?

Billing is a key factor in choosing a platform. thshxt‑style platforms usually charge per task or via packages (exact prices depend on each platform’s real‑time rates). For example, 50,000 detections for ¥88/month, 100,000 for ¥168/month, etc. The drawback: if task volumes are uneven, packages may be wasted or insufficient.

KK‑DATA uses a pay‑per‑record, no subscription model:

• Top up balance (USDT anonymous, minimum ~50 USDT)
• Charges are deducted only after each detection is completed (deduplication is free)
• Pay only for what you use; no fixed costs

Scenario	thshxt‑style Platforms	KK‑DATA
Small batch (fewer than 10,000/month)	May have minimum spend or small package	Per‑record charge, precise cost
Medium/large batch (100,000 – 1,000,000/month)	Must buy multiple packages; leftover balance possible	Pay‑as‑you‑go, flexible scaling
Multi‑platform (Telegram+WhatsApp)	Usually billed separately	Unified balance, any combination
Anonymity	Supports Alipay/WeChat (real‑name required)	Supports USDT TRC20 anonymous top‑up

Recommendation: When to Choose KK‑DATA Over thshxt‑style Platforms?

Based on data dimensions, export formats, budget control, anonymity, and multi‑platform support, here is a decision tree:

• If you only need basic activation detection (just checking whether a number is registered on Telegram/WhatsApp), and the volume is low (fewer than 5,000/month), thshxt platforms’ free quotas or small packages may suffice.
• If you need activity level, gender recognition, tgid/wsid export, or involve multiple platforms (e.g., simultaneously checking Telegram, WhatsApp, iMessage, RCS), KK‑DATA’s one‑stop screening experience is superior.
• If you value transparent pricing and anonymous payments (e.g., overseas teams wanting to avoid fund association risks), KK‑DATA’s USDT top‑up + per‑record charge is the best choice.
• If you frequently handle millions of numbers (e.g., outbound business development), KK‑DATA’s 1‑million‑record limit per task and deduplication warehouse can significantly reduce redundant work.

In summary: thshxt‑style platforms suit entry‑level needs, while KK‑DATA targets professional teams that require deep data management, batch export of complex dimensions, and cost control.

Frequently Asked Questions

Q: Is there a difference between tgid in thshxt exports and tgid from KK‑DATA?
A: The field itself is the same—a Telegram user ID. The difference lies in KK‑DATA’s ability to export additional information such as activity level, gender, and registration time alongside tgid, providing a more complete dataset. thshxt platforms typically export only basic status (registered/not registered) and tgid may be missing or inconsistent in format.

Q: Does KK‑DATA support exporting wsid to CSV?
A: Yes. Check “export wsid” in the WhatsApp screening task; the CSV file will include columns for phone number, wsid, country, detection time, etc. wsid can be used for WhatsApp Business API message sending.

Q: Which exports faster, thshxt platforms or KK‑DATA?
A: Speed depends on task size and server load. KK‑DATA’s backend uses multi‑threaded parallel processing, typically completing a 1‑million‑record task within minutes (actual time varies by detection type). thshxt platforms may take longer for similar volumes due to task scheduling limits. Check each platform’s console for real‑time experience.

Q: If I only want to verify whether numbers are registered, do I need to export tgid?
A: Not necessarily. If you only need validity, activation detection and status export are sufficient. For subsequent precise messaging (e.g., group invitations, marketing messages), tgid is essential. KK‑DATA provides flexible checkbox options—select only the fields you need, without extra data volume.

Q: Can I import my existing thshxt data when migrating to KK‑DATA?
A: Yes. KK‑DATA supports importing old number lists via CSV/TXT. The system will automatically deduplicate matching numbers to avoid repeated charges. We recommend reading the documentation to understand field mapping rules and how to configure tgid/wsid export tasks.

---

If you have specific requirements for tgid/wsid export, or wish to migrate from thshxt platforms to a more flexible system, feel free to log in to the application console to experience it, refer to the documentation for detailed field descriptions, or contact support @kkdata_cc for migration guidance.