Global number generation to screening: from 0 to building a high-intention US active TG customer acquisition list (full analysis of CSV export specifications)

When you are faced with a cold-start overseas customer acquisition task, the most common problem you encounter is not “where to find the number”, but “can the number you find can be used?” The phone number is empty, the number is out of service, the user has stopped watching Telegram for a long time - these invalid data will directly drag down the marketing ROI. This article will take you through the complete link: from generating a U.S. number pool for free, to screening out the truly valuable US active tg users, and then teaching you step by step to export the data into a standardized CSV/TXT file and directly import it into the downstream CRM or automation system. Active TG in the United States This field is the key entry point for you to build a high-intent customer acquisition list.

What is US Active TG? Why is it a key conversion pool for overseas customers?

“Activity” is the most valuable indicator in Telegram marketing scenarios. If a number is only registered but has not been logged in for a long time, the other party will not see it at all if you send a private message or join a group (tg adds followers). On the contrary, US TG active number means that the user has recently performed online activities on Telegram - logging in, sending and receiving messages, and browsing channels - so that your contact behavior is likely to be noticed.

For independent website promotion, cross-border e-commerce community operations, and CPA/CPS affiliate marketing, filtering US Telegram active data can significantly improve the response rate and conversion efficiency. Ordinary registration data may be 99% sunk costs, while active data is the 1% golden lead pool.

Where does the number come from? How the global number generation module quickly builds the original US number pool

The design idea of KK-DATA is “generate for free first, and then filter by items”. You don’t need to spend money on data in the first place. The process is very simple: log in to the Application Console, enter the “Global Number Generation” module, select the country/region - the United States, set the number segment or generate it randomly, and the system will generate batch numbers for free. These numbers have not been filtered yet, so they are not billed.

After the generation is completed, you can submit the number directly to the “Number Screening” module. Global number generation supports 240+ countries/regions, covering major number segments, and also supports custom CSV import.

Efficient combination of free generation + filtering numbers by bar: no need to pay for invalid numbers

This is the core efficiency logic of the entire product. Generation is free, only actual testing will be deducted per item. In other words, if only 20,000 of the 100,000 U.S. numbers you generate pass the activity test, you only need to pay for those 20,000. There is no charge for unused numbers.

You may think, “I’ll just generate a bunch of them and filter them” - yes, this is also a recommended approach. But the premise is that your filtering granularity must be fine enough. It’s not enough to be “active”, you also need to match age/gender to lock in the real target audience.

Common raw pool source quality comparison table

Source method	Cost	Mobile phone number compliance	Number validity	Activity level	Crowd portrait accuracy	Recommended usage scenarios
Random number segment generation (free)	0	Comply with number segment rules	General (some empty numbers)	Uncontrollable	None	Cold start data pool, test
Collection of landing pages	High (advertising fee)	Users actively submit, good compliance	Very high (real-time mobile phone number)	High	High (including name/email filled in by the user)	High intention customer remarketing
Historical customer data	Medium and low (organization cost)	Depends on the acquisition method	Medium (may have been down)	Uncertain	Medium (needs cleaning + completion)	Recommendations for reuse and repurchase by old customers

KK-DATA’s global number generation module is suitable for downstream supplementation of the first two scenarios.

How to filter US active tg data through KK-DATA - task creation and result export process

The three-step process is clear and repeatable.

Step 1: Choose the appropriate detection combination

Select “Telegram Filter Number” in the console, and then check the following detection types:

• tg activation: Go through basic verification first and filter out unregistered numbers.
• tg active: Specify the active window (such as the last 30 days), this part is your US active tg candidate pool
• tg gender (including age field): further filter gender + age. For example, if you only want American active users who are male and aged between 25 and 35, you can perform secondary filtering based on the returned gender and age fields. Note: The “about 30 years old” mentioned here is a statistical inference based on social network behavioral data. It is not accurate to the ID card level and is completely sufficient for marketing crowd delineation.

You can obtain multi-dimensional results in one task to avoid wasting balance through multiple screenings.

Step 2: Data preview and field selection before export

After the task is completed, click “Export”. The system supports CSV and TXT formats. Before exporting, you can check the required fields. Common fields are:

• phone (number, carrying country code)
• tgid (Telegram internal ID, can be used for subsequent contacts)
• status_active (active or not)
• gender (Gender)
• age (age)
• login_date (Last login time)

It is recommended to leave unnecessary fields unchecked to keep downstream imports simple.

Step 3: Data Deduplication Warehouse – Automatically remove duplicates to avoid repeated deductions

If your number pool contains duplicate numbers from previous tasks, after turning on the “Data Deduplication Warehouse” function, the system will automatically skip these numbers and no new detection fees will be incurred. This can save a lot of costs for teams that screen US TG active numbers in batches and batches.

Detailed explanation of US active tg export specifications: CSV/TXT column names, encoding, delimiters and downstream import recommendations

This is the core part of this article. Many overseas teams are stuck at the level of “the data is obtained, but it is garbled when imported into the CRM”. Knowing the specifications clearly can save a lot of troubleshooting time.

Default column definitions and examples

The first line of the export file is the field name. Taking a U.S. active TG screening as an example, the listing may be: phone, tgid, status_active, gender, age, login_date.

An example of a real row (hypothetical data):

phone,tgid,status_active,gender,age,login_date
+12025551234,123456789,1,male,32,2025-03-15

• Encoding: UTF-8-BOM. The BOM prefix is ​​to solve the garbled problem when Excel opens UTF-8 files. If you use Linux/Mac tools or build your own CRM downstream, BOM usually does not affect it. However, if you use a GBK-encoded ERP system, you need to first use Notepad++ to convert it to UTF-8 without BOM or directly convert it to GBK.
• Delimiter: CSV default comma. If you need to import into a system that requires tab characters (TAB) after exporting, you can select TXT (tab-delimited) during the export process. It is recommended to confirm the format required by the downstream before submitting the task.
• Line break: Unix/LF (standard), suitable for most new versions of Linux/Windows applications.
• Mobile phone number format: Always carry the country code, no spaces, no brackets, no plus sign? ——all have a plus sign (+). If the system you want to import requires 11 pure digits, please do preprocessing downstream.

List of available export fields (subject to the actual display on the console)

• phone: Mobile phone number with country code
• tgid: Telegram user ID
• status_active: 0/1 means inactive/active
• gender：male/female/unknown
• age: Estimated age (integer)
• country_code: Country code
• login_days: Number of days since last login
• language: Interface language
• has_profile_photo: With or without avatar

Downstream import compatibility verification suggestions

1. Small sample test: Export the first 5 items and manually import them into the target system to confirm that the field mapping is correct.
2. Field deduplication: If the downstream system uses phone or tgid as the primary key, please perform deduplication in Excel or SQL before importing to avoid conflicts.
3. Date format: login_date The format is generally YYYY-MM-DD, which is compatible with the ISO standard.

How can the downstream effectively utilize this batch of US active TG data? ——Introduce CRM, community invitations, and private message automated suggestions

Once you get the tools, the data itself won’t automatically bring customers. You need a landing strategy.

• Import CRM: HubSpot, Salesforce or self-built system. Use phone as the unique identifier and use it with tgid to reach Telegram later. It is not recommended to only rely on mobile phone numbers to send text messages - the cost is high and the reach rate is low.
• Community Invitation: Use tgid to automatically invite users to your channel/group through Telegram Bot or third-party tools (such as combot). Be sure to set a rate limit and do not exceed 2,000 messages per day to avoid triggering Telegram risk control.
• Private message automation: Combined with the two-way customer service robot [https://t.me/kkdata_robot](https://t.me/kkdata_robot) to achieve hierarchical contact. Test it first with a welcome message. Active users will be more patient with you.
• Compliance Reminder: Do not bombard or post sensitive content. Telegram takes spam very seriously.

Common misunderstandings and pitfall avoidance guidelines for filtering active TG data in the United States

1. Thinking that “activated” = “active”: This is the biggest misunderstanding. Many numbers have never been online after registration. When you send a message, you are talking to the air.
2. Ignore age field interpretation bias: age is an inferred value, not an accurate data. It can be used for crowd stratification, but do not use it for age verification.
3. Exit due to insufficient balance: Before submitting the task, confirm that the balance is sufficient to pay the estimated fee. Insufficient balance will cause the task to fail to be submitted.
4. No duplication is removed, and repeated testing is a waste of money: Enable the deduplication warehouse function, and the money saved can be used to screen a batch of new numbers.
5. Import garbled code problem: Most of the problems lie in encoding. Remember: UTF-8-BOM is exported, and the rest of the system will do the transcoding by itself.

FAQ

Q: What encoding is used for exported CSV files? Why is my Excel garbled when I open it?

Answer: UTF-8-BOM encoding. If the downstream import uses GBK, it is recommended to use Notepad++ or Sublime to transcode first, or specify UTF-8 when importing into the downstream CRM. Bing/Google search “CSV UTF-8 vs GBK transcoding” to learn more.

Question: What is the order and field names of the columns in CSV? Can it be used directly for mass mailing?

Answer: Field examples (subject to actual export): phone, tgid, status_active, gender, age, login_date. It is recommended to preview before exporting. “Directly used for mass mailing” depends on whether the other party supports mobile phone number as a unique identifier, and usually needs to be converted into tgid for Telegram reach; if you need “email + mobile phone number” dual reach, you can keep phone + email (if there is an email column in your original number pool).

Question: How to distinguish between “tg active users” and “tg registered users”? Which one is better for one-to-one private messaging?

Answer: tg activated only verifies whether the number is registered with Telegram; tg active detects whether there is login/online behavior within the specified time window (such as the last 30 days). It is recommended to choose active users for private messages; registered users are acceptable for community recruitment. Pairing the gender + age fields can further increase intent.

Question: What should I do if the exported files are less than 5,000? Can these numbers be reused?

Answer: Yes. The filtered numbers are all valid and active and can be used directly for contact. If the number is small, it means that the quality of the original pool is low, and more accurate number segments can be regenerated and then screened. The numbers that have been detected will automatically enter the deduplication warehouse, and the same number will not be deducted again next time, but only if you turn on this function.

Question: I need to filter out female users who are “active TG in the United States” and are about 30 years old. How do I do this?

Answer: When creating a screening task, check “tg activated + tg active + tg gender (including age)”. After the task is completed, preview the data before exporting, exclude gender according to gender=male, and filter the 25~35 range according to the age field. The console currently does not directly enable age filtering in the task filtering conditions, but it can be easily processed with Excel or SQL after exporting.

---

Now you have mastered the whole link process: from free generation of US number pool, to filtering out high-quality US active TG data, to standardized export and direct import into downstream systems. All that’s left is to give it a try.

👉 Log in to the console to start screening numbers If you have any questions or need customer service to assist in setting up tasks, please contact customer service in both directions https://t.me/kkdata_robot For complete field formats and billing details, see Usage Document and Official Website Billing Page.