Skip to main content
Event organizers and sponsors want to know who is actually in the room. The problem is that most event registrations come in on personal addresses. A Luma event can be 60 to 65% personal Gmail and other non-business emails, which tells you a name but not a company. Enrichment closes that gap. It takes an attendee’s email and resolves their professional identity: company, title, seniority, LinkedIn profile, company size, industry, and location. That is what lets heyBTW match the person to an account and connect them to pipeline. Enrichment never adds phone numbers.

What gets enriched

For each attendee, enrichment adds:
  • Company name and domain
  • Job title and seniority
  • LinkedIn profile URL
  • Company size and industry
  • Location
Enrichment uses a reverse email lookup. It works on business emails and resolves many personal-email registrations to a current company, which is exactly the case that simple email-domain matching would miss. No phone numbers are ever added.

Three ways to enrich

You can enrich automatically as events come in, on demand for a single event, or in one batch across everything already imported.

Auto-enrich new events

Turn on Auto-enrich new events and every event imported from Luma, Splash, or Zuddl is enriched automatically as RSVPs sync. It runs in the background, roughly 1 to 2 minutes per batch, and pulls new RSVPs as they arrive. Two settings control what auto-enrich touches:
  • Scope. Choose which attendees to enrich, for example Approved only, so you do not spend credits on registrations you have not approved.
  • Skip partner contacts. Exclude partner-side attendees. Useful when your partners’ contacts are already well-covered in your CRM, and it saves credits.
Per-event overrides win when set, so you can turn auto-enrich on globally and still control individual events.

Enrich a single event

You can run enrichment on one event on demand, either from the event row on the Enrichment page or from the attendee table inside the collab. heyBTW shows the number of leads and the credit cost before it runs, for example “Confirm update 47 leads, using 47 credits.” After it completes, the attendee table and AI insights populate with the new data.

Catch up on past events

When you first connect a source, use Catch up on existing events to enrich everything already imported in one run. Past-event enrichment is a one-shot pass over historical attendee lists and takes about 1 to 2 minutes per event. This is the fastest way to make attribution work from day one rather than waiting for new events to accumulate.

What to expect from match rates

Expect 80 to 85% of attendees to resolve to a person on a typical list. Apple-relay and single-use privacy emails cannot be matched, which caps even a clean list at around 90%. The Enrichment page shows a match rate on each enriched event so you can see how a given list performed.

Credits and billing

Enrichment is metered. One credit enriches one contact.
  • Free to start. New accounts include 100 free enrichments.
  • Plan allowance. Paid plans include a monthly credit allowance that resets each cycle. The meter on the Enrichment page shows what is left before any overage applies.
  • Overage. Once you pass your monthly allowance, extra enrichments cost $0.05 per credit, billed daily as they are used, so there are no surprise end-of-cycle spikes.
  • Re-enrichment is usually free. Re-enriching a contact within 90 days reuses the cached result at no cost. Credits are only spent when the data is genuinely refreshed.
  • Enterprise. Enterprise plans get a custom allowance and pricing. You can also buy additional credits at any time.

How it writes to your CRM

Enriched contacts sync to your CRM as Contacts. Company, title, LinkedIn, seniority, and company size update on sync. heyBTW is careful about what it does not touch:
  • Lifecycle stage is read from your CRM and never overwritten.
  • Your custom properties are untouched unless a funnel rule you set fires.
  • Enrichment is additive: it fills in missing fields rather than overwriting data you already have.

Partner attendees

Partner attendees are enriched along with everyone else by default. If your partners’ contacts are already well-covered in your CRM, turn on Skip partner contacts per event to exclude them and save credits.

How enrichment feeds the rest of heyBTW

Once an attendee is enriched, that data is persisted and reused everywhere.
  • Attribution. Better company identification means more attendees match to CRM accounts, so more of them connect to your pipeline.
  • AI Insights. The AI Event Attendee Insights panel and the Ask heyBTW AI agent answer with full context: titles, companies, seniority, and LinkedIn profiles.
  • Explorer. Enriched identity and firmographics show up on the person and company nodes you browse in the Context Graph Explorer.
  • Cross-event reuse. Enrichment results are cached. If the same person appears at multiple events, their data carries over and you do not pay to enrich them again within the 90-day window.