I have a conversation about dropdown properties at least once a week. Sometimes twice. And it always starts the same way: a client opens a property in HubSpot, scrolls through 85 options, and says “I don’t even know what half of these mean anymore.”
The thing about dropdown properties is they start clean. Someone builds them with five or six options that make sense. And then over the next two years, every new scenario gets its own value. Every conference. Every campaign. Every one-off source. Until the dropdown has 47 options, three of them are misspelled, two of them are duplicates with slightly different capitalization, and nobody can remember which one they’re supposed to use.
This week, I was on a call where a client’s lead source property had a value for a specific local chamber of commerce event. Not “chamber event” or “networking event.” The specific chapter, in a specific city. Another value had the same conference listed two different ways... one with the year, one without. So now you have data split across two values for the same event, and neither one tells you anything useful in a report.
Two years from now, someone on the leadership team is going to ask: “Do we actually close deals from that conference?” And the answer is going to be: “We don’t know, because we never tagged it consistently through the pipeline.”
That unanswerable question is the cost of a messy dropdown. Not today. Two years from now, when it actually matters.
The Long-Tail Dropdown Problem
Here’s the pattern. A company starts tracking lead sources or deal sources in HubSpot. The first version is clean: Website, Referral, Conference, Outbound, Partner. Five values. Everyone knows which one to pick. Reports make sense.
Then someone attends a specific conference and wants to track it separately. So they add “AWS Summit 2025” to the dropdown. Then someone else adds “HubSpot INBOUND.” Then “Trade Show - Chicago.” Then “Trade Show Chicago” (no dash). Then “Chamber of Commerce Thornton.” Then “Chamber of Commerce - Thornton CO.”
Now the dropdown has 30 values. Half the sales team picks “Conference” for everything because they don’t want to scroll. The other half picks the specific event but spells it differently every time. Your reports show 12 leads from “Conference” and 3 from “AWS Summit 2025” and 1 from “AWS Summit” (someone forgot the year), and you can’t answer the simple question: how many leads came from conferences this year?
This happens with every long-tail dropdown. Lead source. Deal source. Industry. Referral partner. Campaign. The more specific the values get, the less useful the property becomes.
The Fix: Two Properties, Not One
We’ve landed on the same framework across multiple clients now, and it works every time. Instead of one dropdown that tries to do everything, you build two.
Property one: the category. This is your high-level bucket. Website, Referral, Conference, Outbound, Partner, Paid, Organic. Six to ten values, maximum. These are the values that show up in your reports and dashboards. They answer the big question: where do our leads come from?
Property two: the detail. This is where the specifics go. “AWS Summit 2026.” “INBOUND 2025.” “Partner - Smith & Associates.” “Google Ads - California Campaign.” This property captures the granular information without polluting the category property.
The category property is what you report on. The detail property is what you reference when someone asks a follow-up question. “We got 47 leads from conferences this quarter” comes from property one. “Which conferences?” comes from property two.
This works because you’re separating the reporting question (what type of source?) from the context question (which specific one?). Your dashboards stay clean. Your follow-up answers are still there when you need them.
Rules for Dropdown Hygiene
Once you have the structure right, here are the rules that keep it clean:
No years in the category property. “Conference” doesn’t need a year. The date the lead was created tells you when. If you need to know which conference in which year, that’s what the detail property is for.
Consistent naming in the detail property. Pick a format and stick to it. “AWS Summit 2026” not “AWS Summit” or “AWS 2026” or “aws summit 2026.” Document the format. Share it with the team. Better yet, make it a dropdown instead of a text field so people can’t freestyle.
Audit quarterly. Every quarter, pull up your dropdown properties and look at the values. Are there duplicates? Values nobody uses anymore? Misspellings? A value that says “do not use” but keeps accruing records because nobody removed it from a form? We see this constantly. A legacy value that was supposed to be retired is still an option somewhere, and records keep landing on it.
Fewer values, always. If you’re debating whether something needs its own dropdown value, the answer is almost always no. It goes in the detail property. The category property should have so few options that picking the right one takes zero thought.
The Dropdown Decay Problem
One of the sneakiest issues with dropdown properties is decay. Values that were relevant two years ago are still sitting there. Nobody uses them. But nobody removes them either, because what if something breaks?
We audited a client’s portal recently and found a dropdown value that literally said “Zendesk Routed (do not use)” and it had records landing on it that month. Another client had a dropdown value for a role that hadn’t existed in the company for over a year, and contacts were still being tagged with it through a form nobody had updated.
Dropdown decay happens slowly. One obsolete value at a time. And it creates two problems: it makes the dropdown harder to use (more scrolling, more confusion about which value is “right”), and it quietly pollutes your data when records land on values that shouldn’t exist anymore.
The fix is boring but necessary. Audit your dropdowns. Remove or archive values that aren’t in use. Update forms and workflows that reference old values. And document what each value means so the next person who looks at it doesn’t have to guess.
The Question You Want to Be Able to Answer
Here’s the test for whether your lead source (or any dropdown property) is set up right:
Two years from now, your CEO asks: “How many deals did we close from conferences last year, and which conferences performed best?”
Can you answer that in under five minutes?
If yes, your properties are working. If the answer requires exporting data, manually de-duplicating values, guessing which misspelling maps to which event, and caveating the numbers because half the team used “Conference” and the other half used specific event names... your properties need work.
The data you track today is the report you can pull tomorrow. And a dropdown with 47 values, three misspellings, and no naming convention isn’t tracking data. It’s creating the illusion of tracking data.
If you want help cleaning up your properties and building a structure that actually supports reporting, that’s what we do.