TG Number Deduplication Guide: Integrate Dedup Repository to Avoid Cross-Task Repeated Charges

When batch-screening TG numbers, duplicate numbers always lead to wasted money? If you frequently need to submit number lists for Telegram activity, gender, or account existence checks, mastering “TG deduplication” is essential. This article explains the hidden funnel of repeated charges from real-world scenarios and provides step-by-step instructions on how to use a dedup repository for automatic cross-task deduplication, significantly reducing testing costs. At the end, we compare the deduplication capabilities of mainstream platforms like 007data and thdata to help you choose the right tool.

Why Deduplication is Necessary Before TG Screening? — The Hidden Funnel of Repeated Charges

Many teams only focus on the unit price per task during TG screening, neglecting the cumulative cost of duplicate numbers. Suppose you maintain a list of 50,000 numbers for your weekly promotion list, and each time you test 30,000 active numbers from it — but 30% of those numbers were already tested the week before. If you don’t proactively deduplicate, those 30% will incur full charges every time. At a rate of XXX yuan per number, you could waste hundreds or even thousands of yuan in a month.

Typical scenarios of repeated charges include:

Scenario 1: Same batch of numbers submitted repeatedly across multiple screening tasks

For example, you are doing TG group growth for projects A and B respectively, and you submit the same (or partially overlapping) expanded number list for both. The system will test all numbers for each task separately, even though many numbers’ status test results are exactly the same.

Scenario 2: Previously tested numbers mistakenly re-submitted

Operators might extract numbers from an old Excel file and upload them without deduplication; or lists from different channels overlap and are merged directly. These duplicate numbers incur charges again, while the test results add no new value.

Comparison with and without deduplication:

• Without deduplication: Submit 50,000 numbers, with only 30,000 actual new additions; 20,000 are duplicates, costing 20,000 × unit price extra.
• With deduplication: The system automatically removes duplicate numbers, only testing the 30,000 new ones, saving about 40% in costs.

The dedup repository is the core feature to solve this problem.

What is a Dedup Repository? How to Achieve Cross-Task Number Deduplication?

A dedup repository is a centralized number storage and comparison system. You can upload previously tested number lists to the repository. Whenever you create a new screening task, the system automatically compares the submitted numbers against the repository. Only numbers not found in the repository are actually tested; already tested numbers are skipped without further charges.

How a Dedup Repository Works: Unique Identifier (Number) + Historical Test Record Comparison

Each number uses its international format (e.g., 8613800138000) as a unique identifier. After uploading numbers in a task, the system traverses all repository records, removes matches, and only the remaining numbers enter the actual testing process. After testing, the new numbers and their results are automatically added to the repository, so they are skipped next time.

Added Value of the Dedup Repository: View Test Statistics, Avoid Re-purchasing or Regenerating Data

The repository not only records numbers but also the test time, test type (TG existence/active/inactive, etc.), and results for each number. You can check the total number of tests and distributions of different statuses at any time, serving as a basis for subsequent data reuse and cost accounting. This prevents accidentally repurchasing or regenerating the same numbers, further saving costs.

Three Steps to Achieve TG Number Deduplication — Taking KK-DATA as an Example

Below we use KK-DATA (https://app.kkdata.cc/) to demonstrate cross-task deduplication via the dedup repository. The process is clear and takes only three steps.

Step 1: Import Number List into the Dedup Repository

Log in to the KK-DATA console, find the “Data Dedup Repository” module in the left navigation (the exact name may appear as “Number Deduplication” or “Repository Management”). Click “Import Numbers”, select your existing historical tested number file (e.g., TG numbers previously tested with other tools). The system will add these numbers to the repository, marking them as “tested”. You can also add notes about the source or test type during import for easier management later.

Step 2: Create a TG Screening Task and Link the Dedup Repository

Go back to the “Create Task” page, select “Telegram Screening” type, and upload your new list of numbers to be tested. In the task settings, find the “Dedup Repository” switch, choose the repository you created earlier (or the default repository). The system will prompt: “After submitting the task, numbers already existing in the repository will be automatically excluded.”

Fill in other test parameters (e.g., activity window of 7 days, gender recognition, etc.) and click Submit. Before charging, KK-DATA first compares with the repository, calculates the number of new numbers, and displays an estimated fee. If the new count is 0, the task will indicate no charge.

Step 3: View Dedup Statistics and Task Results

After the task completes, go to the “Task Details” page and find the “Dedup Record” tab, which lists the number of duplicate numbers removed and the actual number of numbers tested. When exporting results, only the test data for new numbers (e.g., TG ID, valid/invalid) are included. If you need to review, you can return to the repository to view all historical test records; the repository is automatically updated with the new numbers from this task.

Best Practices: How to Plan TG Screening Tasks to Maximize Savings

1. First import all historical data: Regardless of which tool you used before, as long as you have a list of tested numbers (even just the numbers), import them into the dedup repository first. This immediately covers all tested records, so subsequent tasks will not retest them.
2. Merge and deduplicate before submitting batches: If you need to test the same audience multiple times over a period (e.g., weekly monitoring of activity changes), submit the entire number list to the repository once, then each time extract only the new numbers for a new task. Avoid testing the same number every week.
3. Set activity test windows appropriately: TG activity checks support windows of 7, 15, 30 days. If you only care about recent activity, you don’t need to run long-window tests on all numbers. Separating tasks by different windows also reduces repeated testing.
4. Use export results to update the repository: Some tools (e.g., 007data) may not include a “tested” flag in their export results. You can download the number list and manually import it into the KK-DATA repository, then automatically compare it when running tasks on other platforms.

Competitor Comparison: Dedup Capabilities of 007data, thdata and Other TG Screening Platforms

Currently, mainstream TG screening tools vary significantly in deduplication functions. Below is an objective comparison from three dimensions to help you choose based on your needs.

Platform	Built-in cross-task dedup repository	Separate charge for dedup	Ease of operation
KK-DATA	Yes, supports automatic cross-task comparison and historical record management	Repository is free; testing charged by actual new numbers	Three steps, intuitive console
007data	Partial (requires manual upload of exclusion list)	No separate charge, but cannot actively block duplicates	Need to manually import exclusion file in each task, cumbersome
thdata	No public explicit support	—	Users must deduplicate manually in Excel (VLOOKUP)

Functional Dimension: Built-in dedup repository vs. manual dedup required

• KK-DATA: Built-in dedup repository, supports long-term storage of historical records, automatic comparison when creating tasks.
• 007data: No separate repository, but allows uploading an “exclusion number” file (txt/csv) when creating a task. This means you need to maintain a list of already tested numbers and upload it manually each time. If you forget to update or the exclusion file is incomplete, duplicates will still be tested.
• thdata: Detailed functions not publicly disclosed; based on user feedback, basically relies on user’s own Excel deduplication.

Pricing Dimension: Separate charge for dedup, refund for repeated tests?

• KK-DATA: Repository is free; testing is charged by the number of new numbers. If the system finds that all submitted numbers have already been tested, no charge occurs.
• 007data: No separate charge, but once a duplicate number enters the testing process, it is charged, and no refunds are supported. You must ensure the exclusion list is complete.
• thdata: Specific billing rules unknown; consult customer service in advance to confirm whether repeated tests are refundable.

Experience Dimension: Ease of cross-task dedup operation

• KK-DATA: Import once, effective for a long time. Each subsequent task only requires checking the repository, and the system handles it automatically. Very user-friendly for operations teams.
• 007data: Each task requires uploading an exclusion file separately, which is easy to forget or fail to update. Managing multiple tasks simultaneously increases overhead.
• thdata: More steps, requires manual deduplication by the user, not suitable for large-scale batch operations.

Frequently Asked Questions

Q: Is it necessary to use a dedup repository for TG number deduplication?
A: Not necessarily, but recommended. Manual deduplication is also possible, but it is easy to miss duplicates across tasks and cannot automatically link historical test records. Using a dedup repository automates comparison and saves effort.

Q: Is KK-DATA’s dedup repository free?
A: The dedup repository itself is free of charge, but testing tasks are billed per number. With the repository enabled, only new numbers are charged; already tested numbers are not charged again. Please refer to the real-time price on the console for exact rates.

Q: The dedup repository can deduplicate across tasks. If I previously tested numbers with 007data, can I import them into KK-DATA’s dedup repository?
A: Yes. As long as you have a list of tested numbers, you can manually import them into KK-DATA’s data dedup repository as reference data. Note that the import does not automatically verify the status of these numbers; it is only used for dedup comparison.

Q: After using the dedup repository, will duplicate numbers still appear in the screening task results?
A: Typically no. The system removes numbers already in the repository from the submitted list, so the task results only contain test data for new numbers. You can view historical test statistics in the repository.

Q: What if I want to retest a specific number (e.g., after a period of time)?
A: You can remove that number from the repository or mark it as “allow retest”, then submit again. KK-DATA supports repository management functions. For details, refer to the documentation (https://docs.kkdata.cc/) or contact customer service via Telegram @kkdata_robot.

---

Experience the cost savings of TG number deduplication now: Log in to the KK-DATA console (https://app.kkdata.cc/) and create your first dedup repository. If you encounter any issues during operation, feel free to contact customer service via Telegram (@kkdata_robot) for assistance. The full usage documentation is available at https://docs.kkdata.cc/.