CRM tags and custom fields: what to set up and why it matters for your business

What CRM tags and custom fields actually are

Most businesses that struggle to get value from their CRM have the same root problem: the data inside it is unstructured. Contacts sit in the system, but there is no reliable way to filter them, no consistent fields to run reports against, and no tagging logic that the team actually follows. Automations fail because the trigger conditions are never met. Email segments include the wrong people. The CRM becomes a glorified address book.

CRM tags and custom fields are how you fix this. Tags are flexible labels attached to contacts, organisations, opportunities, or projects. They are good for grouping records by category: relationship type (for example ‘Prospect’ or ‘Client’), campaign, service area interest, or anything you want to filter informally. Custom fields are structured data points with a defined type: a date, a number, a dropdown selection, or a text string. They are filterable, reportable, and automatable. Both tags and custom fields allow you to record information in the CRM that is relevant to you and your business.

The simplest way to distinguish them: tags are labels that describe what category a record belongs to. Custom fields are data fields that you add, to record data you want to query, calculate, or trigger on. If you need to know when something happened or how much something is worth, that is a field, not a tag.

If you use Capsule CRM, there is a third concept worth knowing from the start: DataTags. A DataTag is a tag that has custom fields attached to it. Those fields only appear when the DataTag is applied to a record, so your contacts stay uncluttered until the tag makes them relevant. When you apply a DataTag, a prompt appears to fill in the linked fields, and those fields are grouped together neatly on the record.

Contents

• Tags vs custom fields: how to choose
• How to build a CRM tagging system that works
• Designing custom fields that actually get filled in
• Practical tag and custom field examples by business type
• How tags and fields power segmentation and automation
• Five mistakes that make CRM data useless
• DataTags: Capsule’s third tier
• How the main SME CRMs handle tags and custom fields
• TL;DR

Tags vs custom fields: how to choose

The decision rule is straightforward: if you will filter, report, or automate on something, make it a custom field. If you just need to group contacts informally, make it a tag.

Tags work well for things that overlap or evolve over time. A contact can have multiple tags at once (“prospect”, “event:spring-2025”, “service:retained”) and you can add or remove them as the relationship changes. Good tag use cases include: relationship stage (prospect, active client, lapsed), lead source group (Google, LinkedIn, Referral), service area interest, campaign or event attendance, and referral programme membership.

Custom fields work better when you need the value to be consistent and queryable. “Referral source” as a free-text field becomes useless within weeks: half the team types “Referral” and the other half types “word of mouth” or “networking intro”. However, when the custom field is created as a dropdown list, everyone picks from the same list and your filtered reports mean something. Custom fields are the right choice for: contract renewal date or review date, contract value, industry sector, client tier, lead time, team headcount, and any value you want an automation to trigger on.

How to build a CRM tagging system that works

The most common tagging problem is not too few tags. It is too many, too inconsistent, and owned by nobody. Within six months of a CRM going live, a lot of teams have accumulated duplicates from different naming conventions (“Client”, “client”, “CLIENT”, “active client”) and a long tail of one-off email campaign tags that never get cleaned up.

You can avoid tag proliferation by agreeing some rules before anyone touches the CRM. The simplest approach: lowercase, words separated by hyphens. prospect, active-client, source:referral, event:networking-june-2025. If you prefer UPPERCASE for visual clarity, that works too. The key is that everyone uses the same consistent format from day one.

A prefix system groups tags by purpose and makes filtering much faster:

• source: — how the contact arrived (referral, inbound, event, cold-outreach)
• service: — what they are interested in or currently receiving
• event: — a specific campaign, conference, or networking event
• status: — relationship stage (prospect, active, dormant, lapsed)

Aim for five to seven tags per contact as a practical ceiling. More than that and the tags stop describing anything meaningful. Review your tag list every six months: any tag that appears on fewer than five contacts, or that nobody has applied in six months, should be deleted or consolidated to keep your CRM (and connected systems) clean.

Designing custom fields that actually get filled in

The test for any new custom field: will we filter on this, report on it, or trigger an automation from it? If the answer to all three is no, the information belongs in an activity note, not a field. Fields without a clear purpose will be empty on 80% of records within a month, which makes them worse than useless.

Data types matter - use a dropdown whenever there is a fixed list of options, such as: sector, client tier, lead source, service type. Use date fields for anything time-based you want to trigger on: contract renewal date, last review, certificate expiry. Use number for anything you might want to aggregate or compare: deal value, team headcount, approximate annual revenue. Checkboxes work for binary flags: VIP status, GDPR consent captured, NDA signed.

Record level also matters. Most CRMs let you define fields separately for People, Organisations, Opportunities, and Projects. Industry belongs on the Organisation, not the Person. Role and seniority belong on the Person. Deal value belongs on the Opportunity. Putting the wrong data on the wrong record type is one of the most common causes of a messy CRM, and one of the hardest to fix once you have hundreds of records. If you are planning a CRM migration or starting from scratch, the CRM setup and data migration guide covers how to plan your data structure before you import anything.

Here’s a sensible starter set of custom fields for most SMEs:

Practical tag and custom field examples by business type

The right set of tags and fields depends on what you actually need to do with your contacts. Here is how this tends to look across four common SME types.

How tags and fields power segmentation and automation

Tags and custom fields are not just organisational tools. They can often be used as inputs that make segmentation and automation possible.

For email marketing, segments built on tag values or field conditions mean you send the right message to the right list. In Transpond or Mailchimp, a segment of contacts tagged service:retained with a non-empty “Renewal date” field gives you a precise audience for a renewal campaign, without manually assembling a list each time. Our email segmentation guide covers how to build these segments in practice.

For automation via Zapier, a date field is what makes time-based triggers possible. A “Renewal date” custom field can fire a task in your CRM and send a reminder email 30 days before the date, without anyone having to remember. A dropdown field change, moving a contact from “Prospect” to “Active client”, can trigger an onboarding workflow automatically. Our guide to using Zapier with your CRM covers setting these up. You can also combine field-based triggers with conditional email automation to build sequences that branch based on a contact’s field values.

For pipeline reporting, fields on opportunity records are what give your funnel numbers meaning. A “Deal value” field makes your pipeline total accurate. A “Lead source” field tells you which channel is generating your best opportunities and which is generating noise.

We used exactly this kind of structure for a luxury travel operator, building contact organisation around tags for partner type and custom fields for booking visibility. See how the CRM data structure worked in practice for that client.

Five mistakes that make CRM data useless

These are the patterns that turn a well-intentioned tag and custom field CRM setup into a system nobody trusts.

1. Duplicate tags from inconsistent casing. Client, client, and CLIENT are three different tags in most CRMs.

How to fix: Agree a naming format before anyone starts tagging, and audit periodically to merge duplicates.

2. Free-text fields where a dropdown should be. “Referral source” as a text field will have fifteen variations within two months.

How to fix: Any field where a finite set of options exists should be a dropdown list from the start - this constrains data input and keeps it consistent.

3. Over-tagging. A contact with twelve tags is a contact that tells you nothing.

How to fix: Aim for five tags at most per contact, preferably less. Tags that nobody applies actively should be deleted, not left to accumulate.

4. Putting data on the wrong record type. Industry on a Person record means re-entering it every time someone new from the same organisation appears in your system.

How to fix: Industry belongs on the Organisation. Seniority and role belong on the Person. Getting this right early saves a significant amount of rework.

5. Creating fields nobody fills in. This usually happens when fields are added without a clear owner or trigger for when to update them.

How to fix: Every field should have a defined process: “we fill in Renewal date when a contract is signed”, not “fill this in at some point”. Without a process, the field will sit empty and unused.

DataTags: Capsule’s third tier

If you use Capsule CRM, there is a third data structure worth knowing about: DataTags. Most Capsule users are not aware these exist, and the ones who are often underuse them.

A regular tag is a label with no additional data. A global custom field appears on every record of that type, whether it is relevant or not. A DataTag sits between the two: it is a tag that carries its own conditional custom fields, which only appear when the DataTag is applied to a contact or organisation.

The practical benefit is keeping records clean. A global “Renewal date” field clutters every contact in your CRM, including prospects who have never signed a contract. As a field attached to a DataTag called “Active client”, it only appears on records where it actually belongs.

Some practical DataTag examples:

• “Active retainer client” DataTag: fields for which service, start date, monthly retainer value
• “Networking event” DataTag: fields for which event, date attended, follow-up action taken
• “Referred contact” DataTag: fields for referring person, referral date, reward issued

To set these up in Capsule, go to Account Settings, then Tags and DataTags. Any existing tag can be converted to a DataTag and given its own custom fields. For a broader walkthrough of the platform, our Capsule CRM setup guide covers the full configuration sequence.

HubSpot has a partial equivalent: dependent properties, where a field only becomes visible when another property holds a specific value. It requires more configuration than Capsule DataTags but achieves a similar outcome. Pipedrive and Zoho have no direct equivalent at standard plan tiers, with fields applying globally to the record type.

For a real-world example of how a structured tag and custom field setup works in practice, see how we organised contact data and pipeline tracking for a commercial fit-out contractor.

How the main SME CRMs handle tags and custom fields

One note on predefined system fields: most CRMs ship with built-in fields already wired to platform functions. HubSpot has “Lead status” and “Deal stage”. Pipedrive has “Lost reason”. Capsule has pipeline stage and activity types. Before creating a custom field for something, check whether the CRM already tracks it natively. Recreating a field that already exists introduces duplication and potential confusion.

TL;DR

• Tags group contacts by category. Custom fields store structured data you can filter, report, or automate on. Both serve different purposes and work best together.
• Use a dropdown list field for any value where a fixed set of options exists. Never use free text for something you will want to filter on later.
• Agree a tag naming convention before anyone starts tagging.
• Put data on the right record type: industry on the Organisation, role on the Person, deal value on the Opportunity.
• Only create a custom field if you will filter, report, or automate on it. Anything else belongs in an activity note.
• In Capsule CRM, DataTags let you attach conditional fields to a tag so those fields only appear on the records where they are relevant.
• Five to seven tags per contact is a practical ceiling. Review and prune every six months.
• Every field needs a clear process for when and how it gets filled in. A field that is 20% complete is worse than no field at all.