Full analysis of the filter number service export format: How KK-DATA connects the results to your CRM
关于作者
KK-DATA 获客数据筛号平台官方内容团队。
Full analysis of the filter number service export format: How KK-DATA connects the results to your CRM
After filtering numbers in batches, how to efficiently export the data and import it into CRM? This is a key step for many overseas teams to use the screening service. If your team is running a Telegram community, WhatsApp marketing or Line private message promotion, then whether the exported fields are complete and the format is universal directly determines the subsequent conversion efficiency. This article will analyze the export format standard of KK-DATA in detail, compare the field differences of different platforms (Telegram, WhatsApp, Line, etc.), and give practical suggestions for cleaning and docking with CRM to help you go from screening to marketing in one go.
What is the export format of the filter number service? What file types does KK-DATA support?
Export format refers to the file encoding and structure provided by the platform to the user after the screening task is completed. KK-DATA supports two formats by default:
| Format | Features | Applicable scenarios |
|---|---|---|
| CSV (comma separated values) | Structured, clear column names, can be directly read by Excel and database | Import into CRM, data warehouse or perform secondary analysis |
| TXT (plain text) | One number per line, compact file, no delimiters | Quickly view the number list, script batch import into the basic system |
Free combination of fields
Before submitting the screening task, you can check the fields that need to be exported in the console. Unchecked fields will not appear in the final file, thus controlling the file size and privacy leakage risk.
Both formats use UTF-8 encoding and are compatible with most modern CRMs (such as HubSpot, Salesforce, Zoho) and self-developed systems. If your old domestic system has garbled characters, you can use a text editor to save it as ANSI/GBK and then import it.
What are the differences in the fields exported from multi-platform filter results?
Different social platforms (Telegram, WhatsApp, Line, Zalo, iMessage, etc.) have different detectable indicators, so the export fields also have different focuses. Understanding these differences can help you plan data mapping in advance and avoid manual leaks later.
Detailed explanation of Telegram filter number export field
Telegram is one of the most commonly used channels for overseas private messaging. KK-DATA’s detection of Telegram covers the following typical fields:
- tg activation (registration test): whether the number is registered with Telegram
- tg active (customizable active window, such as 7 days / 30 days): whether there is any operation within the specified time
- Gender: User’s gender estimated from public data (male/female/unknown)
- Age group: about 30 years old, about 25-35 years old, etc., estimated based on public data, non-ID card level accuracy
- tgid: Telegram’s unique user ID, which can be used for directed private messages or robots.
The activity window can be specified when submitting a task, such as “active in the past 30 days” or “active in the past 7 days”, and the export results will reflect the active status under this condition.
Comparison of export fields such as WhatsApp / Line / Zalo
| Platform | Typical export fields | Differentiating features |
|---|---|---|
| Open, active, gender (some include avatar) | Gender detection can be used for group push (such as female users recommending beauty products) | |
| Line | Activation, gender, uid | uid can be directly connected to Line@ group sending, suitable for Japan, Taiwan, and Southeast Asian markets |
| Zalo | Activation, activity, gender | For the Vietnamese market, the activity field can significantly increase the arrival rate of private messages |
| iMessage / iOS | iOS device detection, iMessage validity | Suitable for precise reach of Apple users |
| RCS / Facebook / Instagram | Open, active, some include avatars | The number of fields is related to the environment, see the console export template for details |
The exported fields are subject to the console
The specific export fields of each platform may be adjusted with versions or regions. It is recommended to preview the export template in the console before submitting the task. For details, see KK-DATA export documentation.
How to clean the data exported by the screening service and import it into CRM?
Importing screen size results directly into a CRM often requires several cleaning steps. The following takes the most common CSV file as an example to illustrate the standard process:
- Number deduplication: KK-DATA provides data deduplication warehouse, which can compare numbers across tasks and avoid repeated detection and deductions and repeated import into CRM.
- Field mapping: Map the exported column names (such as
phone,tg_active,gender) to fields in the CRM (such as “Mobile phone number”, “Verified”, “Gender”). It is recommended to preset mapping rules in CRM. - Encoding conversion: If CRM only supports GBK, please save the CSV as GBK encoding (notepad++ or
iconvcommand available). - Split big data files: The maximum number of single tasks is about 1 million, and direct import may time out. It is recommended to split a file every 50,000 items and import them in batches.
Be sure to check field mapping before importing
Duplicate numbers in CRM may result in import failure or duplicate customer creation. It is recommended to use KK-DATA’s data deduplication warehouse first, and then export the cleaned data.
Practical Example (Self-developed system docking):
- Export CSV: columns named
phone, tg_active, gender-Write a Python script to read line by line, mark the number intg_active = 1as “verified”, and then write to the CRM customer’scustom_field.
What is the best practice for exporting results from the screening service to be directly used in marketing activities?
Export fields from different platforms have different marketing values. The following are the preferred usages summarized based on practical experience:
- Telegram (including tgid): Send private messages directly to tgid through bots, the conversion rate is 2-3 times higher than group text messages. It is recommended to screen users whose “tg active” is 1 at the same time to avoid disturbing inactive people.
- WhatsApp (Gender + Active): Grouped by gender, female users recommend FMCG/beauty, while male users recommend 3C/tools. Numbers with high activity have higher response rates.
- Line(uid): Use Line@ official API to push messages in batches to uid, suitable for middle-aged and elderly users in Japan and Taiwan.
- Zalo (Active + Gender): The first choice in the Vietnamese market, import active users into Zalo OA and then send keyword private messages.
- iMessage/iOS: The valid iMessage number of Apple users can be directly used for blue text rich media push, please pay attention to the privacy policy.
Core Principle: Prioritize the use of “activity” and “gender” field combinations, which can significantly increase the open rate and conversion rate.
How to handle large amounts of data after exporting? Things to note when handling millions of numbers in a single task
The maximum number of KK-DATA tasks in a single task is about 1 million, and the size of the exported CSV file may range from tens to hundreds of MB. The processing suggestions are as follows:
- Segmented export: If the number exceeds 1 million, multiple subtasks can be split and exported separately, and then the data deduplication warehouse can be used to merge and deduplicate.
- Avoid opening Excel directly: Excel supports up to 1,048,576 rows, and data will be lost if it exceeds. It is recommended to use VSCode + CSV plug-in or command line tool
csvkitto view. - Programming: Use Python (
pandas) orawkcommands to filter by conditions and then import into CRM, which can greatly reduce system pressure. - Import CRM in batches: Every 20,000 items are considered a batch to avoid CRM API timeout.
What should I do if my CRM does not support CSV? Other docking solutions
While CSV is a universal format, some homegrown systems or legacy CRMs may only accept specific formats. Here are the alternatives:
- Use middleware: Such as Zapier and Make (formerly Integromat) support receiving CSV and converting it into API requests. Triggers can be set to automatically sync the CSV when it is uploaded to Google Sheets.
- Script parsing after exporting TXT: KK-DATA supports TXT format (one number per line), write a simple Shell or Python script to read line by line, and write directly through the REST API of CRM.
- Convert to JSON format: Use tools (such as
csvtojson) to convert CSV to JSON, and then batch POST to CRM through back-end scripts. - Manual temporary solution: If the amount of data is very small (hundreds of items), you can open the CSV and copy and paste it into the CRM import interface (some CRMs support pasting text).
Best Practice: If you have the development resources, always use CSV format as the data source and use scripts to do intermediate conversions to avoid manual errors.
FAQ
**Q: Are the column names of the CSV file exported by the screening service in English or Chinese? **
Answer: By default, the column names are exported in English (such as phone, tg_active, gender, etc.) to facilitate docking with international systems. You can also preview the field names in the console, or refer to Official Documentation to get the latest list.
**Q: Can I export only some fields (for example, only export number and active status)? ** Answer: Yes. Before submitting the screening task, the console allows you to check the fields that need to be exported. Unchecked fields will not appear in the final file, thereby reducing the file size and protecting data privacy.
**Q: Is the age field in the exported data accurate? Can it be directly used for precision marketing? ** Answer: The age field is estimated from public data, non-ID card level accuracy, and can assist in analyzing crowd trends (such as about 30 years old). It is recommended to make a comprehensive judgment based on gender, activity and other dimensions to avoid over-reliance on a single field.
**Q: What character encoding is used for exported files? What should I do if the domestic CRM is garbled? ** Answer: The default export is UTF-8 encoding, compatible with most modern CRMs. If the old domestic system has garbled characters, you can use Notepad or a text editor to save it as ANSI/GBK and then import it.
**Q: How to handle exporting more than 1 million numbers in a single task? ** Answer: Currently, the maximum number of single tasks is about 1 million. If you need to process a larger amount of data, it is recommended to split it into multiple subtasks and export them separately, and then merge them through the KK-DATA data deduplication warehouse to avoid wasting balances through repeated detection.
Experience the screening service immediately and turn data into effective reach
From this article, you should already know: reasonable export format and field mapping can maximize the value of batch number data. KK-DATA – Let every screen number bring you convertible customer resources.
👉Log in to the console to start screening numbers Two-way contact customer service https://t.me/kkdata_robot for technical support Official website https://kkdata.cc/ · Documentation https://docs.kkdata.cc/
Related Articles
Complete guide to exporting valid iMessage numbers: Batch verification, filtering and results acquisition methods
Want to obtain valid iMessage numbers in batches for reaching iOS users? This article explains in detail the detection principle, export steps, field interpretation and precautions for valid iMessage numbers. Use the KK-DATA platform to easily complete number screening and data export, improving the efficiency of overseas customer acquisition. Suitable for cross-border e-commerce, application promotion and other scenarios.
Apple ecological customer acquisition guide: How to use the number screening service to accurately detect iOS blue numbers and iMessage valid numbers in batches
In overseas marketing, Apple user groups are of high value but difficult to reach accurately. This article explains in detail how the number screening service detects iOS blue numbers and iMessage valid numbers in batches. From the principle to the operation steps, it helps you efficiently screen valid numbers, reduce marketing costs, and improve ROI. Attached are real-life scenario comparisons and answers to frequently asked questions.
Practical guide to number screening service funnel: three-step operation process from number generation to gender screening
Master the complete process of number screening service funnel: number generation, multi-platform activation detection, activity and gender (including age field) screening. This tutorial takes KK-DATA as an example to explain in detail the installment funnel strategy to help you acquire customers efficiently and reduce costs. Attached are frequently asked questions and checklists, suitable for overseas operation teams.