Your Swapcard attendee list, working the pipeline.
The lists your event role already entitles you to, validated into Luminik and run through sourcing, enrichment, sequencing, capture, and attribution.
How the Swapcard integration works
Four steps from your side, and most of them are watching it happen.
Tell Luminik about your Swapcard event
You are sponsoring or organizing an event that runs on Swapcard. During onboarding you point Luminik at it; setup takes minutes, not a services engagement.
Your lists appear in the pipeline
The attendee and meeting lists your Swapcard role already entitles you to show up in Luminik as first-class records, validated row by row, not as a CSV somebody reconciles next week.
The rest of the motion runs
Those records flow through the same pipeline as every other source: ICP scoring, enrichment through the vendors you brought, sequencing, on-floor capture matching, and CRM writeback.
Attribution counts them
Pipeline that started as a Swapcard attendee row is attributed like everything else: sourced and influenced, split on Opportunity fields your RevOps team names.
Questions your ops team will ask
How does Luminik access our Swapcard data?
With your permission and your own event access, arranged during onboarding. Luminik reads only what your role on the event already sees, and your access details are never stored.
Is this allowed under Swapcard's terms?
The data is yours: lists your exhibitor or organizer role already entitles you to view. Nothing is accessed beyond your entitlement, and nothing is collected from accounts that are not yours.
What happens when something goes wrong?
The connection stops and a human looks at it with the specific reason. Nothing is guessed or written half-finished into your CRM.
Which roles work?
Organizer and exhibitor access. Attendee-level access sees too little to be useful for pipeline work.
Sponsoring an event that runs on Swapcard?
Bring it to the walkthrough and see your own attendee list land in the pipeline.