Dreamforce is the largest event in the Salesforce ecosystem, drawing tens of thousands of attendees to San Francisco. For exhibitors selling into that ecosystem it is the highest-density gathering of the year.
It also carries a risk that does not exist at other events: your prospects are CRM professionals, and they will notice if your CRM hygiene is bad.
The credibility problem
At most trade shows, a follow-up email with a misspelled company name is a minor irritation. At Dreamforce, the recipient is often a Salesforce administrator who spends their working life cleaning exactly that kind of data.
A sloppy lead record produces a follow-up that says, implicitly: we are not good at the thing you care about. If what you sell touches CRM data at all, that is close to disqualifying.
So the standard at Dreamforce is higher, and it is higher in a specific way — not more polish, but better data.
What "better data" means here
- Clean field mapping. Structured fields, not a free-text blob dumped into the description.
- Attribution set at capture. Campaign, lead source and event set correctly when the lead is created, not retrofitted in a bulk update three weeks later.
- No duplicates. Dreamforce attendees frequently already exist in your CRM. Creating a second record for someone who is already a contact is the exact failure this audience notices.
- Context that survives. The reason the conversation mattered, in a field, not in someone's memory.
What to capture at Dreamforce
Ecosystem context is what makes follow-up relevant:
- Salesforce edition and clouds — Sales, Service, Marketing, Data Cloud
- Ecosystem footprint — managed packages, AppExchange tools in use
- Org complexity — number of users, admin-to-user ratio, whether they have a dedicated RevOps function
- Current workflow pain — specifically, in the area you address
- Buying role — admin, RevOps lead, sales leader, IT, procurement
- Whether they are already a customer — surprisingly often missed
California is an all-party consent state, with teeth
Dreamforce is in San Francisco, so California law applies. Penal Code §632 requires the consent of all parties to record a confidential communication.
California is the most consequential US state to get this wrong, because §637.2 creates a private right of action allowing recovery of $5,000 per violation or three times actual damages — without any need to prove harm.
Read "per violation" carefully. A booth team recording 300 conversations across three days without valid consent is not facing a single claim.
Practical process:
- Ask before recording, every time
- Wait for an explicit yes
- Re-ask when someone joins — Dreamforce booth conversations frequently attract colleagues
- Log the consent with a timestamp — in a state with a private right of action, the log is your defence
Full detail in our guide to two-party consent states.
There is an additional irony worth noting: at an event about customer data, being casual about your prospects' data is a bad look independent of the legal exposure.
A workable Dreamforce process
Before
- Deduplicate your CRM against the attendee list where possible
- Set up campaign and attribution fields so they populate at capture
- Agree the ecosystem qualification fields
- Rehearse the consent script — California is unforgiving
During
- Check whether they are already in your CRM before creating anything
- Ask consent, re-ask when the group changes
- Capture the ecosystem context, not just the interest
- Confirm the next step out loud
Each evening
Review while recoverable, and fix data quality issues the same night rather than accumulating them.
After
Follow up within 48 hours with something specific. This audience receives an enormous volume of post-Dreamforce email and discards generic messages instantly.
Why the CRM sync speed matters here more than usual
At most events, a lead sitting in someone's notebook until Friday is a lost opportunity. At Dreamforce it is also a demonstration.
If your product claims to improve how data reaches a CRM, and your own event leads take a week to arrive there in poor shape, the contradiction is visible to the exact people who will spot it.
This is the case Confee is built around — the conversation becomes structured CRM fields in under 30 seconds, which at Dreamforce is both the operational answer and the credibility answer.
The short version
Dreamforce prospects live in CRMs and judge you by yours. Capture clean structured fields, set attribution at creation, check for duplicates, and get California consent right — §637.2 makes it a per-violation exposure.
Related reading:
- Two-Party Consent States: Recording at US Trade Shows — the California rules
- Auto-Fill Salesforce and HubSpot From a Conversation — the integration mechanics
- CRM Field Mapping for Event Leads — getting the structure right
FAQ
What makes Dreamforce lead capture different?
The audience. Attendees are largely Salesforce admins, RevOps professionals and sales leaders who live inside a CRM. They notice bad data hygiene, and a sloppy follow-up damages credibility with exactly the audience least likely to forgive it.
Is California a two-party consent state?
Yes. Penal Code §632 requires all-party consent for confidential communications, and §637.2 creates a private right of action for $5,000 per violation or treble damages without proving harm.
How should Dreamforce leads be structured in the CRM?
To the standard the audience would apply themselves — clean field mapping, no free-text dumping, attribution set at capture, consistent lead source, and no duplicate records.
What should you capture at Dreamforce beyond contact details?
Salesforce edition and clouds, ecosystem footprint and managed packages, org complexity and admin-to-user ratio, current workflow pain, buying role, and whether they are already a customer.