How to scrape Twitter emails from an X audience

To scrape Twitter emails, start with an X audience you can describe precisely, collect the available profile data, and keep only addresses that the source actually exposes. A follower count is not an email count. Many profiles publish no address, and a string that looks like an email is not necessarily a working mailbox.

This walkthrough covers account audiences, post audiences, hashtags, and custom account lists in Octrieve. The workflow was reviewed on 26 October 2026. The downloadable example uses fictional records; this article does not claim a live extraction rate.

1. Choose the audience before choosing a tool

Use followers when you want people following a relevant account, following when you want the accounts it follows, and a post audience when the discussion around a particular post is your starting point. A hashtag can surface a broader topic, but it also brings unrelated participants. An explicit account list is easier to audit when you already know whom you want to research.

2. Configure a small, reviewable job

1. Open the X dashboard and choose a mode available to your account.
2. Enter the input required by that mode. Do not paste a full search sentence into a field asking for one handle.
3. Set an email limit within the allowance shown in your account. A limit tells the job when to stop; it does not guarantee that the source contains that many addresses.
4. Where your plan permits bio keyword filtering, use it to narrow the returned profiles. A bio match is a text match, not proof of a person's occupation.
5. Start the job, then review its status and returned source links before expanding the audience.

For a first review, choose an audience small enough that you can inspect each result. Record the account or post, mode, run date, and job status. A completed job and a partial job should not be treated as the same coverage result.

3. Inspect the profile and the email separately

Octrieve's X profile normalizer looks for addresses exposed in the available bio text. If a bio has no address, it does not generate one from the person's name. Imported records have a different provenance from a fresh provider response; inspect the job source rather than assuming that every row was collected today.

Download the illustrative full CSV to see the current columns. Use Profile URL and Bio to review context, Email source for provenance, and Validation to understand the check performed. The exporter writes format_only; it does not certify deliverability.

4. Prepare the export for a specific campaign

The full export can place multiple addresses in one Email cell, separated by semicolons. Split that cell if your destination tool expects one address per row. The email-only export is a separate shape: one Email column, without the profile context. Keep the full export as your audit copy.

Remove duplicates across separate exports, apply your suppression list, and review whether each contact is relevant. Public visibility alone does not establish permission to send a message. A format check, a mailbox check, and a campaign permission decision answer different questions.

5. Measure coverage without inventing a success rate

Track profiles reviewed, profiles with a visible email, unique addresses retained, and relevant contacts retained. Divide unique addresses by profiles reviewed only when both counts cover the same job and review window. Do not use the account's entire follower count as the denominator for a partial run.

If the result is sparse, inspect a few profiles manually. An audience with no published contact details is a source limitation; increasing the requested email limit does not create missing addresses. Use the Twitter email scraper overview for product scope, or the bulk email scraper for export details.