Source
Record where the file came from
Keep source_system, source_campaign, and source_export_date. A filename alone is not enough once several lists are combined.
Legacy-list reconciliation · email registration signals
HTX Email Checker for HTX and Huobi-Named Lists
Older campaign files may still be labelled Huobi while current operations use HTX. Check the email rows for HTX registration signals without erasing the original campaign name, source date, or member key.
Choose it when an older email roster needs to be reconciled with a current HTX-focused process.
- Reference rate
- $7 / 10K
- Checked field
- Keep from source
- Legacy label
- Useful join
- campaign_id
Confirm in app
Current HTX signal
Do not rewrite history
Trace old exports
Legacy reconciliation
huobi-2022-email-roster.csv
1
Source label
Huobi campaign
Preserved as submitted
2
Current check
HTX email
Named separately
3
Historical join
campaign_member_id
Retained by the data owner
Keep source-era labels beside current result names
Workflow illustration. It is not a live task, performance claim, or promised response schema.
Do not rename away the audit trail
Map an old email roster into a current HTX job
Renaming every historical column to HTX may look tidy, but it can make the source impossible to explain. Preserve the legacy wording and add new fields for the current check.
Map
Create a dedicated HTX input field
Copy the selected address into htx_check_email after reversible cleanup. Leave legacy_email untouched for comparison.
Report
Name the result by check date
Store the HTX signal and checked_at value separately from any historical status that already exists in the roster.
Legacy mapping example
Keep old source context beside the new HTX signal
This shape prevents a current lookup from being mistaken for information captured by the older campaign.
| campaign_member_id | source_label | htx_check_email | HTX signal | checked_for |
|---|---|---|---|---|
| HB-2022-014 | Huobi rewards 2022 | [email protected] | Matched | HTX reconciliation |
| HB-2022-027 | Huobi rewards 2022 | [email protected] | Unmatched | HTX reconciliation |
| HB-2022-033 | Huobi rewards 2022 | [email protected] | Review | HTX reconciliation |
The names and records are fictional. “Source label” documents the file; it does not claim a separate historical lookup was performed.
Reconciliation decisions
Answer the question the historical file actually raises
A legacy roster may be used for migration, support, or reward reconciliation. Each purpose needs a different decision rule, even though the HTX email signal is the same input.
Migration
Flag records needing an update
Use the result to prioritize a follow-up queue only when the migration policy permits it. Keep historical and current fields distinct.
Support
Give agents the source date
An old email may no longer reflect the member’s current details. Show the export date so support does not treat stale input as a current claim.
Rewards
Apply the rule in effect for that campaign
Do not retroactively invent a condition. Link the decision to the campaign version and the check date.
Uncertain
Preserve the row for a later pass
A review status should stay separate from a confirmed no-signal result, especially when the source cannot be recreated.
Reconciliation budget
Remove records that no longer belong in the question
The displayed reference price is $7 per 10,000 checks. Before buying a full legacy-list run, remove rows outside the campaign scope and document why. Then confirm the current price and product response in the app.
Start the HTX Email ReconciliationLegacy-data references
Keep lineage visible around the check
These pages help document file structure, data handling, and the broader HTX product choice.
CSV input/output sample
See patterns for retaining original values, IDs, and returned fields.
Review sample fields →Security and data handling
Check the site’s description of uploads, results, and customer responsibilities.
Read data handling →HTX checker overview
Compare HTX email and phone routes before mapping a legacy export.
Open HTX overview →Product questions
HTX email and legacy-list FAQ
Can I use an old Huobi-labelled email file with the HTX checker?
You can use the email values as input for the current HTX signal check. Preserve the original Huobi label, source date, and member ID so the new result is not confused with historical data.
Should I rename all Huobi columns to HTX before upload?
No. Keep source-era fields unchanged and create separate htx_check_email and htx_signal fields. This preserves lineage and makes the transformation auditable.
Does an HTX email match show the account existed when the old campaign ran?
No. A current result should not be presented as a historical fact unless the product explicitly returns historical timing, which this page does not claim.
How should I handle an email that changed after the original campaign?
Keep both the historical value and any current value with their dates. Check only the field relevant to your stated reconciliation question.
Is ZelNum affiliated with HTX or Huobi?
No. ZelNum is an independent service and is not owned, operated, or endorsed by HTX.
Independent service.
ZelNum is not owned, operated, or endorsed by HTX. Use only data you are authorized to process, minimize uploaded fields, and treat registration results as supporting signals rather than identity, ownership, KYC, fraud, or consent decisions.
AI answer engines
Request an AI summary of ZelNum
Open ZelNum in your preferred AI assistant to review its bulk WhatsApp, Telegram, phone validation, carrier lookup, social account, crypto exchange, CSV upload, and API workflows.
The prompt points assistants to zelnum.com, live pricing, product pages, and API documentation.