tg valid vs tg active: Definitions, Screening Order, and Business Selection Recommendations

In overseas marketing and Telegram community management, bulk verification of whether numbers are usable is the first step. However, many teams easily confuse the two concepts of tg valid and tg active, leading to improper screening strategies — either wasting budget on checking the activity of a large number of invalid numbers, or relying only on validity and missing out on real reach effectiveness. This article provides a complete comparison of the core differences between tg valid vs tg active, from detection definitions, data types, cost logic to business selection, and gives best practice recommendations of “valid first, active second.”

What is tg valid? — The Core Definition of Registration Status Detection

tg valid (also called “tg registered” on the platform) means the number has completed Telegram registration and exists in the Telegram user database. This is the most basic screening dimension: it only verifies “whether registered” and does not involve any online behavior or recent usage.

The detection principle is to query the number in real time to confirm whether it is recognized by the Telegram system as a legitimate user. The returned results usually only have two categories: registered (valid) or unregistered (invalid/empty). Some detections can also export the corresponding tgid (Telegram internal user ID) for the number, which is convenient for subsequent user system building.

Data content and use cases of tg valid detection

• Output fields: registration status (yes/no), tgid (optional), number itself.
• Typical application scenarios:
  • Remove empty numbers from a large batch to obtain a reachable user base.
  • Serve as a “pre-filter” for subsequent active detection, avoiding wasting money on invalid numbers.
  • Basic risk control verification: determine whether a number has ever registered for Telegram (for fraud prevention or virtual number identification).
• Advantages: low unit price, fast speed, stable results. Since it only queries the registration status, the data source is updated frequently, and the false positive rate is extremely low.

Differences and similarities between tg valid and “tg registered”

In the KK-DATA console and documentation, “tg registered” is a common expression for tg valid. The two are completely equivalent and both refer to numbers that have registered for Telegram. When selecting the detection type, users only need to look for the “valid” or “registered” label and don’t need to dwell on it.

What is tg active? — Deep Screening from the Online Behavior Dimension

tg active detection further refines: it determines whether the number has had behaviors such as logging in, sending messages, viewing channels, etc., within a specified time window, thereby reflecting the user’s actual recent activity level.

The platform has multiple built-in activity window options, commonly 7 days, 15 days, 30 days. The detection comprehensively uses data sources such as last online timestamp, channel interaction records, etc., to generate an “active/inactive” label. Because it requires more complex analysis logic, the unit price of tg active detection is usually higher than tg valid detection.

How to choose an active window? (7 days/15 days/30 days)

Active Window	Applicable Scenarios	Expected Reach Rate
7 days	Timed events, urgent notifications, instant interaction marketing	Highest (users are online almost daily)
15 days	Regular community recruitment, DM promotion, product operations	Medium (most active users log in within two weeks)
30 days	User pool inventory, long-term silent user reactivation, high-base rough screening	Lower (may include users who haven’t used deeply for a long time)

Recommendation: If you have high timeliness requirements (e.g., must send today), choose 7 days; if you just want to screen potential users who “have used Telegram recently,” 15 days or 30 days are more economical.

Limitations of tg active detection

• Privacy settings: Some users turn off the visibility of “last online time,” causing active detection to rely on other behavioral data (e.g., group messages), which may miss some truly active users.
• Timeliness: The detection result is based on past window behavior; if a user becomes active right after detection, they won’t be marked. Therefore, the active status has a “snapshot” nature; it is recommended to complete detection 1-3 days before marketing.
• Higher cost: Compared to valid detection, active detection consumes more computing resources, so the unit price is naturally higher, making it unsuitable for full-scale distribution.

tg valid vs tg active: A table showing core differences

Comparison Dimension	tg valid	tg active
Detection Target	Whether registered for Telegram	Whether online/having behavior within a specified time window
Output Fields	Registration status (yes/no), tgid	Active label (yes/no), last online time (partially obtainable)
Data Update Frequency	Real-time, almost no delay	Depends on behavior logs, may have 1-3 day delay
Applicable Stage	Initial rough screening (eliminate empty numbers)	Pre-precise marketing screening (retain high-value users)
Cost Level	Low	Medium to high (see console real-time pricing)
Typical Unit Price	Low (see website pricing page)	Higher (see console)
Affected by Privacy Settings	No	Yes (some users are invisible)

Data type comparison: valid only answers “whether registered,” active answers “whether online”

tg valid outputs a true/false judgment: yes/no. tg active outputs a time-dimension-based judgment and may return the last online timestamp (if the user hasn’t turned off privacy), helping operators evaluate user stickiness.

Scenario comparison: Volume vs. Precision

• Volume stage (e.g., obtaining a basic user pool): Use tg valid first to eliminate invalid numbers at the lowest cost.
• Precise marketing stage (e.g., DM promotion, community invitations): On the basis of valid numbers, use tg active to screen recently active users to ensure ROI.

Why is “valid first, active second” recommended?

This is the best balance between cost and efficiency. Suppose you have 100,000 numbers, of which only 30,000 are registered for Telegram. If you directly run active detection on all numbers, you’d pay for active detection on 70,000 invalid numbers (and get no meaningful results). But if you run valid detection first and then perform active screening only on the 30,000 valid numbers, the total cost is greatly reduced.

Cost optimization: Valid detection unit price is usually lower than active detection

Under KK-DATA’s per-record billing model, the unit price of tg valid detection is much lower than that of active detection (specific numbers subject to the console real-time price). Suppose the valid detection unit price is X and the active detection unit price is Y (Y > X). For 100,000 numbers, valid first costs 100,000 × X, get 30,000 valid numbers; then active on those 30,000 costs 30,000 × Y. Total cost = 10X + 3Y. If you run active on all 100,000 directly: 100,000 × Y = 10Y. Since Y > X and 10X + 3Y is significantly less than 10Y (because 10X is usually less than 7Y), valid first then active saves a lot of budget.

Task flow design: Generate → Valid → Active → Export

Recommended business pipeline:

1. Global number generation (free): Use KK-DATA’s global number generation feature to generate target numbers by country/number range, or import your own CSV list.
2. tg valid screening: Submit the number list for tg valid detection, exclude all unregistered empty numbers.
3. Export valid numbers: Export the valid results (including tgid) as CSV/TXT.
4. tg active screening: Submit the valid number list for active detection and select the appropriate active window (7/15/30 days).
5. Export active list: Obtain a highly reachable user list for marketing, DM, or community invitations.

How to choose between valid and active for different business scenarios?

Community operation scenarios: Active numbers are core

Community recruitment and event operations require users to interact within a short period. If you send invitations to a bunch of registered but long-inactive numbers, conversion rates will be extremely low. Therefore, it is recommended to directly use tg active detection (e.g., a 15-day window) to ensure that reached users have recently been active on Telegram.

DM promotion scenarios: First valid for wide coverage, then active for precise filtering

DM promotion often requires high send volumes, but also needs to control the risk of being reported and banned. Initially, you can use tg valid to screen all registered numbers for a first round of broad reach (e.g., product preheating notifications). Then, based on feedback data (open rates, reply rates), identify high-value groups and perform tg active screening on those users for a second precise push.

Risk control verification scenarios: Valid is sufficient for basic verification

If you only need to determine whether a number has ever registered for Telegram, for fraud prevention or virtual account identification, tg valid detection is enough. Adding active detection only increases cost without substantial benefit.

How to complete tg valid and tg active screening in one click with KK-DATA?

In the KK-DATA console, the operation is very simple and requires no programming:

1. Log in and select the Telegram Screening module.
2. Upload a number file (supports CSV/TXT) or paste a number list.
3. In the detection type, check:
   • Check “valid detection” → get registration status.
   • Check “active detection” → can further select the active window (7/15/30 days).
   • You can also check both simultaneously; the system will automatically perform valid judgment first, then execute active detection on the valid numbers.
4. View the estimated cost before submitting, confirm and execute.
5. After the task is completed, export the filtered data from the results page (can include tgid and active label).

Frequently Asked Questions

Q: Which is more accurate, tg valid or tg active?
The accuracy of both depends on the data source update frequency. tg valid is based on real-time registration status, usually with high accuracy (>99%); tg active relies on recent behavioral records and may have a small number of missed detections due to privacy settings or data delays. KK-DATA’s active window includes multiple options; it is recommended to choose the 7-day or 15-day window based on business freshness requirements.

Q: Can tg active detection determine whether a user is online?
It can partially determine, but cannot guarantee 100% accuracy. Active detection mainly relies on behavioral data such as last online time and group messages. If the user has turned off the visibility of “last seen,” the platform may still estimate through other signals like channel interaction. The specific algorithm is not disclosed, but the results can be used for marketing reference.

Q: If I do valid detection first and then active detection, how is the total cost calculated?
Total cost = number of valid detection records × valid unit price + number of active detection records × active unit price (active detection is only performed on valid numbers). For example, 100,000 numbers, valid unit price 0.002 yuan, active unit price 0.008 yuan, valid rate 30%, then total cost = 100,000 × 0.002 + 30,000 × 0.008 = 200 + 240 = 440 yuan. If you directly run active on all 100,000, it would be 100,000 × 0.008 = 800 yuan, saving nearly half.

Q: Can tg valid detection always export tgid?
On the KK-DATA platform, tg valid detection supports exporting tgid (Telegram user unique ID), provided that the number is registered and the system can obtain the ID. In rare cases (e.g., the number is deactivated or abnormal), the ID may not be obtainable. The exported tgid can be used for subsequent user tagging or retargeting.

Q: Should I choose a 7-day or 15-day active window?
If the marketing campaign has high timeliness requirements (e.g., a limited-time lottery, tonight’s livestream), choose 7 days; for regular community operations (e.g., weekly push), 15 days is sufficient; if only doing user retention inventory, 30 days is more economical. It is recommended to first test both windows on a small batch to see the hit rate before deciding the full-scale window.

---

For more technical details and operation guides, please refer to the KK-DATA Official Documentation. Log in to the Application Console now to start screening, or contact customer service @kkdata_cc for personalized advice.