KK-DATA avatar KK-DATA

Full analysis of the export fields of the screening system: how to efficiently connect CRM and marketing contact tools

Sieve number system Export kkdata CRM Data deduplication

Full analysis of the export fields of the screening system: how to efficiently connect CRM and marketing contact tools

In the scenario of acquiring customers overseas, the core value of the screening system is to quickly verify the validity, activity, gender and other key dimensions of the phone number, allowing the marketing team to only reach the “real and available” numbers, avoiding the waste of resources and the risk of account suspension caused by blind mass messaging. However, after many teams export the screening results to CSV or Excel, they don’t know how to efficiently import them into CRM (customer relationship management system) or marketing tools, resulting in data being broken between “screening completed” and “actual contact”.

This article will explain in detail how to seamlessly connect the screening results of the Screen Number System to the customer management process from the four dimensions of export field type, format selection, CRM field mapping, data deduplication and cost control, to achieve a closed loop from “number screening” to “marketing reach”. Taking KK-DATA as an example, we introduce its supported cross-platform filters (Telegram, WhatsApp, Line, Zalo, etc.), multi-format export (CSV, TXT, Excel) and cross-task deduplication functions to help you maximize the ROI of each inspection expense.


What is the screening system and why should it be connected to CRM?

The core value of Screen Number System is not “generating numbers”, but “verifying numbers”: determining whether a batch of mobile phone numbers have been registered on designated social platforms (such as Telegram, WhatsApp), whether they are active, what their gender is, and even exporting unique platform IDs (tgid/wsid/uid). This information directly determines the accuracy of subsequent marketing strategies.

  • The first function of docking with CRM: Let the filtered data automatically flow into the customer management database. For example, if you label a number that is “Telegram activated and active in the last 7 days, male, about 30 years old”, it can be directly used for targeted private messages after being imported into CRM.
  • The second function of docking with CRM: deduplication. If a certain number has been contacted before, if duplicates are not removed when screening the number again, not only will the detection quota be wasted, but the user may also be reported for repeated contact.
  • The third function of docking with CRM: tracking conversions. By associating the “activity” and “reachability” in the filter results with the “final transaction” in the CRM, the initial filtering conditions can be continuously optimized.

To summarize in one sentence: a screening system without a CRM can only produce “one-time data”; with a CRM, a continuous iteration of “screening → contact → feedback → re-screening” can be formed.

Tips

If you plan to use the screening system to generate data and connect it to CRM, it is recommended to first clarify which fields need to be filled in in CRM. For example, if there are only four fields in the product: “mobile phone number, channel, recent interaction time, and tags”, then the “number”, “platform type”, “active status” and “gender” exported by the screening system can directly correspond to them. If there are too many CRM fields, it will increase the mapping workload.


What field types does the filter number system support exporting?

Taking KK-DATA as an example, it supports simultaneous screening of multiple platforms in a single task. The exported fields vary depending on the platform and detection type, but they can be roughly summarized into the following three categories.

Basic verification fields: activated/valid/active

  • Activation: Whether the number is registered on the platform (such as Telegram registration detection). It is suitable for “filtering before entering the door” to remove non-registered numbers first.
  • Valid: Based on activation, verify whether the number can receive messages normally (some platforms such as WhatsApp need to detect “valid” to successfully send messages).
  • Activity: Whether the number has logged in or interacted within the specified time window (such as the last 7 days, 30 days). It is suitable for “precise contact” and only sends private messages or invitations to active users to reduce the risk of complaints.

Usage Scenario:

  • Use “Activate” filtering before mass sending to filter out invalid numbers and save sending costs.
  • When using private message marketing, use the “active” label to target recently online users to increase the open rate.

Social targeting fields: gender and age tags

  • Gender: Telegram, WhatsApp, Line and other platforms all support gender recognition and can output “male”, “female”, “unknown”, etc.
  • Age: The gender detection results of some platforms (such as Telegram) will include the Age field, which can be used to interpret/screen people around 30 years old. Note: This data is not ID card-level accuracy, but an approximate value inferred based on multi-dimensional information such as user profile, nickname, avatar, etc.

Usage Scenario:

  • Promote male-oriented products (such as tools and games) to male users.
  • Combine age fields for stratification: for example, filter users “28-35 years old, active on Telegram” for financial management marketing.

Cross-platform and device fields: tgid/uid/device type

  • tgid: Telegram’s internal unique user identification, which can be used for cross-platform deduplication (for example, binding the same tgid number to CRM to avoid duplication of appropriation strategies).
  • wsid: WhatsApp business ID, used for accurate matching when connecting to WhatsApp Business API.
  • uid: User ID for platforms such as Line and Zalo, suitable for establishing unique indexes in CRM.
  • Device type: iMessage detection will return iOS device information (such as iPhone model), and RCS detection will return whether the Android device supports RCS rich media messages.

The value of these identifiers is: when you screen accounts on multiple platforms, the same mobile phone number may have Telegram and WhatsApp activated at the same time. Through tgid or wsid, it can be merged into “same user multiple channels” records in CRM to achieve a more complete user portrait.


How to import the exported data of the screening system into CRM?

Export format selection (CSV/TXT/Excel)

Export formatApplicable scenariosAdvantagesDisadvantages
CSVBatch import into CRM (such as HubSpot, Salesforce, self-built systems)Highly versatile, supported by almost all CRMs; fields can be customized with separators; the file is smallPay attention to encoding (UTF-8 recommended), otherwise Chinese characters will be garbled
ExcelManual viewing, filtering, preprocessing (such as pivot table analysis)Can be processed directly with formulas; data viewing is friendlyThe file is large; some CRMs do not support direct import into Excel and need to be saved as CSV first
TXTDeveloper docking, API batch calling, simple number listMinimalist format, easy to process with scripts; suitable for simple import of one number per lineMissing field structure (such as only numbers but no platform type)

Practical Suggestion: If your CRM supports CSV batch import, CSV is preferred. If the team needs to manually review the data first (for example, sorting by activity and manually eliminating certain numbers), they can first open the CSV preprocessing in Excel, and then save it as a CSV and import it into CRM.

Practical suggestions for CRM field mapping

The exported CSV file typically contains the following columns: 号码, 平台, 开通状态, 活跃状态, 性别, 年龄段, tgid/uid, 最近活跃时间, etc. CRMs usually have fields such as 手机号, 渠道, 最近互动时间, 标签, 用户ID, etc.

Mapping method:

  1. On the screen number system console, first preview the exported field names (for example, the KK-DATA console will display tg_active, wa_active, etc.).
  2. Open Excel or Google Sheets, import the CSV, and use formulas such as =IF(A2="tg_active","Telegram",IF(...)) to convert the field value into a label that CRM can recognize (such as “Telegram_7-day active”).
  3. If CRM supports custom fields, you can directly use the field name of the filter number system as the CRM field name. For example, create a new “TG active status” field in CRM and directly correspond to the tg_active column when mapping.
  4. Note: It is recommended that data from multiple platforms be stored in separate columns instead of mixed in a column of “Platform”, otherwise CRM cannot filter by platform.

Screen number system data deduplication function: avoid repeated access and waste of quota

KK-DATA provides Cross-task number deduplication warehouse: No matter how many times the same number is submitted, the fee will only be deducted for the first detection, and subsequent submissions will be automatically skipped (or only a very low deduplication query fee will be charged). This feature is crucial for CRM integration:

  • Avoid duplicate detection: Suppose you wholesale 100,000 numbers and submit the number screening task in three times. If you do not need to remove duplicates, 30,000 numbers may be duplicated in the second submission, and fees will be deducted in vain. After deduplication is enabled, only the fees for the 70,000 new items will be deducted.
  • Avoid repeated contacts: When importing CRM, “mobile phone number” is usually used as the only key. If a number has been imported before, the number screening system will not export the number again after deduplication, and there will be no duplicate records in the CRM, thereby reducing user resentment and the risk of account suspension.

Notice

Data in the deduplication warehouse will be retained continuously. If you need to re-detect a number (for example, update the activity status), you need to manually remove the deduplication record in the console before submitting a new task. For details, please refer to KK-DATA usage documentation.


Cost control strategy of screening system (pay-as-you-go billing)

KK-DATA adopts the No subscription package, per-item deduction model. After recharging USDT (TRC20), the corresponding fee will be deducted from the balance when each task is completed. This means you only pay for the numbers you actually detect, with no monthly or annual fees.

Cost Control Tips:

  1. Select the minimum detection type: If you only want to verify whether the number has activated Telegram, only detect the “activation” type. Do not check “Active” or “Gender” because the latter has a higher unit price (see the real-time price of the console for specific unit prices).
  2. Use deduplication: As mentioned before, deduplication in the warehouse can avoid repeated deductions. It is recommended that all new numbers go through the duplicate warehouse before submitting the task.
  3. Submit in batches: If the number is large (for example, 500,000), you can split it into several small tasks and run some of them first, and then decide whether to continue after evaluating the cost.
  4. Export field selection on demand: When exporting, only check the fields you really need (such as export number + platform + active status), which reduces unnecessary field processing workload and avoids too many irrelevant columns in CRM.

What kind of screening system is suitable for CRM?

Taken together, a screening system that can seamlessly connect to CRM should meet the following standards:

  • Export field richness: Covers at least the dimensions of activation, validity, activity, gender, age, platform ID, etc.; supports simultaneous screening of multiple platforms (Telegram, WhatsApp, Line, Zalo, iMessage, RCS, etc.).
  • Format Compatibility: Supports CSV, Excel, and TXT export, and the exported file field names are clear and consistent (such as naming with English lowercase underscores).
  • Data Quality: Built-in cross-task deduplication function; activity labels have clear time window descriptions (such as “behavior in the last 7 days”).
  • Billing Transparency: Fees are deducted on a per-item basis, with no hidden fees; estimated fees are displayed before submitting tasks.
  • Technical ease of use: No need to write code, filtering and exporting can be completed through the console; at the same time, a REST API is provided for developers to directly connect to CRM (KK-DATA can consult customer service to obtain API documentation).

KK-DATA is a product designed based on these standards: it supports 10+ platform filter numbers, and fields include tg_active, wa_gender, line_uid, etc.; the export format is optional CSV or TXT; it is equipped with a cross-task deduplication warehouse; billed by item and virtual currency recharge. If you are looking for a screening system that can directly connect to CRM, you may wish to go to the official website to learn more, or directly use the Application Console to start the experience.


FAQ

**Q: Can the CSV file exported by the screening system be directly imported into CRM? **

Answer: Yes. Most CRMs (e.g. HubSpot, Salesforce, Zoho) support CSV bulk import. When exporting, it is recommended to select UTF-8 encoding and confirm that the delimiter is consistent with CRM requirements (usually comma or semicolon). If the CRM field names are different from the column names exported by the filter system, you can rename the column names in Excel before importing.

**Q: What exactly does “activity” in the screening system refer to? **

Answer: Activity refers to whether the number has logged in or interacted within the specified time window (such as the last 7 days, 30 days). Different platforms may have slightly different definitions. For example, Telegram activity detection will refer to the last online time, while WhatsApp activity detection is based on online status. For details, please view the console field description of the screen number platform.

**Q: What should I do if my CRM fields are inconsistent with the Excel column names exported by the screening system? **

Answer: It is recommended to use Excel or data cleaning tools (such as Python Pandas, QUERY function of Google Sheets) to rename or split fields before importing. For example, rename tg_active to “TG Active Status”. If the CRM supports a custom field mapping table, you can also directly establish a mapping rule of “source field → target field” to complete it in one step.

**Q: Can the screen number system export multi-platform data? How to prevent the same number from appearing repeatedly on different platforms? **

Answer: Yes. KK-DATA supports selecting multiple platforms such as Telegram, WhatsApp, Line, Zalo, etc. in one task at the same time. The export results will be displayed as one number per row and different platform status columns. The best way to avoid duplication is to use the cross-task deduplication warehouse of the screening number system (the same number will only be deducted once), or create a unique index based on the “mobile phone number” field in the CRM and automatically deduplicate it when importing.

**Q: Can the numbers filtered using the screening system be used directly for mass messaging? **

Answer: It is recommended to first confirm that the account owner has authorized it or that your marketing activities comply with local laws and regulations (such as GDPR, CCPA). The number screening system only outputs “whether the number is activated/active” and does not involve the user’s consent status. For private messaging platforms (such as Telegram and WhatsApp), you must comply with the anti-spam policy of the platform before sending in groups. For example, Telegram limits the number of people that can actively join groups per day. The “active” label in the filter results can help you reach active users first and reduce the risk of being marked as spam.


If you are looking for a screen number system that can efficiently export rich fields, support multi-platform screen numbers, and have cross-task deduplication capabilities, please visit the following resources:

Only by truly using the screen number data can every test be of value.

Related Articles

Full analysis of the filter number service export format: How KK-DATA connects the results to your CRM

How to efficiently export data after batch screening and import it into CRM? This article explains in detail the CSV/TXT and other multi-format export standards of the KK-DATA screening service, compares the field differences on different platforms (Telegram, WhatsApp, Line, etc.), and provides practical suggestions for cleaning and CRM docking to help you improve customer acquisition and conversion efficiency.

The marketing studio uses the screening system to efficiently deliver customer lists: a set of reusable SOP processes

Overseas marketing studios often face pain points such as invalid numbers, repeated screening, and slow delivery. This article takes a real business scenario as an example to explain in detail how to use the screening system to formulate standardized SOPs from number generation, cross-platform detection to data deduplication and delivery, helping studios save costs and improve list quality. Suitable for team reference in customer acquisition scenarios such as Telegram/WhatsApp/Zalo.

How to use the screening number system to create an efficient customer acquisition data pipeline: a complete tutorial from number generation to precise screening

From number generation to multi-platform social screening, to data deduplication and export, this tutorial explains in detail the core role of the screening system in the customer acquisition data pipeline.手把手教你用KK-DATA搭建「生成→筛选→导出」全流程,支持Telegram、WhatsApp、Line等平台,解决传统手动验证慢、维度少、重复检测等痛点,提升出海获客效率与ROI。