Attio takes a different approach from traditional CRMs. Rather than fixed Lead and Contact schemas, you define objects, attributes and lists to fit how you actually work.
For trade show leads that flexibility is genuinely useful — and it is also the trap. A system that lets you model anything will let you model it badly.
Do not create an "Event Lead" object
The instinct is to create a dedicated object for event leads. Resist it.
The problem: a booth visitor is very often already in your workspace — from a newsletter, a demo request, a previous event. Creating them as a separate object type means:
- No visibility that they are a known contact
- Fragmented interaction history
- Reporting that cannot compare event-sourced against other pipeline
- A merge problem later
Model event leads on the standard People and Companies objects, with event context carried elsewhere.
Use Lists for the event
Attio's Lists are the right tool. A list can hold records from an object and carry its own attributes, which is exactly what an event needs.
Create a list per event — "Hannover Messe 2026" — with list-specific attributes:
| Attribute | Type |
|---|---|
| Conversation date | Date |
| Booth / session | Text |
| Qualification summary | Text |
| Next step agreed | Text |
| Budget indication | Number / Currency |
| Timeline | Select |
| Lead quality | Select |
| Owner | Actor reference |
The People and Companies records stay canonical; the event context lives on the list entry. No duplication, no fragmentation, and full history preserved.
Object attributes worth adding
A few attributes belong on the objects themselves rather than a list — anything true of the person or company regardless of which event you met them at:
- Incumbent solution — on Companies
- Decision role — on People
- First met at — on People, useful for attribution over time
Keep this set small. Attribute sprawl in a flexible system is a real failure mode, and Attio makes it easy to add fields nobody fills.
Getting data in
API. Attio's REST API is clean and well documented. It creates and updates records, adds them to lists, and sets list-entry attributes in a single flow. This is the right route for anything capturing the conversation and writing structured qualification directly — the model Confee uses.
Automations. Attio's built-in automations handle assignment, notifications and list movement without external tooling.
CSV import. Fine for badge scanner exports. As always, post-show and contact-only.
Automations worth setting up
On a record being added to the event list:
- Assign an owner — round robin or by territory
- Create a task for follow-up within 48 hours
- Slack notification for leads above a quality threshold
- Move between list stages as follow-up progresses
Attio's automation builder is straightforward enough that a sales ops person can configure this without engineering help — a genuine advantage over enterprise CRMs where the same change is a ticket.
The duplicate question
Attio matches on email and domain when creating through the API or import, and surfaces potential duplicates for review.
The reliable pattern remains: match on email before creating. If the person exists, add the existing record to the event list rather than creating a new one. That preserves their entire history — and means whoever follows up can see they have been in a nurture sequence for months, rather than opening with "great to meet you."
Post-show workflow
- Sync or import within 24 hours
- Review Attio's duplicate suggestions and merge
- Confirm every record is on the event list
- Check ownership is assigned
- Verify follow-up tasks exist
- Work the list by qualification, not alphabetically
Reporting
Because event context lives on a list, reporting is straightforward: filter by list, group by qualification or owner, and compare against other sources.
Over several events the "first met at" attribute becomes genuinely valuable — it lets you see which events produce customers over a multi-year horizon, rather than just which produced the most scans.
The short version
Attio's flexibility suits event leads well, provided you use it deliberately. Model on People and Companies, use a List per event with its own attributes, match on email before creating, and automate ownership.
Do not create a separate event-lead object. It fragments exactly the history that makes follow-up credible.
Related reading:
- CRM Field Mapping for Event Leads — designing the structure
- How to Sync Trade Show Leads to Pipedrive — a fixed-schema comparison
- Voice to CRM — how conversations become structured records
FAQ
How do you get trade show leads into Attio?
Through the API, an automation platform, or CSV import. Attio's data model is flexible, so the important step is deciding the structure and creating the attributes before the event.
Should event leads be a separate object in Attio?
Usually not. Model them on the existing People and Companies objects with a list for the event. A separate object fragments data and hides that a visitor is already a known contact.
What is the best way to organise a specific event in Attio?
Use a List. Lists carry their own attributes, so event-specific fields live there while People and Companies records stay canonical — event context without duplication.
Does Attio handle duplicate event leads automatically?
It matches on email and domain at creation and surfaces duplicates for merging. Matching on email before creation remains the reliable approach.