Tags and custom fields are what make Lime Go your CRM, not a generic system. Without them, you have a contact register. With them, you have a tool for working data-driven at every level.
Most people who start using Lime Go don't fully understand the difference between the two. This guide clears that up and shows how to build a structure that actually gets used.
The difference between tags and custom fields
Custom fields are information fields. They're for storing data — a date, a number, a yes/no, a text. They appear on the record and can be filled in when creating or editing it.
Examples: "Contract start: 2024-09-01", "Received training: Yes", "Number of licenses: 25"
Tags are categories. They're for filtering. You apply a tag to a company, a deal, or a person so you can quickly find everyone with that category.
Examples: "Priority customer", "Using a competitor", "Machinery", "Check back after summer"
A simple rule of thumb: if you want to search for it and find everyone with the same thing, use a tag. If you want to see a specific value on an individual record, use a custom field.
Three levels: and why it matters
Tags and custom fields exist at three separate levels in Lime Go:
- Deals and projects — on the green deal record
- Companies — on the blue company record
- People — on the contact record
It's important to keep these separate. Deal-level tags appear and can be filtered in the pipeline. Company-level tags appear and can be filtered in the Find view and the customer view. Person-level tags are used when you work with contact persons and newsletters.
Never apply a tag at the wrong level — it creates confusion and filters that don't work the way you intended.
Tags at the company level
This is where the most fundamental segmentation happens. Company tags are used to describe what companies are and which segment they belong to.
Think in three categories:
Relationship-status tags complement the built-in relationship filter.
The relationship filter tells you whether a company is a customer, a prospect, or neither. Tags tell you why and how:
- Priority customer
- Contract ended
- Win-back
- Strategic partner
Segmentation tags — what the company does or is
- Machinery
- Education
- Consulting solution
- Public sector
Working-status tags — where you are in the relationship
- Using a competitor
- Check back after summer
- Met at trade show Q3
- Not ready now
The third category is often the most valuable for active outreach because it gives you a clear next step.
Practical rule: always combine relationship filter + tag when filtering. "Relationship: Has contacted + Tag: Check back after summer" is a much more powerful filter than either on its own.
Tags at the deal and project level
Deal tags are for segmenting your pipeline. Use them to answer the question: what is this deal about?
Good categories:
Product segment or service type
What are you selling in this deal? Machinery, service, training, licenses, fiber. Choose whatever's natural for your portfolio.
Campaigns
Did the deal come from a specific campaign? Tag it with the campaign name. Then afterward you can filter the pipeline and sales dashboard by "October trade show" and see exactly how much that campaign generated.
Why deal tags enable data-driven sales work:
In the pipeline you can filter by tags and immediately see "all deals in the training segment expected to close this month". In the sales dashboard you'll then see a pie chart of which segments generate the most sales. That's the information you need to prioritize correctly.
Tags at the person level
Person tags are used in two contexts: to filter for contact persons, and to manage email consent for newsletters.
Common person tags:
Role-based tags
- Decision-maker
- Contract owner
- Marketing manager
- Technical contact
Newsletter and consent
- Newsletter subscriber
- CEO report
Role-based tags are especially useful in combined filters: "All contact persons tagged Decision-maker at companies tagged Priority customer with relationship Is customer" gives you a ready-made list to call ahead of an important offer.
Custom fields in practice
On deals and projects
Keep it short and relevant. Only choose fields you'll actually fill in on every deal:
- Checkbox: "Qualified budget" — a quick way to see if the deal is serious
- Date: "Desired decision date" — makes it easy to filter for deals with a decision this month
- Multi-select: "Number for training" — helps you value the deal correctly
- Text or link: "Quote URL" — for quick access without leaving Lime Go
On company records
Company fields are for customer-related information that doesn't change per deal:
- "Contract start" — the date the customer relationship began
- "Received training" — a checkbox ticked when onboarding is complete
- "Contract value ARR" — if you want it on the customer record
On contact records
Contact-record fields are rare but sometimes necessary:
- "Alternative email address" — if the person has multiple addresses
- "LinkedIn profile" — for easy access
Step by step: design your tag structure
Before you create tags in settings, do this:
1. Write down your most common questions about customers and deals:
- Which customers are most strategically important to us?
- Which prospects have we talked to but not won?
- Which deals in the pipeline came from our latest trade show?
- Which customers buy product X but not product Y?
Each question points to a tag or filter need.
2. Decide which level each tag belongs at:
Is it about the company itself → company tag. Is it about this specific deal → deal tag. Is it about a contact person → person tag.
3. Keep the number of tags manageable:
10–15 tags per level is a good benchmark. More than that and team members pick the wrong one or skip tagging altogether. Start with the most important ones and add more as needed.
4. Document the tag structure internally:
Write down what each tag means and when it should be used. Without this, different people start using the same tags in different ways, and the filters stop working the way you intended.
Common mistakes to avoid
Mixing up tags and the relationship filter. Don't create a tag called "Customer" — there's already a relationship filter for that. Tags should complement relationship status, not duplicate it.
Overly granular tags. "Customer since 2019" as a tag is unnecessary — there's a contract-start field for that. Tags should be broad categories, not unique values.
Tags without an owner. If no one is responsible for keeping the tags up to date, they stop reflecting reality. Decide who's responsible for tagging new companies and deals.
Tags that are never used in filters. If you never filter by a tag, there's no reason to have it. Review the tag structure once a year and remove what isn't used.
Next step
Once your tag and field structure is in place, it's time to use it actively in prospecting. See the guide Prospect new customers with filters and lists for how to combine relationship filters and tags to build accurate calling lists.