KK-DATA avatar KK-DATA

Complete Guide to Number Screening Export Field Table: Data Dictionary and Terminology Explanation (KK-DATA Platform)

导出 字段 kkdata 数据字典

Complete Guide to Screen Number Export Field Table: Data Dictionary and Terminology (KK-DATA Platform)

When you download filtering results from the KK-DATA platform, each column in the CSV or TXT file has a specific meaning. Without understanding these fields, you may easily misjudge number quality and waste your marketing budget. This article systematically organizes the Screen Number Export Field Table, covering common fields, status value definitions, and usage scenarios for platforms like Telegram, WhatsApp, iMessage, and RCS, helping you quickly interpret export results like a data operations expert.

Whether you are engaged in overseas customer acquisition, community operations, or private message marketing, mastering this data dictionary will improve subsequent data processing efficiency and avoid decision-making errors caused by terminology confusion.


I. Why Do You Need to Understand Screen Number Export Fields?

Filtering results are not simply a binary “valid/invalid” judgment. A number might be registered on Telegram but inactive for a long time, or registered on WhatsApp but not bound to iMessage. If you directly use unfiltered data for bulk messaging, you may encounter:

  • A large number of message send failures, affecting account reputation
  • Reaching non-target active users, resulting in low conversion rates
  • Inability to accurately differentiate gender-oriented marketing content

The export field table transforms raw detection data into readable, analyzable structured information. Only by understanding the meaning of each field can you perform subsequent operations based on actual status, e.g., importing numbers with “tg effective” into broadcast tools, or using numbers with “tg active 30 days” for high-value event notifications.


II. Quick Overview of Export Fields

KK-DATA’s export data is generally divided into four major field categories. The table below summarizes common field groups:

CategoryField ExamplesDescription
Platform Identificationplatform, country_code, numberNumber’s platform, country code, original number
Status Detectiontelegram_status, whatsapp_status, active_levelPlatform registration/valid/active detection results
User Attributestgid, wsid, gender, last_active_daysUnique user ID, gender prediction, active days
Auxiliary Informationtask_id, detect_time, dedup_key, estimated_costTask traceability, dedup markers, cost estimation

Depending on the detection type, field names and quantities may vary, but the core logic remains consistent. The following sections explain each category in detail.

Field meanings are subject to real-time display in the console

Field names for different detection types may be adjusted with version updates. Please refer to the actual exported data from the application console and the latest instructions in the documentation.

1. Platform Identification Fields

  • number: Original phone number, usually including country code (e.g., +8613800138000).
  • country_code: Country code (e.g., 86), used to filter numbers from specific countries.
  • platform: Detected platform type. Enum values include telegram, whatsapp, imessage, rcs. Note: a single number screening task may target one platform, but this field in the export result uniformly marks the platform.

2. Status Detection Fields

  • telegram_status: Whether registered on Telegram (registered/unregistered).
  • telegram_effective: Whether searchable/contactable (valid/invalid).
  • telegram_active: Activity level (e.g., active 7 days/15 days/30 days).
  • whatsapp_status: Whether registered on WhatsApp (registered/unregistered).
  • imessage_status: Whether iMessage is activated (enabled/disabled).
  • rcs_status: Whether RCS is supported (supported/unsupported).
  • active_level: Comprehensive activity indicator (e.g., high/medium/low).

3. User Attribute Fields and Auxiliary Information

  • tgid: Telegram user unique ID (numeric string), can be used for precise targeting.
  • wsid: WhatsApp user unique identifier (Base64 encoded string).
  • gender or predicted_gender: Gender predicted based on avatar and nickname (male/female/unknown).
  • last_active_days: Days since last activity at the time of detection (e.g., 5 means active 5 days ago).
  • detect_time: Timestamp of detection task completion (UTC).
  • task_id: Task number, used for cross-task data correlation.
  • dedup_key: Record key in the deduplication repository, useful for identifying duplicate numbers.
  • estimated_cost: Estimated cost before task submission (numeric, in yuan).
  • actual_cost: Actual charge after task completion.

III. Detailed Explanation of Platform Identification Fields

Telegram number screening is the most common scenario in overseas marketing, and the export fields are the richest.

  • telegram_status: Values “registered” or “unregistered”. Registered only means the number has been registered on Telegram, but does not guarantee current contactability (e.g., deleted or banned account).
  • telegram_effective: Values “valid” or “invalid”. Valid means the number is currently searchable and can receive messages (not deleted, not restricted for violations). Note: valid does not mean active.
  • telegram_active: Activity level determined by last login time. Common windows: 7 days, 15 days, 30 days. For example, “active_7d” indicates login activity within 7 days. This field appears only when an activity detection task has been submitted.
  • tgid: Telegram user unique numeric ID, can be used to import into TG broadcast tools for precise sending, avoiding failures due to incorrect number format.
  • telegram_gender: Gender inferred from public information such as avatar and nickname. Field name is telegram_gender or unified gender. Values: male, female, unknown.
  • whatsapp_status: Values “valid” or “not detected”. Valid means the number is registered on WhatsApp and can receive messages (not expired, not deleted).
  • wsid: WhatsApp user internal identifier (usually Base64 string). After export, it can be bound with the number for precise push across devices or sessions, avoiding loss due to number changes.

The detection field names for iMessage and RCS are similar, but status values differ slightly.

  • imessage_status: Values “enabled” or “disabled”. Enabled means the Apple ID/number has activated iMessage functionality.
  • rcs_status: Values “supported” or “unsupported”. RCS (Rich Communication Services) is an enhanced SMS protocol provided by operators, already popular in some countries. Additionally, the operator_info field may be included to display the operator name (e.g., T-Mobile, Verizon), helping determine the number’s carrier.

IV. Detailed Explanation of Status Detection Fields

Understanding the differences between “registered”, “valid”, and “active” is key to using the screening tool efficiently.

1. Registration Status vs. Validity Status

FieldMeaningTypical Scenario
telegram_status = registeredNumber is registered on TelegramInitial screening, bulk adding friends
telegram_effective = validCurrently searchable and can receive messagesCold start private messages to verified numbers
whatsapp_status = validCan receive WhatsApp messagesImport into WhatsApp broadcast tools

Note: A number may show as registered but invalid (e.g., account deleted), or valid but long inactive. In marketing, priority should be given to the valid field; if high reach rate is desired, further filter by activity level.

2. Activity Status and Window Settings

Activity detection requires specifying a time window. Common options are 7 days, 15 days, and 30 days. The field last_active_days in the export result gives the exact number of days, while the active_window field (if present) records the window value set in the task.

  • If the window is set to 15 days, only numbers that had login activity within 15 days are marked as “active 15 days”.
  • Numbers active within a 7-day window usually have a higher conversion rate than those within a 30-day window, but the quantity is smaller. Choose according to marketing purpose: use 7-day active for high-conversion campaigns, 30-day active for brand exposure.

3. Gender Identification Status

The accuracy of the gender prediction field gender or predicted_gender depends on the richness of Telegram public information (avatar, nickname). Generally, numbers with clear avatars and typical names can achieve 70%~80% accuracy, but this should not be the sole criterion. It is recommended to combine with activity level and target market characteristics.


V. User Attribute Fields and Auxiliary Information

1. Meaning of TGID and WSID Export

  • TGID (Telegram ID): Each Telegram user has a unique numeric ID. After export, you can use this ID to send messages directly to the user (via Bot API) without relying on phone numbers. This is useful when the number has changed or SMS cannot be sent.
  • WSID (WhatsApp ID): Internal identifier for WhatsApp users. Similarly, it can be used for precise sending. Especially after binding WSID, even if the number changes, the same user can still be located. Exporting both WSID and the number, then importing into broadcast tools, not only improves delivery rate but also reduces failures due to number format errors.

2. Gender Prediction and Active Days

  • Gender field values: male, female, unknown. Note: Some numbers may return unknown due to insufficient information; this should not be considered invalid data.
  • The active days field active_days indicates the number of days since the last login. For example, active_days=3 means the number had login activity 3 days ago. This field is more precise than the window level and can be used for secondary filtering by day intervals.

3. Data Deduplication Repository and Export Markers

If you submit multiple number screening tasks, duplicate numbers are automatically deduplicated to avoid double charges. The dedup_key field in the export result indicates the record identifier in the deduplication repository, while task_id marks the task this record belongs to. You can use these two fields to trace data sources or merge results from multiple tasks in subsequent processing.


VI. Relationship Between Export Fields and Billing

KK-DATA uses a per-record billing model, with different unit prices for different detection types. The exported data usually includes cost-related fields:

  • estimated_cost: Estimated cost displayed before task submission (in yuan). The actual charge may vary slightly due to deduplication.
  • actual_cost: Actual amount deducted after task completion. You can view the detection cost for each number in the exported CSV (some tasks may not record per-number costs and only show totals).

Important: Free number generation (global number generation) does not incur charges; only online number screening tasks are charged per detection record. Before submitting a task, confirm the estimated cost in the console to ensure sufficient balance.

Note the unit price differences among detection types

Detection unit prices for Telegram, WhatsApp, iMessage, etc., differ. Activity detection and simple registration detection may also have different unit prices. Before submitting a task, check the billing documentation or the estimated value displayed in the console to avoid task failure due to insufficient balance.


VII. Common Field Misunderstandings and Precautions

Common pitfalls summarized to help you avoid detours in data analysis:

  1. Valid ≠ Active: A number may be valid (reachable) but not logged in for half a year, making message reception probability very low. Always refer to the activity field.
  2. Gender prediction is for reference only: Avatars and nicknames can be misleading (e.g., cartoon images). For high-value marketing campaigns, combine with other dimensions such as activity level.
  3. TGID and number are not one-to-one: Users may change phone numbers, but tgid remains the same. After exporting tgid, use it as the basis for subsequent operations rather than the number.
  4. Dedup key in deduplication repository cannot be reused across tasks: Each task has its own deduplication logic; dedup_key is not guaranteed unique across different tasks.
  5. Active days are calculated based on platform login records: If a user is online but does not send messages, they may still be recorded as active. This is normal.

Frequently Asked Questions

Q: What is the difference between tg valid and tg active?

A: tg valid detection checks whether the number is registered on Telegram and currently searchable/contactable; tg active detection further checks whether the user has logged in within a specified window (e.g., 7/15/30 days) on top of validity. Activity detection consumes more balance and is suitable for marketing scenarios requiring high reach rates.

Q: How to determine if a number has registered WhatsApp?

A: Check the whatsapp_status field in the export result. Values “registered” or “valid” indicate the number is registered on WhatsApp and can receive messages; if “unregistered” or “not detected”, you need to resubmit the detection task.

Q: What is the use of exporting WSID?

A: WSID is an internal unique identifier for WhatsApp users. It can be used for precise targeted message sending, avoiding the inability to locate the same user after a number change. Importing WSID into broadcast tools can improve message delivery rates and reduce send failures due to number format issues.

Q: How to interpret the last_active_days field in the exported CSV?

A: This field indicates the number of days since the last activity at the time of detection completion. For example, last_active_days=3 means the number had login activity 3 days ago. This data comes from the platform’s last online timestamp, precise to the day. If the field is empty or null, it may mean the number is valid but the exact active days cannot be obtained (e.g., due to privacy settings).

Q: How accurate is the gender field? Is it helpful for marketing?

A: Gender prediction is based on analysis of Telegram’s public avatar and nickname text, with an accuracy of about 70%~80%, varying by region and culture. It can be used as an auxiliary reference but is not recommended as the sole filtering criterion. For marketing requiring precise gender targeting (e.g., women’s products, men’s clothing), it is recommended to first filter high-quality users by activity level, then do final grouping with the gender field.


Next Steps

  • Log in to the application console to view your number screening task export data, and compare it with this article to understand each field.
  • Refer to the complete documentation for more field examples.
  • If you have further questions, contact customer service directly via Telegram @kkdata_robot for assistance.

This article helps you clarify the complete data dictionary and terminology explanation of the screen number export field table. Mastering these concepts will enable you to use filtering results more efficiently and improve your overseas customer acquisition ROI.