How to Find Conference Attendees on X Before an Event
By MentionLeads · July 26, 2026 · 8 min read
In short: Find conference attendees on X by monitoring four signals: replies to speakers, event hashtags, venue mentions, and explicit attendance announcements. Search each signal separately, verify that the person is relevant, then reply publicly about the topic they raised before suggesting a meeting. This works better than collecting everyone who mentions the conference because it prioritizes people already showing context and intent.
How to find conference attendees on X is not really a list-building problem. It is a signal-matching problem: who is attending, what do they care about, and is there a natural reason to speak before the event? I use a four-lane search workflow, then move qualified people into a private X List with the exact post that made them relevant.
Which X signals actually identify conference attendees?
The strongest signals are first-person attendance announcements and detailed replies to speakers. Event hashtags provide volume but plenty of noise, while venue mentions catch attendees who never use the official hashtag. Treat each source differently instead of combining every mention into one feed.
| Signal | Example search | What it tells you | Main weakness |
|---|---|---|---|
| Attendee announcement | "going to SaaStr" OR "see you at SaaStr" | The person says they plan to attend | Misses people using images or vague wording |
| Speaker replies | Replies under a speaker’s agenda post | Reveals the attendee’s actual problem or question | Some repliers will watch remotely |
| Event hashtag | #SaaStrAnnual filter:replies | Finds active participants and side-event chatter | Sponsors and content accounts dominate results |
| Venue mention | "Moscone Center" "Dreamforce" | Catches travel, booth, and meetup posts | Employees, locals, and vendors create noise |
Start with announcements because the attendance claim is explicit. Use speaker replies next because a reply such as “Will you cover SOC 2 reviews for enterprise deals?” gives you a much better opening than “Excited for the conference.” Hashtags and venue posts should fill gaps, not become your primary prospect list.
How should you build the searches before the event?
Create a small search map containing the official event name, common abbreviation, hashtag, speakers, venue, city, and attendance phrases. Run each query in X’s Latest tab so recent attendee posts do not get buried beneath popular sponsor content.
- Search exact attendance language: "going to Web Summit", "attending Web Summit", "see you at Web Summit", and "who else is going".
- Search plans and logistics: "Web Summit" coffee, "Web Summit" meetup, "Web Summit" dinner, and "Web Summit" recommendations.
- Search the hashtag with exclusions: #WebSummit -giveaway -sponsored -tickets.
- Search individual speakers: from:speakerhandle "Web Summit", then inspect replies to their agenda and session posts.
- Search venue plus event: "Altice Arena" "Web Summit" or the venue name combined with the conference dates.
Use `since:` and `until:` to isolate the useful window, and add `lang:en` if language matters for your outreach. X search syntax changes and occasionally ignores a filter, so open the Latest results and manually test one known post. The practical operators and exclusions are covered in this guide to X search operators for finding buyers.
How do speaker replies reveal the best people to contact?
Speaker replies reveal topic-level intent, not just attendance. Open posts where speakers share their session title, ask for audience questions, or announce office hours; then inspect replies for specific operational problems, tool comparisons, and requests for examples.
Suppose a revenue operations speaker posts about pipeline attribution. “Can’t wait” is weak. “Will you cover self-reported attribution for partner events?” is strong because you can respond to the actual question: share a field you use in HubSpot, mention a reporting limitation, or point them toward the speaker’s relevant session.
Reply in the existing thread before sending a DM. A useful public answer gives the person context when they visit your profile and lets the speaker or other attendees join in. This is the same principle behind building B2B lead streams from X replies: the reply content matters more than the keyword match.
How can venue mentions and hashtags find attendees the official account misses?
Venue and hashtag searches find people discussing travel, side events, booth setup, and local plans without formally announcing attendance. Require a second piece of evidence, such as the event name, date, speaker, badge photo, or first-person travel language, before labeling someone an attendee.
| Post | Classification | Next step |
|---|---|---|
| “Landing Sunday for Dreamforce. Any quiet breakfast spots near Moscone?” | Confirmed attendee with a logistics need | Recommend a specific place, then ask what sessions they are prioritizing |
| “Our team built the booth at Moscone today” | Likely vendor or contractor | Skip unless vendors fit your market |
| “Five lessons from #Dreamforce” | Could be a remote commentator or old recap | Check the timestamp and profile before engaging |
| “Free audit at booth 214 #Dreamforce” | Sponsor promotion | Do not treat it as attendee intent |
Do not reply with “Let’s connect at the event” to a restaurant request. Answer the request first. A useful response such as “The lobby café gets packed; try the place on Howard before 8:30” creates a reason for a follow-up, while an immediate calendar link makes the interaction feel harvested.
How should you qualify an attendee before starting a conversation?
Qualify on relevance, evidence, and conversation surface. The person should fit your market, show credible signs of attending, and have posted something you can respond to without forcing your product into the thread.
Record five fields in a sheet or CRM: X handle, company and role, attendance evidence, topic signal, and next action. Save the source-post URL. Without that URL, a list of handles loses the context that made each person worth contacting.
Use a private X List called something specific, such as “Fintech Summit prospects — April,” rather than following everyone. Check it once in the morning and once late afternoon for new questions, travel updates, and session reactions. This guide explains how to structure Twitter Lists for lead generation without turning the list into another unread feed.
A good candidate has two independent signals: for example, a “see you there” post plus a reply about data residency under a speaker’s session announcement. A hashtag in the bio or a generic repost is not enough. False positives waste time and produce the awkward DM: “Are you attending?” sent to someone who is not.
What should you say before asking to meet?
Lead with the post, not the conference. Make one useful observation or ask one narrow question, continue publicly if possible, and suggest meeting only after the person responds. The goal is a relevant exchange before the badge scan, not a disguised cold pitch.
- Weak: “Saw you’re attending. We help SaaS companies improve pipeline. Want to grab 15 minutes?”
- Better: “Your question about self-reported attribution caught my eye. We keep event source and buyer-stated source separate because reps overwrite the first field. Are you trying to fix reporting or rep adoption?”
- After a reply: “I’m at the attribution session Tuesday too. Happy to compare the fields we use over coffee afterward if useful.”
Avoid sending the same DM to every person using the hashtag. It ignores why each person posted and can trigger spam reports or account restrictions. Keep meeting requests optional, name a real session or time window, and stop after one unanswered follow-up.
What pre-event workflow keeps this manageable?
Run the workflow in three passes instead of monitoring X all day. Build the search map early, qualify active attendees during the final week, and use the last two days only for timely logistics or meeting coordination.
| Timing | Work to do | Output |
|---|---|---|
| Two to three weeks before | Save event, speaker, hashtag, and venue searches | A search map and first private List |
| Seven days before | Review replies and announcements; save source posts | A qualified shortlist with topic context |
| Two days before | Respond to current travel, session, and meetup posts | Live conversations and a few relevant meeting options |
| Event morning | Check the List for schedule changes and questions | Timely replies, not fresh cold outreach |
Do not automate replies from a keyword trigger. Conference posts are unusually context-sensitive: “Can’t make it this year” contains the event name but clearly is not an attendee signal. Automation is useful for collecting possible posts; a human should classify the post and write the reply.
Frequently asked questions
Can you find conference attendees on X without an attendee list?
Yes. Search first-person announcements, speaker replies, official hashtags, venue references, and side-event plans. Require at least one explicit attendance signal, such as “flying in Sunday,” and ideally a second signal tied to a session or topic.
How early should you contact conference attendees on X?
Start searching two to three weeks before the event, but prioritize conversations during the final week when travel and session plans become concrete. Contacting someone months early often produces vague exchanges; contacting them on event morning leaves no room to build context.
Should you DM conference attendees or reply publicly first?
Reply publicly first when the post gives you a natural opening. Move to DM after they respond, ask for details privately, or indicate interest in meeting. A public exchange makes the DM recognizable and avoids the cold-calendar-link pattern common around large conferences.
Start here
- Pick one upcoming conference and write four searches: an attendance phrase, the official hashtag, one speaker query, and the venue plus event name.
- Review the Latest results and save five people who show both attendance evidence and a specific topic signal.
- Reply to the two strongest posts with a useful answer or narrow question; do not mention your product unless it directly answers what they asked.
If you want to monitor those signals without repeatedly running every search by hand, MentionLeads can collect relevant X conversations for review.