Salesforce is the system of record for event-sourced pipeline.
Writeback in 48 hours.
OAuth. Field-mapped by your RevOps team. Sourced and influenced pipeline on Opportunity custom fields within 48 hours. Campaigns, Leads, Contacts: all in the Salesforce your team already queries.
How the Salesforce integration works
Four steps, each with a specific thing it does and a specific Salesforce surface it touches. No marketing wand-waving.
Connect via OAuth
One OAuth handshake, scoped to the objects Luminik writes. No password stored, no custom connected app to configure. Your Salesforce admin approves the scope list, Luminik stores a refresh token, and the connection is live.
Scopes, api refresh_token full Field-level mapping
Map every Luminik field to a Salesforce field you pick. Standard or custom. Attendee title into Lead.Title. Event name into Campaign.Name. ICP score into a custom field you own. Changes go through a preview step before a single record writes.
Configurable per org, per integration Attribution writeback within 48 hours
Within 48 hours of event close, Luminik writes event-sourced pipeline back to Opportunities. Sourced and influenced are split across separate fields. Your CFO gets the number Marketing can defend.
Custom Opportunity fields, named by your RevOps team Hourly sync, on-demand refresh
Engagement data flows back hourly on a cron (webhooks land in v1.1). Need a push right now? Trigger sync on any list and the queue fires immediately. No waiting for the next tick.
Sync cadence, hourly or manual What writes where
Every Luminik field maps to a Salesforce object and field you can point at. Here's the default. Change any row during mapping.
| Luminik field | Salesforce object / field |
|---|---|
| Attendee (ICP-matched) | Lead or Contact (by email match) |
| Attendee target-account boost | Custom field on Lead or Contact |
| ICP score (explainable) | Custom field + reason-code picklist |
| Event touch | Campaign Member (Status: Responded / Attended) |
| Voice note + AI summary | Task on Lead or Contact, body truncated to 32K |
| Booked meeting | Event + Task, linked to Opportunity if matched |
| Sourced pipeline | Custom Opportunity field you pick |
| Influenced pipeline | Custom Opportunity field you pick |
Who this is for
RevOps teams where Salesforce is the source of truth
If it's not in Salesforce, it doesn't count. Luminik writes event attribution directly to Opportunities so the number your ops team reports is the same number marketing produced.
Marketing leaders defending the event line
You need sourced vs influenced pipeline as two Opportunity fields the CFO can pull up. Written back within 48 hours of floor close. No vendor screenshot in the path.
AEs who live on Lead and Contact records
The ICP score, the voice note, the meeting context: all on the Lead or Contact record the rep already opened in Salesforce. No second tool to check before the follow-up call.
We'd scan 1,500 badges at Black Hat and create maybe 20 opportunities. With Luminik writing back to Salesforce within 48 hours, the post-event review stopped being a PDF and started being a pipeline query.
Salesforce-specific questions
What Salesforce edition do we need?
Enterprise or Unlimited for custom field writeback. Professional works for standard fields only, with the caveat that the attribution split relies on custom Opportunity fields. Lightning Experience is assumed. Classic works but isn't actively tested.
How do field-level permissions work?
Luminik writes under the OAuth user's profile. The connecting admin picks a profile with write access to the fields being mapped. Anything you don't grant, Luminik doesn't touch. The mapping UI flags fields the connected user can't write before you save.
Can we test in a sandbox first?
Yes. During pilot setup we connect your sandbox, do the mapping, run one event through the full motion (sourcing, enrichment, sequencing, capture, attribution), and validate the writeback shape with your RevOps team before touching production. Sandbox-to-prod field differences are surfaced in the mapping diff.
What about custom objects and roll-up summaries?
Custom objects are supported for writeback targets if they have Lead or Contact lookups. Roll-up summary fields behave normally, Luminik writes to the child records and Salesforce aggregates on its own schedule. We don't force a recalculation.
Will this spam my Opportunity records?
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 RevOps team to review before anything writes to the Opportunity. You decide what lands on the record.
See the Salesforce writeback on your sandbox.
20 minutes. Bring a RevOps lead and one Opportunity you want attributed. We do the mapping live and show the exact fields Luminik would touch.