When you're managing thousands of attendees across multiple integrations, "Sync" is not a useful answer.

Until now, the Studio > Content > People view showed a fixed list of source types — Registration, Code, Organizer, Sync, Developer API, Excel Import. Helpful enough at a glance, but the moment you're running data syncs through multiple connectors, it all collapses into one ambiguous label. Debugging data issues becomes a scavenger hunt.

That's fixed. Source tracking in the People list now goes one level deeper.

What's New

When a connector pushes people into your event, the Source column now shows the connector's actual name instead of the generic "Sync" label. If you're syncing from ASP Events, you'll see ASP Events. If it's your registration platform, CRM, or any other connected tool — same deal.

Where You'll See It

• Studio > Content > People — the Source column now shows the connector name wherever it's available
• People export — Source Details are included in CSV exports so you can audit and filter outside Studio

Key  Behaviors 

• Automatic — no configuration needed. The connector name is captured and stored at import time.
• Legacy records keep their existing source label — this applies to people added going forward.

Why Organizers Will Love It

Multi-source events are the norm — registration platforms, CRM syncs, badge scanning systems, hosted buyer tools — they all funnel people into Swapcard through different pipes. When something looks off in your People list, you need to know which pipe caused it.

This update makes data auditing dramatically faster. Spot a duplicate? Check the source. Attendee missing a field? Check the source. Running a post-event report by acquisition channel? The data's already there.

Less "where did this person come from?" — more "let's fix it."

💡 Pro tip: Source Details are included in the People export — filter the CSV by source name to quickly segment attendees by acquisition channel.