Dynamics 365 Sales handles event leads capably. The obstacles teams hit are rarely technical — they are organisational, and they need to be solved weeks before the show rather than during it.
The governance problem comes first
Dynamics is usually deployed in larger organisations with a central CRM administration function. Adding a custom field, publishing a duplicate detection rule or modifying a business process flow typically requires:
- A change request
- Review by a CRM owner
- Testing in a sandbox environment
- A release window
That process commonly runs two to six weeks.
The practical consequence: if you decide the week before a trade show that you need an Event Name field, you will not have it. The leads will be captured into notes, and the attribution will be lost permanently.
Start the field conversation two months before the event. This is the single most useful piece of advice for Dynamics users exhibiting at trade shows, and it is entirely non-technical.
Use the Lead table
Dynamics separates Lead from Account, Contact and Opportunity, with a formal qualification step converting one into the others.
Event leads belong in the Lead table:
- They can be disqualified cleanly with a recorded reason
- Accounts are not polluted with organisations you met once
- Lead-specific reporting stays meaningful
- Qualification is a deliberate act, not an import side-effect
Disqualification reasons matter here. Dynamics captures them natively, and reviewing them after an event tells you whether the event produced poor leads or your follow-up was poor — two problems with completely different fixes.
Fields worth requesting
Custom columns on the Lead table in Dataverse:
| Field | Type | Notes |
|---|---|---|
| Event Name | Choice | Must be a choice column, not text |
| Conversation Date | Date Only | |
| Qualification Summary | Multiline Text | |
| Next Step Agreed | Text | |
| Budget Indication | Currency | |
| Timeline | Choice | |
| Incumbent Solution | Text | |
| Decision Roles | Choice (multi) |
Request them as a single batch with a clear business justification. Piecemeal requests get deprioritised; a documented set tied to a specific event tends to move faster.
Business process flows for events
The standard lead-to-opportunity flow assumes qualification criteria that do not always fit an event context.
A dedicated event business process flow can require, before progression:
- Event Name populated
- Qualification Summary non-empty
- A scheduled follow-up activity
- An assigned owner
This prevents the characteristic post-show failure: 200 leads sitting in the first stage of the process, nobody owning them, nothing forcing movement.
Power Automate for the mechanics
Power Automate is the natural automation layer. Useful flows on lead creation where Event Name is set:
- Assign owner by territory or product interest
- Create a follow-up task dated within 48 hours
- Post to a Teams channel for high-value leads — visibility drives action in enterprise environments
- Trigger a marketing journey if Dynamics Customer Insights is in use
The Teams notification is underrated. In large organisations, a lead nobody sees is a lead nobody works.
Getting data in
Dataverse Web API. Creates Lead rows directly with all custom columns populated. The right route for anything capturing the conversation and writing structured qualification in real time — the approach Confee takes.
Power Automate connectors. Good for connecting forms, scanners or third-party capture tools without custom code.
Import wizard. Supports mapping and duplicate detection. Adequate for badge scanner CSVs, but post-show and contact-only.
Duplicate detection must be published
Dynamics duplicate detection rules must be created and published before they take effect. An unpublished rule does nothing, silently.
Configure at minimum:
- Lead vs Lead on email
- Lead vs Contact on email
Run a detection job after any bulk import. Enterprise CRMs accumulate contacts over years, and trade show attendees are frequently already present from earlier campaigns.
Post-show workflow
- Sync or import within 24 hours
- Run duplicate detection before anyone makes contact
- Verify Event Name is populated across the batch
- Confirm ownership assignment executed
- Check the business process flow started on each lead
- Qualify deliberately; disqualify with a recorded reason
Measuring event ROI
With a consistent Event Name choice column you can build a Power BI report showing leads created, qualification rate, opportunity value generated, win rate versus other sources, and time to close.
That is the analysis that justifies next year's stand — and in an enterprise, justification is what gets budget renewed.
The short version
Dynamics handles event leads well, but its governance model is the real constraint. Request your fields two months ahead, publish duplicate detection rules, use a dedicated business process flow, and automate ownership.
The technology is not the bottleneck. The change request queue is.
Related reading:
- CRM Field Mapping for Event Leads — designing the field structure
- How to Sync Trade Show Leads to Pipedrive — the SMB equivalent
- Auto-Fill Salesforce and HubSpot From a Conversation — the other enterprise CRMs
FAQ
How do trade show leads enter Dynamics 365 Sales?
Through the Lead table in Dataverse — via the API, Power Automate, or import. Dynamics uses a formal qualification process converting a Lead into Account, Contact and Opportunity, so event leads should start as Leads.
What is the biggest obstacle to event lead capture in Dynamics?
Governance, not technology. Adding custom fields or changing a process flow typically requires a change request taking weeks. Teams planning field changes the week before a show usually cannot make them.
Should event leads use a separate business process flow?
Often yes. A dedicated event flow can require the event name, qualification summary and a scheduled follow-up before progression, preventing post-show leads stalling in stage one.
How does Dynamics handle duplicate event leads?
Through duplicate detection rules, which must be configured and published in advance. Match on email at minimum, and run detection jobs after bulk imports.