✓ TestedWorks with CSV, Excel, Google Sheets → JSON-LD Schema
By dataclean.to team · 2026-02-12
Intercom collects email addresses from multiple touchpoints: in-app messenger conversations, support tickets, lead capture bots, and product usage tracking. Unlike dedicated email platforms, Intercom's contact data includes anonymous visitors who never provided an email, leads who gave a partial or fake address to a chatbot, and users identified only by their app user ID. dataclean.to processes your Intercom export to extract valid email contacts from this mixed-quality dataset.
The Problem
Intercom exports mix different contact types into one dataset: known users with verified emails, leads who typed an email into a chatbot field, and anonymous visitors with no email at all. The chatbot-collected emails are particularly unreliable because visitors enter text quickly to get past the 'What is your email?' prompt, resulting in addresses like 'no@no.com', single-character entries, or intentional gibberish. Intercom's JavaScript SDK tracks users by ID, and some user records have email fields populated by your app's backend rather than the user themselves, which may contain staging environment addresses (user@localhost, test@example.com) from development. Merged user profiles can have conflicting email addresses where the surviving record keeps the older, less accurate email. The export includes Intercom-specific fields like 'pseudonym' and 'anonymous' that need to be interpreted to know which contacts are real. Intercom data export guide
How to Fix It
1
Export user data from Intercom
In Intercom, go to Settings > Data Management and request a data export. This generates a CSV of all users, leads, and visitors with their email addresses, custom attributes, and conversation history metadata.
2
Upload to dataclean.to
Import the Intercom CSV. The platform processes the email column, immediately filtering out empty entries from anonymous visitors and flagging placeholder addresses from chatbot interactions.
3
Remove test and development addresses
Identify email addresses from staging or development environments: @localhost, @example.com, @test.com, and addresses matching patterns your development team uses for testing. These pollute production data through SDK misconfigurations.
4
Validate chatbot-collected emails
Scrutinize addresses that users typed into Intercom's lead capture bot. These have the highest error rate due to the casual input context. Correct domain typos and flag single-use throwaway addresses.
5
Export clean user contacts
Download validated user data, excluding anonymous visitors and confirmed fake entries. Use the clean list for product announcements, onboarding sequences, or migration to a dedicated email marketing platform.
Frequently Asked Questions
Why are Intercom chatbot emails so unreliable?
Chat interfaces create a casual context where users type quickly and carelessly. Unlike a formal signup form, a chatbot prompt ('What is your email?') feels temporary and low-stakes to the visitor. Many type the minimum required to continue the conversation, resulting in typos, fake addresses, or placeholder text.
How do I separate real users from anonymous visitors?
Intercom marks contacts as 'user', 'lead', or 'visitor'. dataclean.to preserves these designations. Filter to only users and leads with non-empty email fields to get contacts who have identified themselves.
Can I clean emails from specific Intercom segments?
Yes. Create a segment in Intercom with your desired filters, export that segment, and upload just that subset to dataclean.to. This is more efficient than exporting and cleaning your entire contact database.
Example: Input → Output
name
email
phone
city
status
Alice Johnson
alice@example.com
+1-555-0101
New York
active
alice johnson
ALICE@EXAMPLE.COM
5550101
new york
Active
Red rows show common data quality issues. dataclean.to normalizes and generates JSON-LD automatically.