B2B Data Enrichment from Twitter and GitHub: The Complete Guide

You have a prospect list — names, companies, maybe LinkedIn profiles. But you’re missing context: their tech stack, what’s on their mind right now, the topics they care about professionally. Twitter/X and GitHub are two data enrichment sources that most B2B teams leave untapped, and they can turn a cold outreach into a genuinely relevant conversation.

This guide walks you through what data you can actually pull from these two platforms, how to integrate it into your enrichment workflow, and what you need to know to stay GDPR-compliant.

Enrich your leads directly in Google Sheets

Derrick pulls social links, emails, and company data from your prospect list in a few clicks, without leaving your spreadsheet.

Try for free →

Why enrich beyond LinkedIn

LinkedIn is the default for B2B data enrichment. But stopping there means missing part of the picture. According to HubSpot research, salespeople who personalize outreach using multiple signals — recent activity, interests, tech context — get response rates 2 to 3x higher than generic approaches.

Twitter/X and GitHub don’t replace LinkedIn. They complement it. Each platform reveals a different dimension of your prospect:

For an SDR targeting CTOs or developers, GitHub is often more informative than LinkedIn. For a Growth Marketer prospecting founders or marketing leaders, Twitter/X surfaces their voice and current priorities in ways a LinkedIn profile never will.

Now that you understand why these sources matter, let’s look at what you can actually collect from each one.

What Twitter/X reveals about your B2B prospects

Directly visible data on a public profile

A public Twitter/X profile exposes several pieces of information useful for B2B enrichment:

• Bio: often more candid and direct than LinkedIn. It frequently includes title, company, and a link to their website or another platform.
• Location: approximate but useful for geographic targeting.
• Linked website: typically the company site or their LinkedIn profile.
• Account creation date: a proxy for digital seniority.
• Follower count: a signal of industry influence.

Intent signals: the real value of Twitter

Beyond static profile data, Twitter/X is a goldmine of behavioral signals for B2B prospecting:

Recurring themes: A prospect who regularly tweets about sales automation, no-code tools, or reducing prospecting costs is clearly in exploration mode. That’s a direct opening for a contextual, well-timed approach.

Competitor mentions: If a prospect mentions or criticizes a competing tool, that’s actionable intel for your pitch.

Trigger events: Hiring announcements, product launches, funding rounds — these are often shared on Twitter before they show up on LinkedIn. Catching them early gives you a relevant reason to reach out.

Real example: Sarah, an SDR at a RevOps SaaS startup, monitors the Twitter accounts of her ICP prospects (Sales Directors, Heads of Growth). When one of them tweets about struggling to keep their CRM data clean, she centers her outreach around that exact pain point. Her reply rate on this segment consistently exceeds 18%.

Finding an email from a Twitter profile

It’s possible in some cases:

• The bio sometimes contains an email address in plain text — common practice among content creators and freelancers.
• The profile link often leads to the company website, from which you can retrieve a contact email or run an email finder.
• Replies and threads: some prospects mention their email in public exchanges.

To automate that last step, the most effective approach is to grab the website URL from the Twitter profile, then run a website email and social media extractor on that domain to surface contact addresses.

What GitHub reveals about your technical prospects

GitHub is the go-to platform for technical profiles — developers, CTOs, VP Engineering, technical founders. For teams selling SaaS tools, APIs, or infrastructure solutions, it’s an exceptional data enrichment source.

Available data on a public GitHub profile

• Name and bio: often consistent with LinkedIn, but with a more technical angle.
• Public email: some users display their email directly on their profile — this is intentional and legal on their part.
• Company: a user-filled field that tends to be more up to date than LinkedIn.
• Location: less precise than LinkedIn, but present.
• Website or blog: link to a personal page or portfolio.

Technical data: the real differentiator

This is where GitHub outperforms every other source for technical profiles:

Programming languages: GitHub automatically calculates the languages used across public repos. In seconds, you know whether a developer primarily works in Python, JavaScript, Go, or Rust — essential if you’re selling a tool tied to a specific tech ecosystem.

Tech stack: Configuration files in public repos (package.json, requirements.txt, docker-compose.yml) reveal the technologies a team uses day-to-day — frameworks, databases, cloud services.

Open source contributions: Contributions to well-known projects signal technical interests and expertise level. A CTO contributing to a no-code automation project is clearly interested in that space.

Recent activity: Commit frequency gives a sense of how active someone is — and whether they’re likely to be receptive to outreach right now.

Real example: Mark, Head of Sales at an observability software company, uses GitHub to segment his prospects. He identifies companies whose engineers actively use open source monitoring tools like Prometheus and Grafana, then prioritizes those accounts in his pipeline. His qualification rate is 40% higher than on generic prospect lists.

Extracting emails from GitHub commits

A more advanced technique: every Git commit includes the author’s email address. These emails are sometimes accessible via the public GitHub API on public repos.

Key points to know:

• This practice is legal for publicly accessible data.
• Emails surfaced this way are often professional addresses or personal emails.
• GitHub now lets users mask their email in commits via their privacy settings — privacy-conscious users have typically done this already.

How to integrate this data into your enrichment workflow

Step 1: Find your prospect’s Twitter or GitHub profile

The first step is connecting a B2B prospect to their social profile. A few methods:

• From the company website: Most B2B sites display Twitter/X and GitHub links in the footer or “About” page. Derrick’s Website Email & Social Media Extractor can collect those links automatically from a list of domains in Google Sheets.
• From LinkedIn: A LinkedIn profile’s contact section sometimes includes a Twitter link. Derrick’s LinkedIn Profile Scraper surfaces this as part of its 50+ enrichment attributes.
• Manual search: [First Name Last Name site:twitter.com] or [First Name Last Name site:github.com] in Google to identify the right profile.

Step 2: Collect the relevant data

Once you have the profile, you can gather information using two approaches:

Manual (small volumes): Reviewing profiles individually for high-priority strategic accounts. Time-intensive, but worth it for key targets.

Automated (large volumes): Using the official Twitter/X and GitHub APIs to pull data at scale. Both APIs are documented and legal when used in compliance with their terms of service.

For less technical teams, no-code tools can query these APIs without writing a single line of code.

Step 3: Enrich and qualify in Google Sheets

Once data is collected, the enrichment step involves cross-referencing it with your existing data and qualifying it. Concretely in Google Sheets:

• Add a “Tech Stack” column fed by GitHub languages
• Add an “Interests” column based on recurring Twitter themes
• Use Ask Claude or Ask OpenAI in Derrick to automatically summarize a prospect’s profile from their Twitter/GitHub data and generate a personalized opening line for outreach.

Step 4: Score and prioritize your leads

With these additional data points, your lead scoring becomes significantly more precise. Criteria to incorporate:

• Twitter intent signal (tweeting about your core theme) → +20 points
• GitHub tech stack compatible with your solution → +30 points
• Public email available → +15 points
• Recent GitHub activity (commits in the last 30 days) → +10 points

Derrick’s AI Lead Scoring feature lets you automate this scoring directly in Google Sheets based on custom criteria you define.

GDPR and social media enrichment: what you need to know

This question comes up every time, and rightly so. Here are the key points for a compliant approach.

What’s legal

Public data is accessible, under conditions. GDPR doesn’t prevent collecting data that individuals have made publicly available — but it strictly governs how that data can be used.

Three conditions to meet for compliant enrichment from Twitter/X or GitHub:

1. Legitimate purpose: B2B prospecting relies on the legal basis of legitimate interest (Article 6.1.f of GDPR), provided that the people being prospected could reasonably expect to be contacted in a professional context.
2. Data minimization: Collect only what’s necessary for your commercial objective. Building exhaustive profiles for no clear reason is a compliance risk.
3. Right to object: Anyone you contact must be able to request deletion of their data and opt out of future outreach.

The ICO (UK) and CNIL (France) both publish guidance on applying legitimate interest to B2B prospecting — worth reading if you operate across these markets.

What creates compliance risk

• Sensitive data: Twitter can surface political opinions, religious beliefs, or health-related content. These fall into GDPR’s “special category data” and must never be collected or used for targeting.
• Personal non-professional emails: A personal email found in GitHub commits cannot be used for commercial prospecting without explicit consent.
• Retention: Enriched data must be deleted when it’s no longer relevant to your commercial purpose.

For a deeper dive into GDPR-compliant outbound, read our article on cold emailing and GDPR compliance.

Common mistakes to avoid

Problem 1: Confusing public activity with buying intent

Impact: You spend time enriching profiles with strong Twitter activity, only to find those prospects aren’t remotely in buying mode.

Solution: Cross-reference social signals with firmographic criteria (company size, industry, recent funding) before prioritizing a deep enrichment pass.

Problem 2: Using stale data

Impact: A GitHub profile last updated two years ago reflects a tech stack that may have been abandoned. You personalize a message around a technology they no longer use.

Solution: Filter by recent activity date — recent commits for GitHub, recent tweets for Twitter/X — before feeding data into your scoring model.

Problem 3: Collecting without documenting

Impact: In case of a GDPR audit, you can’t demonstrate where the data came from or what legal basis justified its collection.

Solution: Add a “Source” column in your Google Sheets and systematically log the origin of enriched data (Twitter, GitHub, LinkedIn, website, etc.).

Problem 4: Over-personalizing and triggering a “surveillance” effect

Impact: Mentioning in a first message that you’ve read six months of someone’s tweets can come across as intrusive and damage the relationship before it starts.

Solution: Use social data to calibrate your angle and timing — not to quote it back directly. “I saw you work with Node.js” (GitHub) feels natural. “I read all your tweets about the topic” does not.

Key takeaways

• Twitter/X surfaces real-time intent signals — current interests, pain points, trigger events — that help you personalize outbound at the right moment.
• GitHub exposes tech stack, coding languages, and sometimes a public email — invaluable data for prospecting technical profiles.
• The most efficient workflow starts by pulling social links from company websites, then enriching from those profiles.
• GDPR permits using public data for B2B prospecting under legitimate interest — provided you respect data minimization and the right to object.
• Derrick automatically retrieves social links (Twitter, GitHub) from a list of domains in Google Sheets, covering the critical first step of this workflow.

Conclusion: build a multi-source enrichment strategy

The most effective B2B data enrichment doesn’t rely on a single source — it intelligently combines several. LinkedIn for professional background, Twitter/X for intent signals, GitHub for technical context.

What’s usually missing is step zero: connecting your prospects to their social profiles in the first place. That’s where Derrick comes in — automatically extracting Twitter, GitHub, and other social links from your prospect domains, directly in Google Sheets, with no manual work.

Find your prospects' social profiles at scale

Derrick pulls Twitter, GitHub links and emails from any domain list in Google Sheets — in seconds.

Try for free →

Once those links are in place, your multi-source enrichment workflow can run with the right tools for each platform — and your personalization jumps to a different level.

FAQ

Can you find a prospect’s email from GitHub? Yes, if the user has made their email public on their profile or hasn’t masked it in commits on public repos. These emails are legally accessible, but using them for commercial prospecting requires a legitimate interest basis under GDPR, along with a clear opt-out mechanism.

Is Twitter/X still useful for B2B prospecting after the API became paid? Yes, for two reasons. Profiles remain public and manually browsable for targeted research. The API is also still available (at a cost) for teams that need to automate at scale. For smaller volumes, manual review of high-priority accounts remains highly worthwhile.

Which prospect profiles are worth enriching from GitHub? Technical profiles: developers, CTOs, VP Engineering, and technical founders. GitHub is especially relevant if you’re selling a SaaS product, API, infrastructure tool, or anything with a meaningful technical component.

Does Derrick scrape Twitter or GitHub directly? No. Derrick specializes in B2B enrichment from LinkedIn and company websites. However, its Website Email & Social Media Extractor feature automatically retrieves Twitter and GitHub links present on a company’s website — which is the first step in the workflow described in this article.

How long does it take to enrich 100 prospects from Twitter and GitHub? Manually, budget around 3 to 5 minutes per profile for a thorough review — roughly 5 to 8 hours for 100 prospects. With a semi-automated approach (link retrieval via Derrick, then targeted profile review), you can cut that down to 1 to 2 minutes per prospect by focusing on high-value data points.