Is a CSV after the event enough?

For a single small event with follow-up after close, yes. It is not enough when registration stays open during the show, when sales needs check-in the same day, or when you run many events and attribution has to survive past one spreadsheet.

What should sync first: registration or check-in?

Both, as separate events. Registration starts nurture and planning; check-in proves presence and should stop “see you tomorrow” reminders. Syncing only one of them recreates the gap most teams already hate.

How do integrations relate to GDPR?

The pipe does not create a legal basis. You still need a purpose and, where required, consent for marketing and for sharing with sponsors. Keep those flags distinct in the payload. This is operational guidance, not legal advice.

How do you connect event registration data to your CRM and marketing stack?

By Donghui Qian (Milo)Updated 3 October 20264 min read

Short answer

Treat registration as a source of person-level events, not a spreadsheet dump: agree one identity key, push create-or-update on register / pay / check-in / cancel with the fields sales actually use, and keep marketing consent separate from “they showed up.” A weekly CSV is fine for a one-off; a pipeline that cannot answer who checked in yesterday is not.

Summarise with

Most teams can export a registration list. Far fewer can say, without opening three tools, who registered this week, who paid, who checked in, and which campaign path they came from — with the same email as the CRM record sales already owns.

This guide is about the pipe between the event system and the rest of the stack. It is written for operators and RevOps, whether or not you use BagEvent.

The job is not “export attendees”

A CSV answers “who is on the list right now.” Sales and marketing need a different answer: what changed about this person, and when. Registration, payment, approval, check-in, no-show, refund and cancellation are separate events. If you only sync the final list after the show, you lose the timing that makes follow-up useful.

Moment	What changed	Why CRM cares
Registered	A person (or company contact) entered the funnel	Campaign attribution, nurture, capacity planning
Paid / approved	Intent passed a gate	Sales priority; remove from “still deciding” sequences
Checked in	They were physically (or digitally) present	Attendance proof; stop “reminder” mail; start post-event sequences
Cancelled / refunded	The seat is gone	Stop treating them as attending; fix pipeline stage
No-show	Registered, did not arrive	Different follow-up from “met us on site”

Agree the identity key before you build anything

Integrations fail quietly when the same human becomes two CRM contacts. Pick one matching rule and write it down:

Primary key: work email for B2B, or a CRM contact ID you already collect on the form.
Create vs update: if the email exists, update the contact; if not, create — and decide who owns the “company” field when registration and CRM disagree.
Duplicates: what happens when someone registers with a personal email that sales already has as work email. Name the rule; do not leave it to the first sync.
Guest / +1 records: whether companions become CRM contacts at all. Often they should not.

Fields that earn their place — and fields that do not

Sync the minimum sales will open. Extra columns that nobody maps become noise and break on the next form change.

Usually worth syncing: Name, email, company, job title, ticket or registration type, event name/ID, registration time, paid/approved status, check-in time, UTM or invite source, marketing consent flag.
Sync only if someone owns them: Custom questions, dietary needs, session picks, badge name — useful in ops, clutter in CRM unless a workflow uses them.
Keep out of CRM by default: Payment card references, internal notes, volunteer comments, raw webhook payloads.

Someone who checked in did not automatically agree to a sponsor list or a sales sequence. Keep three flags distinct in every sync:

Event / transactional mail — confirmations, schedule changes, venue notices.
Marketing from the organiser — newsletter, future events.
Share with named sponsors / exhibitors — only if you asked and they said yes.

If the CRM cannot store those separately, do not invent a single “opted in” field that means all three. That is how renewal arguments and complaints start. Detail for EU operators lives in the GDPR field guide.

CSV, native connector, or webhook — pick by how often truth changes

Approach	Fits when	Breaks when
Manual CSV	One event, small team, sales follows up after the show	Registration is still open, or check-in status matters the next morning
Scheduled export / Zap-style glue	A few events a year, stable form fields	Someone renames a question and the mapping silently drops
Native CRM connector	You live in HubSpot, Salesforce, or similar and want create-or-update on known events	Your process needs fields the connector never maps
Webhooks + your middleware	Multiple systems, custom scoring, or strict identity rules	Nobody owns retries, dead letters, and schema changes

A live pipe without an owner is worse than a weekly CSV with an owner. Name who gets paged when sync fails the week of the event.

Test the pipe the way the event will break it

Register, pay (or approve), cancel, and re-register the same email — check CRM for one contact, not four.
Check in a test badge and confirm attendance lands within the SLA you promised sales (same day is a different product from “eventually”).
Change a form field label and confirm the mapping still holds — or that someone is alerted.
Pull a no-show list the morning after day one and see whether CRM stages match reality.

What “good” looks like after the event

You should be able to answer, from CRM or a dashboard fed by it, without opening the registration admin:

How many people registered, paid/approved, checked in, and no-showed — by campaign or invite source.
Which contacts are safe to put in a post-event sequence, and which only get transactional mail.
Which exhibitors or sales owners received consented leads, and when.

If those answers still live in a slide deck assembled by hand, the integration did not finish — the export did.

Frequently asked questions

Only if sales or marketing will act on that person. Companion tickets, press, and staff passes often should stay in the event system. Create contacts for the roles you will follow up; keep the rest as attendance records.