Tags in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers what tags are, the three ways to apply them (manual, workflow, form), how the Tag Added trigger connects automations, how tags power Smart List segmentation, how to design a maintainable tag naming system, and the difference between tags and pipeline stages.

Reading time: about 6 minutes.

What Are Tags in HighLevel?

Tags in HighLevel are text labels applied to contact records. A contact can have multiple tags simultaneously.

Tags describe attributes, statuses, behaviors, or categories that are relevant to how the contact should be treated by the system.

Examples: “New Lead” for a contact who just submitted a form. “Appointment Booked” for a contact who has a scheduled appointment.

“Review Left” for a contact who has left a Google review. “VIP Customer” for a contact who has made multiple purchases.

“Do Not Call” for a contact who requested no phone contact.

Tags are not just labels – they are operational levers. They trigger workflows, define Smart List membership, control automation flow, and enable bulk actions on segmented groups of contacts.

Three Ways Tags Are Applied

Tags are applied to contacts through three mechanisms, each appropriate for different contexts.

Manual application from the contact record is the most direct method. Open the contact, find the tags field, type or select the tag to apply.

Manual tags are used for one-off situations – flagging a specific contact for a specific reason, applying a tag during a sales conversation, or correcting a contact’s tag state.

Automatic application via Workflow Builder is the most scalable method. An Add Tag action in a workflow applies the tag to every contact that reaches that step.

This is how most tags are applied in a well-built HighLevel account – automatically as contacts move through lead capture, appointment booking, job completion, and other process milestones.

Form and survey submissions can apply tags automatically when a contact submits a specific form. In the form settings, configure a tag to apply on submission.

Every contact who submits that form receives the tag – no manual action required. This is common for lead magnet forms, consultation request forms, and intake surveys where the form submission itself carries categorization meaning.

The Tag Added Trigger

The Tag Added trigger in Workflow Builder is one of the most powerful features in HighLevel because it enables indirect workflow connections. Any workflow can fire when a specific tag is applied to a contact – regardless of what process applied the tag.

Consider a review request automation. Rather than building the review request directly into the job completion workflow, a cleaner approach: the job completion workflow adds a tag “Job Completed.” A separate review request workflow is triggered by the “Job Completed” tag.

The two workflows are decoupled – the job completion workflow handles job tracking; the review request workflow handles reputation management. Each is maintained independently.

Adding or removing the review request automation does not require touching the job completion workflow.

This decoupling through tags is the architectural principle that makes large HighLevel setups maintainable. Complex workflows that try to handle everything in a single sequence become difficult to modify.

Tag-triggered workflows that each handle one specific function are easier to test, easier to modify, and easier to disable without affecting other processes.

Tags and Smart List Segmentation

Smart Lists are dynamic contact lists built on filters – and tag filters are the most commonly used. A Smart List with the filter “has tag: Active Customer” automatically includes every contact with that tag.

Add the tag to a new contact and they immediately appear in the Smart List. Remove the tag and they immediately disappear.

Tag-based Smart Lists are the segmentation layer for campaigns. A campaign going to “Active Customers” uses a Smart List filtered by the “Active Customer” tag.

As new contacts earn that tag through purchases or workflows, they automatically become eligible for future sends to that Smart List. The campaign audience stays current without manual maintenance.

Exclusion filtering is equally important. A Smart List with the filter “does not have tag: Review Left” includes all contacts who have not yet left a review.

A review request campaign sent to that Smart List reaches exactly the right audience – no risk of requesting a review from someone who already left one.

Tags as Workflow Conditions

Tags are used as conditions in Workflow Builder’s If/Else branching logic. An If/Else condition can check whether a contact has a specific tag at the time of evaluation and branch the workflow accordingly.

Practical examples: “If contact has tag: Previous Customer, send the returning customer offer; otherwise send the new customer offer.” “If contact has tag: VIP, route to the dedicated VIP pipeline; otherwise route to the standard pipeline.” “If contact does not have tag: Appointment Booked, send the follow-up; otherwise skip.”

Tags as conditions make workflows context-aware. The same workflow can handle multiple contact types differently based on their tags – without requiring separate parallel workflows for each type.

Tags vs. Pipeline Stages

Both tags and pipeline stages categorize contacts, but they serve different roles. Pipeline stages represent position in a linear sales or service process – a contact is in one stage at a time and moves through stages sequentially.

Tags are freeform and non-linear – a contact can have many tags simultaneously and there is no inherent ordering.

Use pipeline stages for tracking where a contact is in the sales process: New Lead, Estimate Sent, Proposal Accepted, Job Scheduled, Job Completed, Invoice Paid. Use tags for everything else: behavioral flags (Review Requested, Review Left), status indicators (VIP Customer, Do Not Call), source tracking (Facebook Lead, Google Organic, Referral), and process completion markers (Onboarded, Training Complete).

Tags and pipeline stages complement each other. A contact in the “Job Completed” pipeline stage might also have tags “VIP Customer,” “Review Requested,” and “Email Campaign Active.” The stage tracks process position; the tags track everything else about the contact.

Designing a Tag Naming Convention

A tag naming convention is the difference between a tag library that is usable at scale and one that devolves into chaos. Without a convention, different team members create slightly different versions of the same tag (“New Lead,” “new lead,” “NewLead,” “Lead – New”) that functionally fragment what should be a unified segment.

A practical convention for most businesses: use sentence case, be descriptive and specific, group related tags with a prefix. For example: “Lead: New,” “Lead: Contacted,” “Customer: Active,” “Customer: Past,” “Review: Requested,” “Review: Left.” The prefix makes the purpose immediately clear and groups related tags together alphabetically in lists.

Tags that no one remembers the purpose of – created in the moment for a specific one-off need – accumulate over time and pollute the tag library. A lightweight documentation practice (even just a simple note listing each tag and its purpose) prevents this accumulation by making it clear before creating a new tag whether a similar tag already exists.

Common Tags for Every Sub-Account

Most HighLevel sub-accounts benefit from a core set of standard tags. The exact list varies by business type, but a useful baseline: a new lead tag (applied when a contact is first created or submits a form), an active customer tag (applied when a sale closes or service begins), a past customer tag (applied when service ends), a review requested tag, a review left tag, a do not contact tag (applied when a contact requests no further communication), and a VIP or priority tag (for high-value contacts who warrant different treatment).

Beyond the core set, process-specific tags are added as the business’s automation matures. Appointment booked, job completed, invoice paid, referral source tags, and campaign enrollment tags are all common additions.

The key is building them intentionally rather than reactively – each new tag should have a clear purpose and a clear workflow that uses it.

What Can You Do With It?

• Automatically categorize contacts as they move through processes: Workflow Add Tag actions apply the right category to each contact at the right stage – no manual sorting required. Every contact entering the system gets the appropriate tags as they progress.
• Trigger specific automations when contacts reach key milestones: The Tag Added trigger fires targeted workflows precisely when a contact reaches a milestone – job completion, appointment booking, purchase. One tag links many potential downstream automations.
• Build dynamic Smart Lists that stay current automatically: Tag-based Smart Lists update in real time as contacts gain or lose tags. Campaign audiences are always accurate without manual list management.
• Control workflow logic based on contact context: If/Else conditions using tags make workflows context-aware – the same automation behaves differently for VIP customers, previous customers, and new leads based on their tags.
• Exclude contacts from automations they should not receive: Tags like “Review Left” or “Appointment Booked” as exclusion conditions in workflows prevent contacts from receiving communications that are no longer relevant to them.

Key Definitions

Use Cases by Industry

Home Services – Process Milestone Tracking

A plumbing company uses tags to track where each contact is in their service process. When a form is submitted: “Lead: New” tag applied.

When the first call is made: “Lead: Contacted” tag applied. When an appointment is booked: “Appointment: Booked” tag applied, “Lead: New” tag removed.

When the job is completed: “Customer: Active” tag applied, “Job: Completed” tag applied (which triggers the review request workflow).

At any point, the owner can look at a contact’s tags and understand exactly where they are in the process. A Smart List filtered by “has tag: Lead: New and does not have tag: Lead: Contacted” shows all leads who have not yet been called – a daily action list for the owner or the sales team.

Result: Tags provide both a process tracking system and an automation trigger mechanism. The owner has real-time visibility into every lead’s status. The automations fire precisely when needed based on the tags that mark each milestone.

Marketing Agency – Multi-Client Tag Architecture

An agency builds a standard tag taxonomy that is applied consistently across all client sub-accounts via the snapshot template. Every client sub-account starts with the same core tags (Lead: New, Customer: Active, Review: Left, Appointment: Booked, etc.) and the same workflows that use them.

When managing or troubleshooting any client account, the agency team can immediately understand the contact’s status from the tags without learning a different tagging system per client. Consistency across clients reduces the cognitive overhead of managing multiple accounts simultaneously.

Result: Standardized tagging across client accounts makes the agency’s portfolio manageable at scale. A team member who knows the standard tag system can work in any client account without needing to learn that client’s specific setup from scratch.

Real Estate – Lead Source Tracking

A real estate agent tags every new contact with their lead source: “Source: Zillow,” “Source: Google,” “Source: Referral,” “Source: Open House.” Each source tag is applied automatically – the Zillow lead capture webhook applies the Zillow tag, the Google Ads landing form applies the Google tag, the referral form applies the Referral tag.

A Smart List filtered by “has tag: Source: Google” shows all Google-sourced leads. The agent can run a targeted follow-up campaign specifically to Google-sourced leads, or pull a report on how many leads came from each source over the past month – without any manual sorting or data entry.

Result: Lead source attribution is automatic and persistent. The agent knows where every contact came from, can segment by source for targeted communication, and can report on which sources are generating leads – all from the tag data that accumulates automatically as leads enter the system.

Who Is This For?

How to Set Up and Use Tags

Step 1: Design the naming convention

Decide on a naming approach before creating tags. Consistent naming (sentence case, category prefixes) makes the library manageable as it grows.

Step 2: Create core tags

Settings, then Tags. Create the essential tags: lead status (New, Contacted), customer status (Active, Past), process flags (Appointment Booked, Job Completed, Review Requested, Review Left), and contact control tags (Do Not Contact, VIP).

Step 3: Add tag actions to existing workflows

In each key Workflow Builder sequence, add Add Tag actions at the appropriate milestones. Apply the correct tag when a contact books an appointment, when a job is marked complete, when an invoice is paid.

Step 4: Build tag-triggered workflows

Create a new workflow with the Tag Added trigger for each milestone that should initiate a separate automation sequence. The review request workflow triggered by “Job Completed” is the most common example.

Step 5: Create Smart Lists based on tags

Build the standard Smart Lists needed for campaigns – “Active Customers,” “New Leads Not Yet Contacted,” “Contacts Without Review.” Set each Smart List’s filter using the appropriate tag conditions.

Step 6: Add tag conditions to workflows

In workflows where contact context should affect the path, add If/Else branches checking for relevant tags. Route VIP contacts differently, skip steps for contacts who have already completed the relevant action.

Step 7: Apply tags to existing contacts

For contacts already in the system, apply the appropriate tags via bulk action or individual record updates. A well-tagged existing database produces better segmentation from day one of using the new tag structure.

Step 8: Document the tag system

Create a simple reference document listing each tag, its purpose, and what applies or removes it. Share with the team to ensure consistent usage.

Step 9: Audit periodically

Every few months, review the tag library in Settings. Identify and consolidate duplicate or unused tags.

Keep the library clean and intentional.

How Does It Connect to HighLevel?

• Tag-Based Automation: Tag-Based Automation is the dedicated feature page for the Tag Added trigger and tag-driven workflow architecture. Tags and tag-based automation are deeply intertwined – tags are the labels; tag-based automation is what makes those labels do work.
• Smart Lists: Smart Lists use tag filters as their primary segmentation mechanism. A Smart List without tags is limited to demographic or activity filters. Tag-based Smart Lists are dynamic, real-time, and the standard approach for building campaign audiences in HighLevel.
• Workflow Builder: Add Tag, Remove Tag, and Tag Added trigger are core Workflow Builder components. Understanding tags is inseparable from understanding how to build sophisticated automation in HighLevel.
• Contact Management: Tags are stored and displayed on contact records. The contact’s tag state is part of the contact’s profile – visible at a glance when reviewing a contact’s information.
• Email Campaign Automation: Email campaigns use Smart Lists as their audience – and Smart Lists are often tag-filtered. The tag applied to a contact determines which campaign audiences they appear in and which campaigns they receive.

Common Questions

What are Tags in HighLevel?

Text labels applied to contacts for categorization, segmentation, workflow triggering, and automation control. Contacts can have multiple tags simultaneously.

Where do I manage Tags in HighLevel?

Settings, then Tags for the global tag library. Tags are also applied and visible on individual contact records and throughout Workflow Builder.

How do Tags trigger workflows in HighLevel?

The Tag Added trigger in Workflow Builder fires a workflow whenever the specified tag is applied to a contact – regardless of what process applied it. The primary mechanism for decoupling automations.

Can Tags be added and removed automatically in HighLevel workflows?

Yes. Add Tag and Remove Tag are standard Workflow Builder actions. Apply them at any point in a workflow sequence to update contact status as they progress through processes.

How are Tags used for contact segmentation in HighLevel?

Smart List filters use “has tag” and “does not have tag” conditions. Smart Lists with tag filters are real-time, dynamic audience segments that update automatically as tags are applied or removed.

What is the difference between Tags and Pipeline Stages in HighLevel?

Pipeline stages track linear sales process position (one stage at a time). Tags are multi-dimensional, non-linear labels – a contact can have many tags simultaneously representing attributes, behaviors, and statuses that pipeline stages cannot capture.

To Wrap It Up

Tags are arguably the most important infrastructure feature in HighLevel that users rarely think about explicitly. They are the connective tissue between automations, the mechanism for Smart List segmentation, and the system that makes the platform’s automation capabilities genuinely scalable.

A HighLevel account without a thoughtful tag system relies on ad-hoc manual sorting, has automations that cannot be easily connected to each other, and ends up with Smart Lists that require constant manual maintenance. An account with a well-designed tag system has automations that fire exactly when they should, Smart Lists that stay current automatically, and a clear picture of every contact’s status at any point in time.

The investment in designing the tag system upfront – before building workflows and campaigns – pays off in operational clarity and reduced maintenance complexity as the account grows. Tags designed reactively accumulate debt.

Tags designed proactively create leverage.

1. Decide on a naming convention before creating any tags
2. Create the core tag set in Settings, then Tags
3. Add Add Tag and Remove Tag actions to all key workflow milestones
4. Build tag-triggered workflows for each process that should activate on a milestone tag
5. Create Smart Lists filtered by the most important tags
6. Use tag conditions in If/Else branches to make workflows context-aware
7. Document the tag system and share it with the team
8. Audit the tag library quarterly and clean up unused or duplicate tags

Design the tag system before building any automations – not after. Retrofitting a tag architecture onto a collection of existing workflows is significantly harder than building both together.

Tags that are designed to connect specific workflows from the start are used consistently. Tags that are added as afterthoughts to existing workflows are used inconsistently and often duplicated under slightly different names by different team members who did not know the tag already existed.