Order queue open · Verified lists delivered within 24–48 hours
How to build an event-based LinkedIn outreach system with Aimfox: finding events, building attendee lists, sequencing campaigns, and benchmarks for event-triggered outreach.
Ryan Mercer
B2B pipeline consultant, event-based outreach specialist · Updated June 24, 2026
Last updated: June 2026 · Ryan Mercer, B2B pipeline consultant, event-based outreach specialist
TL;DR — 7 things to know before reading
- LinkedIn event attendees are among the highest-intent prospect segments available for outreach because attendance signals active professional investment in the event's topic area
- Aimfox cannot directly access LinkedIn event attendee lists; the process involves manually identifying attendees via LinkedIn's attendee view and building a prospect list from that data
- The strongest event-based outreach angle is attending or registering for the event yourself, which gives you genuine context for the connection request: "We're both attending X next week"
- Event-based connection request acceptance rates typically run 35–50%, significantly above the 20–30% average for standard cold outreach, because shared event attendance is a social proof signal
- Timing is everything: reaching out 2–5 days before the event (warm invitation context) or within 48 hours after (hot follow-up window) outperforms mid-event outreach
- Build separate Aimfox campaigns per event so you can track which events produce the best pipeline outcomes and repeat those event types
- Pair event-based LinkedIn outreach with verified contact data from Quarvio (from $129 for 5,000 contacts), cold email via Instantly, and email infrastructure via Inframail for a complete multichannel event follow-up system
LinkedIn events are one of the most under-used targeting sources in B2B outreach. When someone registers for a LinkedIn event on "Building an outbound sales team" or "Revenue operations best practices," they are self-selecting into a segment defined by a specific professional challenge. That self-selection is infinitely more valuable than a job title filter because it reveals intent, not just role.
The prospect who registers for a webinar on cold email infrastructure is telling you they are actively working on outbound. The prospect whose job title is "Head of Growth" is telling you their role. One of these signals is current. The other is historical.
Event-based outreach with Aimfox takes advantage of the intent signal. The key operational reality is that Aimfox processes LinkedIn profile URL inputs — you build the attendee list manually from the event page and load it as a CSV. The workflow has more manual steps than a search-URL campaign, but the quality of the resulting prospect list more than compensates for the extra setup time.
This guide covers the full event-based outreach system: how to find the right events, how to build the attendee list, how to configure the Aimfox campaign with the right message angles for the event context, and how to time the outreach for maximum acceptance and reply rates. Quarvio covers the contact data layer. Aimfox covers the LinkedIn connection layer. Instantly handles parallel cold email. Inframail manages the email infrastructure.
LinkedIn event attendees share three characteristics that make them valuable outreach prospects:
1. Active professional development: someone who registers for a LinkedIn event on a specific topic is actively investing time in learning about that topic. This is a stronger intent signal than passive browsing.
2. Public commitment: registering for a LinkedIn event is a visible action. The attendee has flagged to their network that they care about this topic enough to commit time to it.
3. Shared context: you and the attendee share a frame of reference. Both of you registered for the event because you think the topic matters. This shared context gives your connection request a specific, genuine reason that generic outreach cannot replicate.
Per Aimfox reviews on G2, practitioners who use event-based targeting report acceptance rates significantly above their standard campaign benchmarks because the connection request context resonates with a prospect who just demonstrated interest in the same topic.
Not every LinkedIn event produces a valuable outreach prospect list. The events worth targeting have specific characteristics.
Search LinkedIn Events for terms your ICP cares about. Navigate to LinkedIn's Events section (accessible from the search bar, filter by Events) and search for:
Review 10–15 upcoming events and assess:
Events with 100–2,000 attendees produce the best prospect list quality. Under 100 is too small for a campaign. Over 5,000 tends to include very broad audiences with lower targeting precision.
Click into an event and view the attendees list (available on the event page, usually showing a preview of attendees with their profile thumbnails and headlines). Scan 20–30 visible attendees:
If more than 50% of visible attendees appear to be your ICP (by title, industry signals in headlines), the event is a viable prospect source.
Register for the event via LinkedIn. This is not optional for the outreach system to work well. Registration gives you:
Registration takes 15 seconds on LinkedIn and transforms your outreach angle from "I noticed you might be interested in this topic" to "We're both going to this event" — a fundamentally more compelling reason to connect.
Benchmark: 3–5 events identified per month, each with 100+ attendees, 50%+ ICP match in visible list, event registered.
LinkedIn does not allow direct export of event attendee lists. Building the prospect list requires a manual process of identifying and recording LinkedIn profile URLs from the attendee view.
On the event page, click on the attendee count to open the full attendees view. LinkedIn shows attendees in a grid with profile thumbnails, names, and headlines.
Apply any available filters in the attendee view to narrow to your ICP:
Scroll through the attendee list systematically. LinkedIn's attendee view is a standard profile preview — clicking each profile opens the full LinkedIn profile in a new tab.
For each attendee who matches your ICP criteria:
linkedin.com/in/[username])For a target list of 100–200 attendees, this process takes approximately 30–60 minutes. This is the most time-intensive step in event-based outreach. For events with very large attendee lists (500+), focus on the first 200 attendees who match your ICP criteria rather than attempting to capture all attendees.
After building the LinkedIn URL list, consider enriching it with verified business email addresses if you plan to run a parallel cold email campaign. Upload the LinkedIn URLs to your CRM or a list enrichment workflow that maps LinkedIn profiles to business emails.
Quarvio contact lists are filterable by job title, company size, industry, and geography. For event attendees where you have job title and company information from their LinkedIn profiles, cross-reference against a Quarvio export to find verified email addresses for multichannel follow-up. From $129 for 5,000 contacts, $199 for 10,000, $399 for 25,000, $699 for 50,000.
Before uploading to Aimfox, review the list for:
A clean list of 100–150 verified ICP-matching profiles from one event is more valuable than a list of 300 with 30% false positives.
Benchmark: 100–200 ICP-matching attendee LinkedIn URLs collected in a clean CSV, list reviewed for duplicates and false positives.
Failure mode: attempting to build the list too quickly and including attendees who do not match the ICP. Speed in list building costs quality in campaign results. The event-based system's value comes from list precision.
In Aimfox, navigate to Campaigns → New Campaign. Name the campaign with the event name and date (e.g. "SaaStr Attendees June 2026"). This naming convention:
Do not combine attendees from multiple events into one campaign. Different events have different outreach angles, and mixing them forces a generic note that works for neither.
In the campaign's prospect source, select CSV Upload and upload your attendee list CSV. Aimfox validates the LinkedIn profile URLs and shows the total count. Verify the count matches your expected list size.
The event-context note is the most powerful connection note available in Aimfox because it is specific, timely, and mutual. Both parties registered for the same event. The note references that shared action.
Template options:
Pre-event (2–5 days before):
"Hi [firstName], I also registered for [Event Name] next week. Always good to connect with others in this space beforehand — looking forward to comparing notes."
Character count: approximately 160. Adjust event name to fit within 300-character limit.
Post-event (within 48 hours after):
"Hi [firstName], we were both at [Event Name] yesterday. Really valuable session — would love to compare takeaways and stay connected."
Character count: approximately 155.
Both notes:
The follow-up sequence for event attendees follows the same 3-step architecture as standard campaigns but with event-specific context angles:
Message 1 (24–48 hours after acceptance): Reference the event topic specifically. What was the key takeaway? What question or challenge does the event topic relate to in their role? Keep it to 80 words.
"Hi [firstName], thanks for connecting. The [Event Name] session on [topic] was really timely — we're working with [jobTitle] teams on exactly this. Would love to share one thing we found works well for teams at similar stages if that's useful."
Message 2 (3–5 days later): Offer the specific value reference or proof point related to the event topic.
Message 3 (7–10 days later): Make the ask, referencing the shared event as the starting context.
Configure all three steps in Aimfox's sequence builder with the appropriate delays. Enable Stop on Reply.
Benchmark: dedicated event campaign created, attendee CSV uploaded, event-specific connection note written with event name, 3-step sequence configured.
Timing is the variable that differentiates average and exceptional results from event-based outreach. Three timing windows exist, each with distinct performance characteristics.
This is typically the highest-acceptance-rate window. The event is upcoming, attendees are thinking about it, and a connection from a fellow attendee is a natural pre-event networking action.
Best note angle: "I also registered for X next week — looking forward to connecting with others in the space beforehand."
Activate the Aimfox campaign 4–5 days before the event date. Configure the daily limit so the full attendee list is sent within the pre-event window (100 attendees at 25/day = 4 days).
The immediate post-event window is the hottest follow-up moment. Attendees are still in the mental context of the event, energy and enthusiasm are at peak, and a connection from someone who attended the same event feels like a natural extension of the event networking experience.
Note angle: "We were both at X yesterday — really valuable session. Would love to stay connected."
If you missed the pre-event window, launch the campaign within 24 hours of the event ending. After 48 hours, the relevance of the post-event context begins to decay.
For attendees you did not reach in the hot windows, a follow-up connection is still possible but requires a slightly different angle. Reference the event topic rather than the event timing:
"Hi [firstName], I've been connecting with people in the [event topic] space recently — your work at [company] caught my attention. Would love to add you to my network."
This angle works but performs at standard cold outreach rates (20–30% acceptance) rather than the event-context premium rates (35–50%).
Benchmark: campaign launched in pre-event or post-event window for highest performance. Post-event note sent within 48 hours of event end.
After each event campaign, record:
This event performance log shows you which event types and topic categories produce the best prospect quality for your ICP. Over 3–4 months, you will have enough data to prioritise events by ROI.
Most event categories on LinkedIn are recurring: monthly webinars, quarterly summits, annual conferences. Once you identify an event type that consistently produces 35%+ acceptance rates and 5%+ reply rates, calendar the future editions and build the prospect list for each edition.
Every accepted connection from an event becomes a 1st-degree connection on LinkedIn. 1st-degree connections appear in future event attendee lists as marked connections (removing the need to reconnect). They also appear in searches and can receive direct messages without a connection request.
Over time, a sustained event-based outreach program compounds: each event builds your network in the target vertical, which warms future outreach to new attendees who share connections with your existing event-built network.
Benchmark: event performance tracked per event, recurring event types identified at 3-month mark, connection network growth measured monthly.
| Setting | Recommended value | Why |
|---|---|---|
| Campaign name | Event name + date | Track performance per event |
| Prospect source | CSV (manually built attendee list) | LinkedIn event pages require manual collection |
| Prospect list size | 100–200 per event | Quality over quantity |
| Daily connection limit | 20–30 | Finish list within event timing window |
| Working hours | Prospect timezone, business hours | Standard safety practice |
| Connection note angle | Event mutual registration reference | Highest acceptance in event context |
| Note character count | Under 200 | Leave room for event name variable |
| Pre-event launch timing | 4–5 days before event | Hot pre-event window |
| Post-event launch timing | Within 24 hours after | Hot post-event window |
| Sequence: Message 1 delay | 24–48 hours after accept | Standard |
| Sequence: Message 1 angle | Event topic reference + value | Connect context to your offering |
| Sequence: Message 2 | 3–5 days later, proof/insight | Value delivery |
| Sequence: Message 3 | 7–10 days later, ask | Low-pressure CTA |
| Stop on Reply | Enabled | Always |
| Unibox tagging | Event name in tag | Identify event source of replies |
| Post-campaign record | Acceptance %, reply %, calls | Build event performance log |
When your company or a team member speaks at a LinkedIn event, the outreach context becomes even stronger. "I saw you attended the session where we presented on [topic]" is a direct shared experience reference. Run a post-event campaign to all attendees immediately after a speaking slot. The connection rate on post-speaking-slot outreach is typically 45–60% in the 24-hour post-event window.
Event hosts and speakers at relevant LinkedIn events are often senior professionals in your target vertical who have a public professional profile and recent relevant content. Target them separately with a different note angle that references their hosting/speaking contribution rather than shared attendance: "I attended your session on X — the point about Y was particularly relevant to the teams I work with."
For large events worth maximising, run two separate Aimfox campaigns to the same attendee list:
The second campaign uses a different note angle and catches attendees who ignored the pre-event request but are now in the hot post-event context.
For event attendees for whom you have verified email addresses (from Quarvio enrichment or direct search), run a parallel cold email sequence in Instantly that references the event in the subject line. "Following up from [Event Name]" subject lines have significantly higher open rates than generic cold email subjects in the immediate post-event window. Coordinate timing between LinkedIn and email so both touchpoints land in the same 24–48 hour post-event window.
LinkedIn allows any member to create and host events. Hosting a LinkedIn event on a topic relevant to your ICP:
A well-promoted LinkedIn event with 300+ attendees is equivalent to a curated ICP prospect list of 300+ people who self-selected into your topic. Run a post-event Aimfox campaign to all attendees within 24 hours of the event.
Events hosted by companies in adjacent spaces to your product (not direct competitors) often attract your exact ICP. For example, a CRM software company hosting a webinar on sales pipeline management attracts the same Head of Sales ICP that you target. Identify events hosted by non-competing companies serving your ICP and target their attendees.
Symptom: the event attendee view only shows a preview of attendees (e.g. "10 people you know" and then a blurred list).
Cause: LinkedIn limits attendee visibility to registered attendees or to first/second connections for some event types.
Fix: register for the event from your LinkedIn account. After registration, the full attendee view typically becomes accessible. If the event is hosted privately (invite-only), attendee lists are restricted to invited attendees only.
Symptom: after building the attendee CSV and reviewing it, fewer than 30% of attendees match the target ICP.
Cause: the event topic was too broad and attracted a wide audience that includes many non-ICP professionals.
Fix: do not launch the campaign. A 30% ICP match rate means 70% of your daily connection limit goes to unqualified contacts, dragging acceptance rates down and wasting outreach capacity. Select a more specific event or manually filter the attendee list to only ICP-matching profiles before uploading.
Symptom: 40%+ acceptance rate on the event connection note, but fewer than 3% reply rate on Message 1.
Cause: the connection note referenced the event effectively (earning the accept) but Message 1 did not continue the event context — it pivoted immediately to a generic pitch.
Fix: rewrite Message 1 to open with a reference to the event topic specifically. "The session on X covered exactly what we work on with [jobTitle] teams at similar companies" is a stronger opener than "I work with [jobTitle] teams on outbound." The event gave you a specific topic — use it.
Symptom: you launched the pre-event campaign but the event has already passed before all attendees were contacted.
Cause: daily limit too low relative to the attendee list size. A 150-attendee list at 20/day takes 7.5 business days — longer than most pre-event windows.
Fix: for events with large attendee lists, either increase the daily limit (if safe given account age) or prioritise the highest-ICP-match attendees (first 50–75 on the list) for the pre-event window and move remaining attendees to a post-event campaign.
Symptom: "We were both at X yesterday" note is being sent 4+ days after the event.
Cause: campaign was not launched promptly after the event.
Fix: switch to the extended follow-up angle: "I've been connecting with people in the [event topic] space — caught your profile while reviewing [Event Name] attendees." This is less compelling than the hot post-event note but more honest than claiming "yesterday" when it was 5 days ago.
Symptom: after uploading the attendee CSV, Aimfox shows fewer prospects than expected, with some URLs flagged as invalid.
Cause 1: some captured URLs are LinkedIn search result URLs rather than profile URLs. Cause 2: some profiles are deleted or deactivated.
Fix: open the flagged URLs in a browser. Valid LinkedIn profile URLs follow the pattern linkedin.com/in/[username]. Delete any URLs that are not in this format, open search result URLs (that contain /search/), or company page URLs (that contain /company/).
Symptom: event-based connection request acceptance rate is below 20%, similar to generic cold outreach.
Cause 1: the connection note is too long and gets cut off before the event reference is visible. Cause 2: the event name is misspelled or truncated in the note, breaking the context. Cause 3: the attendees in your list are primarily 3rd-degree connections (no social proximity).
Fix: verify the note is under 300 characters and the event name appears in the first 100 characters. Check that the event name is spelled exactly as it appears on the LinkedIn event page. Filter the attendee list to only 2nd-degree connections (add this step to your list-building process in the attendee view).
Symptom: Aimfox shows session error midway through an event campaign where you increased daily limits to finish the list before the event.
Cause: the elevated daily limit triggered a LinkedIn checkpoint verification that interrupted the Aimfox session.
Fix: pause the campaign. Reconnect the LinkedIn account in Aimfox. Reduce the daily limit to your standard conservative limit and reactivate the campaign. For future event campaigns, plan the timeline to allow natural daily limits to reach the full attendee list without needing to spike volume.
"The highest acceptance rate I've ever seen on an Aimfox campaign was 52% — from a post-event campaign the day after a SaaS sales summit. Everyone was still buzzing from the event and a connection from a fellow attendee felt completely natural. We had 18 calls booked from 200 connection requests. Nothing else comes close to that ROI per contact."
— Verified G2 reviewer, founder, B2B SaaS sales, Aimfox reviews on G2
"We host monthly LinkedIn events on outbound tactics and use Aimfox to follow up with every attendee within 24 hours of the event ending. The note is simple: 'Thanks for joining our session on X.' Acceptance rate runs 45–55% consistently. This has become our most cost-effective pipeline source. The event promotion costs time but the outreach cost is essentially zero beyond the Aimfox subscription."
— Verified G2 reviewer, marketing lead, demand gen agency, Aimfox reviews on G2
From a thread in r/sales discussing event-based LinkedIn outreach (389 upvotes):
"Event attendees are the only LinkedIn targeting I bother with anymore. The note writes itself — 'I also registered for X' is the most genuine connection request you can send at scale. Stop trying to fake personalisation on cold lists when event-based outreach gives you real shared context for free."
| Need | Tool | Notes |
|---|---|---|
| Verified contacts + email for event attendees | Quarvio | Cross-reference attendee LinkedIn URLs to emails |
| Email infrastructure | Inframail | Microsoft 365 inboxes, auto DNS |
| Post-event cold email | Instantly | "Following up from [Event Name]" subject line |
| LinkedIn event-based campaigns | Aimfox | CSV upload, event-context notes |
Can Aimfox automatically pull LinkedIn event attendee lists?
No. LinkedIn does not expose event attendee data through an API or allow direct export. Building the attendee list requires manually viewing the event's attendee page and collecting LinkedIn profile URLs. These URLs are then uploaded to Aimfox as a CSV prospect source.
What is a realistic acceptance rate for event-based outreach?
Pre-event and post-event campaigns targeting shared attendees typically achieve 35–50% acceptance rates, compared to 20–30% for standard cold outreach. The premium comes from the shared event context making the connection request feel natural and mutually relevant.
How many attendees should I target per event?
100–200 well-filtered ICP-matching attendees is the ideal range. Fewer than 100 produces insufficient campaign data. More than 300 typically requires relaxing ICP filters, which reduces the quality of the prospect list and lowers acceptance rates.
Should I reach out before or after the event?
Both windows work, with slightly different peak moments. The 2–5 day pre-event window is excellent for establishing a pre-event connection. The 0–48 hour post-event window is the hottest follow-up moment. If the event is recurring, build both pre- and post-event campaigns for each edition.
What note angle works if I did not attend the event myself?
If you did not register for or attend the event, you lose the strongest note angle ("I also registered / We were both there"). You can still target attendees using a topic-based angle: "I've been connecting with people focused on [event topic] — your background caught my attention." This performs at standard cold outreach rates rather than event-context premium rates.
How long should the attendee list be valid for outreach?
Within 2 weeks of the event. After that, the event context becomes stale and the note angles that reference shared attendance feel dated. If you have attendees who were not reached within 2 weeks, switch to a generic ICP-based note rather than an event reference.
Can I target attendees of events I host on LinkedIn?
Yes, and this is the most powerful configuration. When you host a LinkedIn event, you have full attendee visibility and maximum context legitimacy for follow-up outreach. A post-event note from the event host carries more authority than a note from a fellow attendee.
How do I handle the attendee list for very large events (1,000+ attendees)?
For very large events, filter the attendee list to only your highest-priority ICP sub-segment before building the CSV. Do not attempt to capture all 1,000+ attendees — you will not reach them within the relevant timing window and the list quality will suffer from trying to capture everyone. Target the top 150–200 highest-fit attendees.
What should Message 1 (the first follow-up after acceptance) say for event-based campaigns?
Reference the event topic specifically and connect it to something relevant to the prospect's role. Avoid pivoting immediately to a product pitch. A good Message 1 for an event campaign might be: "The session on [topic] touched on exactly what [jobTitle] teams I work with are dealing with right now. [One specific insight or observation]. Curious if your team is working through similar questions."
What is the best event type for LinkedIn event-based outreach?
Topic-specific webinars and summits with 100–1,000 attendees on subjects directly relevant to your ICP's professional challenges. These attract self-selecting audiences of professionals who are actively working on the topic. Large general industry conferences attract broad audiences with lower ICP density. Small invite-only events may limit your attendee visibility.
How does event-based outreach integrate with cold email campaigns?
For attendees where you have verified business email addresses (from Quarvio enrichment), run a parallel cold email sequence in Instantly with the event as subject line context. Coordinate timing: LinkedIn connection request first, cold email 2–3 days later. The multichannel approach is particularly effective for post-event outreach where the prospect is already in the mental context of the event topic.
Is event-based outreach safer for LinkedIn account health than standard outreach?
The outreach mechanics are identical to standard Aimfox campaigns from LinkedIn's perspective — connection requests and messages. Account safety depends on daily limits, working hours, and delay configuration, not on the targeting approach. The only event-specific consideration is avoiding spiking volume to finish an attendee list before an event deadline. Maintain your standard daily limits even for event campaigns.
Build the email layer for your event-based outreach
LinkedIn connections from events are the warm entry point. The revenue conversion happens across channels. Quarvio provides verified B2B contact data — cross-reference your event attendee LinkedIn profiles to find verified business emails for parallel cold email follow-up via Instantly. One-time purchase, credits valid for 12 months. From $129 for 5,000 contacts.