HubSpot 101 for Event Managers: How to Track Your Tradeshow ROI from Badge Scan to Closed Deal

Why Event Managers Need to Understand HubSpot

You run the tradeshow, you sign the contract, you manage the booth, the staff, the demos, the giveaways, the side dinners. And then, two months later, someone in Sales says "we did not see any pipeline from that show" — and you have no way to argue back, because the data lives in a system you do not control.

If your company runs on HubSpot, this guide is for you. The goal is not to turn you into a HubSpot admin. The goal is to give you enough working knowledge of how HubSpot tracks contacts, companies, deals, and tradeshow attribution that you can walk into a meeting with your RevOps lead and have a real conversation — not a deaf one.

A note before we start. HubSpot is different from Salesforce. If you have used Salesforce in a previous role, some of the concepts here will feel familiar, but the data model is genuinely different. Do not try to map one to the other one-to-one. We will flag the biggest differences along the way.

The HubSpot Objects Every Event Manager Should Know

HubSpot is built on a small set of core objects. If you understand these, you can understand 80% of what goes on inside the platform.

Contact

A Contact is a person. Anyone who fills a form, gets scanned, gets imported, or interacts with your marketing becomes a Contact. There is no separate "Lead" object in HubSpot. Everyone is a Contact from the first touch. What moves forward is their Lifecycle Stage (covered in the next section), not their object type.

Company

A Company is an organization. Equivalent to a Salesforce Account. Contacts are associated with Companies. One Company can have many Contacts attached to it. If five people from Volvo scan their badge at your booth, you ideally end up with five Contacts all linked to one Company record for Volvo.

Deal

A Deal is a sales opportunity with a dollar value, a stage, a close date, and an owner. Equivalent to a Salesforce Opportunity. A Deal is created when a qualified opportunity is identified — typically after discovery — and progresses through pipeline stages until it closes won or lost.

Marketing Campaign

HubSpot has a Marketing Campaign feature, but it works very differently from a Salesforce Campaign. A HubSpot Marketing Campaign is a tagging layer that groups together assets — emails, landing pages, forms, ads, blog posts, social posts — under one banner. You do not directly add Contacts to a Marketing Campaign the way you add Members to an SF Campaign. Contacts only become "associated" with a Campaign when they interact with one of the tagged assets.

For a tradeshow, you would create a Marketing Campaign called "IBTM World 2025" and tag your pre-event email, your registration landing page, and your post-event follow-up sequence under it. The system then tracks how those assets performed.

List

A List is a group of Contacts. HubSpot has two types:

• Static list: A frozen set of contacts at a moment in time. You add contacts manually or via a one-time import. They stay in the list until you remove them.
• Active list: A dynamic set of contacts that updates automatically based on criteria. If you create an active list of "all contacts with Lifecycle Stage = MQL and Original Source Drill-Down 2 = IBTM World 2025," the list refreshes itself as new contacts match.

For event managers, Lists do a lot of the work that Campaign Members do in Salesforce. We will come back to this in detail.

Property

A Property is what HubSpot calls a field. Contacts, Companies, and Deals all have properties. Some are standard (First Name, Email, Lifecycle Stage). Others are custom, built by your admin.

Engagement

An Engagement is an interaction logged on a record — a call, an email, a meeting, a note, a task. Every Engagement shows up on the contact's timeline automatically. This makes the contact history far more visible by default than it is in most other CRMs. When Sales picks up a contact two weeks after a show, they can scroll the timeline and see everything.

Custom Object

HubSpot Enterprise tier allows you to create your own objects beyond the standard set. This is critical for advanced event tracking, and we will cover it in detail in the Event Interaction section later.

Lifecycle Stage and Lead Status — The Two-Layer System That Trips Everyone Up

This deserves its own section because nine out of ten event managers I talk to get this wrong, including ones who have used HubSpot for two years.

HubSpot tracks where a person sits in your funnel using two different properties, not one. They look similar. They are not.

Lifecycle Stage — the macro funnel position

The standard stages are:

• Subscriber — opted into your newsletter or blog
• Lead — showed some interest (filled a form, attended a webinar, got scanned at your booth)
• Marketing Qualified Lead (MQL) — meets your marketing qualification criteria
• Sales Qualified Lead (SQL) — Sales has reviewed and accepted the contact
• Opportunity — has an open Deal attached
• Customer — closed-won
• Evangelist — post-purchase, advocate
• Other

Lead Status — a sub-property inside the MQL → SQL handoff

Typical values: New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected, Bad Timing. This is the micro-status that Sales uses to track their working state on a contact.

For event managers, the practical rule is:

• A badge scan typically sets Lifecycle Stage = Lead
• A booked demo or meeting at the booth typically sets Lifecycle Stage = MQL
• Once Sales accepts the contact and starts working it, Lifecycle Stage = SQL and Lead Status = Open
• When a Deal is created, Lifecycle Stage = Opportunity (HubSpot auto-progresses this)

If your team is not enforcing Lifecycle Stage updates after a show, your reports will look empty even when the show actually generated pipeline. This is the single most common reason event teams cannot prove ROI in HubSpot.

Follow the Lead: From Badge Scan to Closed Deal in HubSpot

Let us walk through what actually happens to one contact from the moment they walk past your booth to the moment a Deal closes.

Step 1: The Badge Scan or Booth Interaction

Someone walks up to the booth. A staff member scans their badge or logs an interaction in a scanner tool. Two things should happen in HubSpot:

1. A Contact is created (or updated if they already exist)
2. The Contact is associated with a Company (HubSpot tries to do this automatically based on the email domain — if the email is @volvo.com, HubSpot links it to the Volvo company record)

If your scanner tool supports it, you can capture much more than name and email at this stage. A logged interaction can record: what the person was interested in, which staff member talked to them, whether a demo was given, whether literature was sent, whether a follow-up meeting was booked. All of this should push into HubSpot as property values on the Contact, plus an Engagement (a note or meeting) on the timeline.

Step 2: Meeting or Demo at the Booth

If the visitor sat down for a real conversation, that is a different signal than a passing badge scan. A booked meeting at the booth should be logged as a Meeting Engagement on the Contact's timeline, with notes attached.

Step 3: Lifecycle Stage Progression

At the booth, your scanner tool (or your post-show workflow) should set the Lifecycle Stage. A passing scan = Lead. A real conversation or meeting = MQL. A demo with a clear next step = MQL with high intent.

Step 4: Post-Show Handoff to Sales

After the show, the contacts move from event team to Sales. In HubSpot, this typically happens through a workflow:

• A trigger fires when Lifecycle Stage = MQL and a property like "Tradeshow Attended" is set
• A Task is automatically created on the Contact, assigned to the right Sales rep
• A follow-up email sequence may be enrolled
• Sales reviews and either accepts (sets Lifecycle Stage = SQL) or rejects (sets Lifecycle Stage = Other / Disqualified)

This handoff is where most tradeshow pipelines die. We will cover that in its own section later.

Step 5: Deal Creation and Progression

Sales works the contact, discovers a real opportunity, and creates a Deal. The Deal has a value, a stage, a close date, and an owner. HubSpot's standard pipeline stages are typically:

• Appointment Scheduled
• Qualified to Buy
• Presentation Scheduled
• Decision Maker Bought-In
• Contract Sent
• Closed Won / Closed Lost

When a Deal is created and linked to a Contact whose Original Source Drill-Down 2 = "IBTM World 2025," that Deal is now attributable to the event.

Step 6: Closed Deal

The Deal closes won. Revenue is now linked back to the Contact, the Company, the Marketing Campaign, the List, the Custom Property, and (if you have configured it) the Event Interaction custom object. Your show generated pipeline. You can prove it.

How to Tag a Tradeshow in HubSpot — The Multi-Mechanism Pattern

This is the section where Salesforce veterans get frustrated. HubSpot does not have a single "Campaign ID" that does the work of an SF Campaign. Instead, you use a combination of four mechanisms, and each does part of the job.

1. Marketing Campaign

Create a Marketing Campaign named after the event. Tag every asset connected to the show under it — pre-event emails, registration landing page, booth signage QR codes, post-event follow-up sequences, paid ads driving registrations.

What this gives you: asset-level reporting. How many emails were sent, how many opens, how many form fills attributed to the campaign, how many contacts touched any campaign asset.

What this does not give you: a clean list of "everyone who was at the booth." For that, you need a List.

2. Static List of Attendees

Push every scanned contact into a static list called "IBTM World 2025 — Attendees." This is the closest thing to an SF Campaign Member roster. The list is frozen in time — these are the people you actually met at the show.

You can have multiple static lists per event: "IBTM World 2025 — Attendees," "IBTM World 2025 — Demo Given," "IBTM World 2025 — Side Dinner Guests." These slice the audience for different follow-up strategies.

3. Custom Contact Property

Build a custom property — typically a multi-checkbox or text — called "Tradeshows Attended" or "Event Source." When a contact gets scanned, that property gets updated.

This is the most reliable filter. Lists can get deleted. Marketing Campaign associations depend on asset interactions. A custom property sits on the Contact record forever. Sales and RevOps can filter, segment, and report on it for years.

4. Original Source + Drill-Down 1 + Drill-Down 2

HubSpot's built-in attribution. For event-generated contacts, set:

• Original Source = Offline Sources
• Drill-Down 1 = Tradeshow
• Drill-Down 2 = IBTM World 2025

This feeds into Revenue Attribution Reports later. Without it, your tradeshow contacts will look like "direct traffic" or "unknown" in attribution reports, and the CFO will not believe your number.

UTMs for Events — What They Cover and What They Miss

UTMs (Urchin Tracking Module parameters) are short tags appended to URLs that tell HubSpot where a click came from. They get captured automatically when a contact clicks a UTM-tagged link and lands on a page or fills a form.

A typical event UTM setup:

• utm_source=ibtm2025
• utm_medium=tradeshow
• utm_campaign=ibtm-world-2025

HubSpot stores these in the contact's Original Source Drill-Down properties and feeds them into Marketing Campaign reporting through Tracking URLs.

UTMs are useful for:

• Pre-event campaigns driving registrations (email, paid social, partner emails)
• QR codes on booth signage and giveaways
• Post-event follow-up sequences

UTMs are a useful complement, not a replacement, for the four-mechanism tagging pattern above.

Static vs Active Lists — When to Use Which for Tradeshow Segmentation

Both list types matter for events, and they do different jobs.

Static lists are for frozen audiences

Once you import attendees from a show, you do not want that list to change. New people should not enter automatically. Old people should not drop out. The list is your historical record of "who was at this show." Use static lists for:

• Post-show attendee roster
• Demo recipients
• Side event invitees
• VIP / executive interactions

Active lists are for dynamic segments

Use these when you want HubSpot to maintain the segment automatically based on criteria. For example:

• "All IBTM 2025 attendees whose Lifecycle Stage is still Lead two weeks after the show" — this list shrinks as Sales progresses them, and you can use it to trigger re-engagement workflows.
• "All tradeshow contacts from any 2025 event who became Customers" — this list grows as deals close, and feeds your "closed-won by event" reporting.
• "All MQLs from any tradeshow who have not been contacted in 14 days" — Sales accountability list.

Rule of thumb: if the audience should never change, use static. If the audience should reflect a live filter, use active.

Workflows — Your Post-Show Automation Engine

This is one area where HubSpot has a real advantage over Salesforce for event teams. HubSpot Workflows are visual, drag-and-drop, and accessible to non-admins (depending on user permissions). In many HubSpot shops, the event manager can build and own the post-show workflow without going through IT or RevOps.

A typical post-show workflow looks like this:

Trigger: Contact enters the "IBTM World 2025 — Attendees" static list AND Lifecycle Stage = Lead or MQL

Actions:

• Send personalized follow-up email within 24 hours
• Create a Task for the Sales rep who met the contact at the booth, with notes from the booth conversation
• If no response in 5 days, send a second email
• If no response in 10 days, notify the Sales rep with a reminder
• If contact replies or books a meeting, change Lifecycle Stage to MQL (if not already) and exit the workflow

You can build branches for different attendee types — VIPs get different cadences than passing scans, demo recipients get product-specific content, and so on.

Going Deeper: The Event Interaction Custom Object — How We Do It at Lodago

Standard HubSpot objects work fine for tracking a single tradeshow per contact. But events are not one-time interactions. The most valuable contacts are the ones you meet at three shows in a row, plus a webinar, plus a sponsored dinner. Standard properties cannot represent that history cleanly.

This is why at Lodago we built our HubSpot integration around a custom object called Event Interaction.

The problem standard fields cannot solve

If you use a single property called "Tradeshows Attended," it gets messy fast. Either you cram multiple values into a multi-checkbox (and lose context about when each happened) or you keep overwriting a single field (and lose history). Either way, when Sales pulls up the Volvo account, they cannot answer the question: "When did we last see them, and what happened that time?"

The Event Interaction object architecture

In HubSpot Enterprise, you can build a custom object. We architect it as follows:

• Object name: Event Interaction
• Association: Many-to-one with both Contact and Company
• Properties on each Event Interaction record: Event Name, Event Date, Event Type (Tradeshow, Webinar, Dinner, Workshop, Conference), Booth Visit (yes/no), Demo Given (yes/no), Meeting Booked (yes/no), Staff Member Who Met Them, Topic Discussed, Notes, Outcome / Next Step, Influenced Deal ID (if applicable)

Every time a contact is scanned at any event, a new Event Interaction record is created and associated with both the Contact and the Company. Over time, an account builds up a history of every touch.

What this enables

• Account-level reporting: "Show me all accounts we have met at three or more events" — gold for ABM strategies
• Repeat-engagement signals: "Volvo has been to four of our last six shows" — a signal Sales should not miss
• Cross-event attribution: a Deal can be linked back to multiple Event Interactions, not just one
• Side-event tracking: dinners, hospitality suites, and workshops finally have a home
• Historical context for Sales: when a rep walks into a meeting, they can scroll the Event Interaction history on the account, not just the most recent touch

Revenue Attribution Reports in HubSpot

HubSpot's Revenue Attribution Reports are how you actually prove the dollar value of your events to the CFO. They show how closed-won revenue traces back to the original sources, channels, and campaigns that brought the contact in.

The three attribution models HubSpot offers:

• First-touch: Full credit to the first interaction (often a tradeshow if that is where you first met the contact)
• Last-touch: Full credit to the most recent interaction before the deal closed
• Multi-touch: Credit distributed across all interactions (with sub-models: linear, U-shaped, time decay, J-shaped, W-shaped, full-path)

For events, first-touch and multi-touch are the most useful. First-touch tells you which events generated brand-new pipeline. Multi-touch tells you which events influenced deals that had multiple touches.

Custom Properties Cheat Sheet for Tradeshows

These are the custom properties we recommend asking your admin to build (or building yourself if you have permission) for tradeshow tracking in HubSpot.

On the Contact object

On the Company object

On the Deal object

Ask your admin to build these as a starting point. You can add more as your event program matures.

The Post-Show Handoff: Why Most Tradeshow Contacts Die in HubSpot

You can have the best data architecture in the world. If the handoff to Sales is broken, none of it matters.

The most common pattern is: the event team uploads the scanned contacts, sets the Lifecycle Stage to MQL, kicks off a follow-up workflow, and then... nothing. Sales never works the contacts. Two months later, the contacts sit in HubSpot with Lifecycle Stage = MQL, no Tasks completed, no Engagements logged, no Deals created.

The structural reasons this happens:

1. Sales does not trust event leads

They have been burned before. Half the badge scans were people who came for the t-shirt. Until you can prove that your scanned contacts convert better than cold prospecting, Sales will deprioritize them.

2. The contacts are not properly routed

If 800 contacts come back from a show and they all get assigned to a generic queue, nothing gets worked. Each contact needs to be routed to a specific Sales rep — ideally the one who met them at the booth.

3. The follow-up workflow does not include accountability

If the workflow ends after sending two emails, there is no consequence to Sales for not picking up the Tasks. The workflow needs to escalate — to the rep's manager, to a Slack notification, to a dashboard the CRO sees weekly.

4. The Lifecycle Stage never progresses

If nobody is enforcing that Sales actually moves contacts from MQL to SQL (or to Disqualified with a reason), the data rots in place. You cannot report on what nobody is updating.

The 5 HubSpot Reports Every Event Manager Should Know

These are the reports to bookmark and check weekly.

1. Contacts created by Original Source Drill-Down 2 (Event Name)

The basic volume report. How many new contacts did each event generate? Filter by date range and Drill-Down 2.

2. Lifecycle Stage progression for an event's static list

Take the "IBTM World 2025 — Attendees" static list and report on Lifecycle Stage distribution. How many are still Lead? How many MQL? How many SQL? How many Customer? This shows you whether the post-show progression is actually happening.

3. Deals associated with event contacts

A custom Deal report filtered to Deals where the Primary Contact's Drill-Down 2 = "IBTM World 2025." Shows the pipeline generated, sorted by stage and dollar value.

4. Revenue Attribution Report — First Touch by Event (Enterprise only)

The CFO answer. How much closed-won revenue traces first-touch back to each event? This is the number that justifies next year's budget.

5. Task completion rate on event contacts

A sales accountability report. Of the Tasks created from the post-show workflow, how many have been completed? How many are overdue? This catches the handoff problem early.

FAQ

Where to Go from Here

This guide gives you the working knowledge to walk into a conversation with your RevOps lead, your CMO, or your CFO and have a real conversation about how HubSpot tracks your tradeshow contribution. The next step is doing the actual setup work — and that is where many event teams get stuck.