To enrich a conference attendee list, load the list into a table, find each attendee's company domain, add firmographics (size, industry, location, funding), filter to your ICP, then find and verify work emails only for the accounts that pass. Add one line of recent company news for your top accounts so reps walk in with a reason to talk.
That order matters. Most attendee lists are messy (personal emails, company names without domains, job titles typed by hand), and most of the people on them will never buy from you. Filtering before you pay for contact data keeps the job cheap, and it gives your team a short list they can actually prepare for. This guide walks through where the list comes from, what to add, the step-by-step workflow, what it costs in credits, and what to do with the data after the event.
Where do you get an event attendee list?
How much data you start with depends on your relationship to the event:
You're a sponsor or exhibitor. Organizers often share a list of attendees who opted in to sponsor contact, usually as a CSV or through the event app. Check the terms: some lists can be used for pre-event outreach, others only after the event.
You're hosting the event. If you run it on Luma, Databar's Luma event guests importer pulls everyone who registered or was invited into a table with your Luma API key, so there's no export step.
You're attending. You usually won't get the full list. Build a partial one from the public speaker, sponsor and exhibitor pages, then treat those companies as your target accounts.
After the event. Badge scans and business cards become a second list that you'll match back against the first (more on that below).
What data should you add to an attendee list?
You don't need a dossier on 3,000 people. You need enough to decide who to meet and to make the first 30 seconds of the conversation specific.
Layer | Fields | What it's for |
|---|---|---|
Company | Domain, employee count, industry, HQ location, funding | ICP filtering and prioritization |
Contact | Work email (verified), LinkedIn URL, seniority | Pre-event outreach and follow-up |
Buyer | The person you actually sell to, if the attendee isn't them | Multi-threading the account |
Context | Recent news, launches, hiring, their session at the event | Talking points for top accounts only |
If you want a refresher on which company fields matter most for targeting, see our guide to firmographic data.
How to enrich an attendee list step by step
Here's the workflow in a Databar table. Each step is a column you add and run, so you can stop, filter and continue at any point.
Import the list. Create a table from the CSV (Databar accepts comma-separated files) or use the Luma importer. Map name, email, company and title columns.
Clean and dedupe. Attendee exports often include the same person twice (registered, then transferred a ticket). Remove duplicates on the email column before you spend anything. Our deduplication guide covers matching rules if names and companies are inconsistent.
Get a domain for every company. Company-name columns like "Acme" or "ACME Inc." can't be enriched reliably. The Company URL Finder waterfall turns a company name into a website, and every company enrichment after this step keys on the domain.
Add company data. Run the "Lookup company data" waterfall on the domain. It tries providers in the order you set (Muraena, Diffbot, Owler, CompanyEnrich, People Data Labs and others) and stops at the first one that returns a record. Put the cheaper providers first. See how waterfall enrichment works for how order affects cost.
Filter to your ICP. Filter on size, industry and geography, and exclude competitors, current customers, vendors and students. For most B2B teams this is where the list gets much shorter, and everything after this step runs only on the rows that pass.
Fix personal emails. Many people register with a Gmail address. A reverse email lookup waterfall returns the person's name, LinkedIn URL, title and current company from the email they used.
Find and verify work emails. Run the "Email by name" waterfall (Icypeas, Snov.io, Hunter, Findymail, Prospeo, Leadmagic and more) with a verifier such as ZeroBounce switched on. Unverified conference emails are a common source of bounces; our email validation guide explains the statuses.
Reach the buyer, not just the attendee. If the person attending is a coordinator and your buyer is the VP of Sales, add a "Find people by company and job title" column (Leadmagic) or ContactOut's decision-maker search for your target roles at ICP accounts.
Add context for the top accounts. For your top 20 to 50 accounts only, run the "Company news by website" waterfall (PredictLeads, Owler) or an AI Researcher column with a prompt like "one recent launch, hire or announcement from this company, with the date". Recent news is also a trigger in its own right; see news and PR monitoring.
Send it where reps work. Push the shortlist to HubSpot, Salesforce or Pipedrive with an "event: [name]" tag, or export to Google Sheets for the booth team.
How much does it cost to enrich an attendee list?
Databar prices each enrichment in credits, and the catalog shows the price per provider. Two billing rules keep event lists cheap: in a waterfall only the provider that returns data is charged, and lookups that return nothing aren't charged. A partial record that returns some data is charged.
Catalog prices as of September 2026 for the steps above:
Step | Enrichment | Credits per row (when data is returned) |
|---|---|---|
Domain from company name | Company URL Finder waterfall | 1 to 2.5, depending on which provider answers |
Company data | Lookup company data waterfall | 2 (Muraena) to 15 (People Data Labs) |
Person from personal email | Reverse email lookup waterfall | 3 (Snov.io) to 20 (People Data Labs) |
Work email | Email by name waterfall | 3 (Icypeas) to 22 (People Data Labs), plus about 1 for verification |
Company news | Company news by website waterfall | 4 (Owler) or 7 (PredictLeads) |
Custom research | AI Researcher | 5 |
An illustration, not a benchmark: say you have 1,000 attendees who already have company domains, and 250 pass your ICP filter. Company data with Muraena first costs at most 2,000 credits (1,000 rows at 2 credits, if every row hits the first provider). Work emails for the 250 cost at most 1,750 credits if every lookup stopped at a 6-credit provider and was verified. News for the top 50 at Owler's 4 credits is 200. That's under 4,000 credits in the worst case for those assumptions, which fits inside the 5,000 credits on the Build plan ($99/month). Your real number depends on provider order and how many rows return data. For budgeting across the year, see how much to spend on data enrichment.
How do you book meetings before the conference?
Everyone gets "let's meet at the event" emails in the two weeks before a conference. The ones that get answered do three things:
Say something true about their company. A recent launch, a new market, a hiring push. This is what the context column is for.
Connect it to one problem you solve. One sentence, no feature list.
Ask for something small and specific. "15 minutes at the coffee bar on day two?" beats "let's find time to connect".
Keep it to your top accounts. For the next tier, the enriched list is a booth and session plan: who to look for, and what to ask when you find them.
What should you do with the list after the event?
Import badge scans and card photos into a second table, then match them back to the pre-event table on email or name plus company. Anyone you already enriched keeps their data, so you only pay to enrich the new people you met. Then tier the follow-up:
Hot: real conversation, ICP fit, a stated next step. Follow up within a day and reference what they said.
Warm: ICP fit, short conversation. Follow up within two days with one relevant resource.
Nurture: scanned badge only, or outside your ICP. Add to the CRM with the event tag and let marketing handle it.
If you've been building an account list for the event anyway, the same enrichment makes it a reusable account profile afterwards. Our guide to account-based enrichment covers what to keep updating.
Where Databar fits
Databar gives you 100+ data sources inside one table: import the attendee CSV or your Luma guests, run waterfall enrichments for company data and verified emails, filter, and push the result to your CRM. The same steps are available through the API, CLI and MCP server if you'd rather run event prep from a script or an AI agent.
FAQ
How far in advance should you enrich an attendee list?
Two to three weeks before the event gives you time to enrich, filter, research top accounts and send outreach while people are still planning their schedules. If the list arrives late, skip straight to company data, the ICP filter and your top 20 accounts.
What if the list only has names and company names?
Start with a domain-finder step on the company name, then run company data on the domain. With a name and a domain, the email-by-name waterfall can look for a work email. Check a sample of the matched domains by hand first, since common company names can resolve to the wrong website.
Can you enrich attendees who registered with personal emails?
Yes. A reverse email lookup returns the person's current employer and LinkedIn URL where a provider has a match, and you can then find their work email. Not every personal email will match, and lookups that return nothing aren't charged.
Can I pull Luma event guests into Databar automatically?
Yes, for events you host. The Luma importer takes your event's API ID and your Luma API key and loads registered and invited guests into a table, where you can add enrichment columns as usual.
Is it OK to email conference attendees?
It depends on the organizer's terms for the list and on the privacy and anti-spam rules where your recipients are. Sponsor lists often come with conditions on when and how you can contact people. Check both before you send, and keep outreach relevant to the person's role.
Ready to prep your next event? Start free with a 14-day trial and 100 credits, or book a founder demo and we'll build the attendee workflow with you.
Recent articles
See all








