Event attribution that respects the CRM you keep clean.
Field mapping you approve, three-tier match confidence, a review queue for anything uncertain, and sourced pipeline written to Salesforce or HubSpot within 48 hours.
One governed path from attendee list to CRM record
Attendees come in from event platforms and public registrations. What goes out is field-mapped, confidence-scored, and written to the Salesforce, HubSpot, and Apollo you already run.
Attendees in. Pipeline to your CRM.
What event tools usually do to a CRM
You are the one who answers for record quality after the event team signs a tool. This page is about what that tool should have to prove to you first.
The inherited event tool
- A vendor dashboard reports pipeline numbers that exist on no Opportunity record you can query
- Attendee CSVs arrive with no dedupe plan, and the cleanup lands on your team's Monday
- A tool gets write access to the CRM, and six months later nobody can say which fields it touched
- Sourced and influenced get blended into one number, and finance stops trusting both
- The enrichment contract, the DPA, and the compliance questions all route through a vendor you did not pick
The event pipeline, on your rules
- Field mapping your team picks and previews before a single record writes
- Three-tier matching by email, domain, and company name, with a confidence level on every match
- LOW-confidence matches held as suggestions for your review, never written silently
- Sourced and influenced pipeline as two separate fields your CFO can query independently
- Enrichment on your own vendor credentials, so the contract, DPA, and compliance posture stay yours
What writes where, and what gates it
Six record types, each behind a mapping your team approves. Shown here in Salesforce shape; on HubSpot the same records land as contacts, timeline events, and deal properties.
| Luminik record | Where it writes | Your control |
|---|---|---|
| Attendee (ICP-matched) | Lead or Contact, matched by email | You approve the field mapping first |
| Event touch | Campaign Member, status Responded or Attended | Statuses map to your campaign model |
| Voice note + AI summary | Task on the Lead or Contact | Attached to the timeline, never a new object |
| Booked meeting | Event + Task, linked to the Opportunity if matched | Only HIGH or MEDIUM confidence links |
| Sourced pipeline | Custom Opportunity field you pick | Named by your team, split from influenced |
| Influenced pipeline | Custom Opportunity field you pick | Campaign influence with guardrails |
Field-level detail lives on the Salesforce and HubSpot integration pages.
The rules behind every number
An attribution number is only as good as the rules that produced it. These are published, not proprietary, so you can defend the number without defending a black box.
Match rules you can read
A review queue for anything uncertain
Sourced and influenced, kept apart
A writeback window you can plan around
Built to pass your security review
The connection model assumes a RevOps team with opinions: scoped access, previewed mappings, sandbox validation, and an audit trail you can pull without asking us.
OAuth scoped to what it writes
Mapping preview before first write
Sandbox first, production second
An audit trail on every action
BYOV means the vendor relationship stays yours.
Luminik orchestrates enrichment through the Apollo, ZoomInfo, Cognism, or other vendor credentials you already hold. No second data contract, no paying twice for the same records, and no new compliance surface to explain to legal. See the full vendor list.
Questions RevOps asks before granting write access
Will this spam my CRM?
No. Three-tier matching (email, domain, company name) attaches attribution where the match is HIGH or MEDIUM confidence. LOW-confidence matches are saved as suggestions for your team to review before anything writes to the Opportunity. You decide what lands on the record.
What does Luminik write, exactly?
Leads or Contacts for ICP-matched attendees, Campaign Members for event touches, Tasks for voice notes and meetings, and sourced plus influenced pipeline on custom Opportunity fields you name. On HubSpot, the same records land as contacts, timeline events, and deal properties. Every field goes through a mapping your team approves.
Who owns the enrichment relationship under BYOV?
You do. Luminik calls your enrichment vendor's API with your own credentials, so your vendor agreement and DPA cover the enrichment layer. Luminik's DPA covers what it stores and processes on top. No data resale, and no raw profile payloads held past the vendor's own retention window.
Can we validate the writeback in a sandbox before production?
Yes. Pilot setup connects your sandbox, maps the fields, runs one event through sourcing, enrichment, sequencing, capture, and attribution, and validates the result with your team. Production is only connected after you have seen the exact shape of what writes.
What happens to a LOW-confidence match?
It waits. LOW-confidence matches are stored as suggestions with the matching evidence attached, and your team accepts or rejects them from a review queue. Nothing writes to an Opportunity record until someone on your side approves it.
RevOps had to re-map one custom field on Opportunities, but the writeback was clean within 48 hours from event end.
The detail your review will ask for
Bring an Opportunity. See exactly what would write to it.
20 minutes with your sandbox. We map the fields live, run one event through the motion, and show you the review queue before anything touches production.
Sandbox-first pilots on every tier. Details on pricing.