How to Master Keap Tags & Custom Fields for Automated Candidate Management

Keap’s tagging and custom field system is the structural layer that determines whether your recruiting automation runs cleanly or collapses into manual workarounds. Get the architecture right and every follow-up sequence, candidate query, and pipeline report runs itself. Get it wrong and you end up with 200 orphaned tags, a candidate pool you can’t query, and recruiters back to spreadsheets. This guide walks through the exact setup process — taxonomy first, platform second — that powers the broader Keap recruiting automation system.

Before You Start

Before creating a single tag or custom field in Keap, you need three things in place.

• A documented pipeline map. List every stage a candidate moves through from application to offer or rejection. If you can’t name the stages, you can’t tag them consistently.
• A data requirements list. Identify every data point your hiring decisions depend on that Keap’s default contact fields don’t capture — salary range, notice period, assessment score, work arrangement preference. These become your custom fields.
• Automation intent clarity. For every tag category you plan to create, name the automation sequence that tag will trigger. If a tag fires nothing, it should not exist. Time required: two hours of whiteboarding before you open Keap.

Step 1 — Design Your Tag Taxonomy Off-Platform

Your tag taxonomy is the most important decision you will make in this entire process. Build it in a spreadsheet or whiteboard before you touch Keap.

Organize tags into exactly four categories:

• Pipeline Stage: Where the candidate is right now. One tag per candidate at a time. Examples: Stage: Application Received, Stage: Phone Screen Scheduled, Stage: Round 2 Interview, Stage: Offer Extended, Stage: Rejected.
• Skill Set: Primary technical or functional qualifications relevant to your open roles. These are additive — a candidate can carry multiple. Examples: Skill: Python, Skill: HRIS Administration, Skill: Enterprise Sales.
• Availability: How quickly the candidate can start. Examples: Availability: Immediate, Availability: 30 Days, Availability: 60-90 Days, Availability: Passive — Not Looking.
• Disposition: The reason a candidate’s forward movement is paused or ended. Examples: Hold: Salary Mismatch, Hold: Role Filled — Retain for Future, Disqualified: Requirements Gap.

Name every tag with its category prefix. Stage: Round 2 Interview is immediately parseable. Round2 is not. Naming discipline now prevents tag debt later.

Before moving to Step 2, verify: every Stage tag has a named automation sequence it triggers. Every Disposition tag routes the candidate to a defined nurture or close-out campaign. If you cannot name the downstream automation, remove the tag from your taxonomy.

Step 2 — Build Your Custom Field Library

Custom fields capture the structured data your automation logic needs to make decisions that tags cannot encode. Open Keap’s contact custom field settings and build these six fields before anything else.

The Core Six Custom Fields for Recruiting

Add role-specific fields only after these six are in place and actively used. Premature field proliferation creates the same debt problem as premature tag creation. Based on our work with recruiting teams, the most common mistake at this stage is building fields for data you hope to collect someday rather than data your current automations actually consume.

Step 3 — Create Your Tags Inside Keap

With your taxonomy documented and approved, open Keap’s tag management area and build your tag library using the exact names from your taxonomy document. Do not deviate from the naming convention during this step — consistency here is what makes bulk search and automation targeting reliable later.

Create tag categories in Keap that mirror your four taxonomy categories (Pipeline Stage, Skill Set, Availability, Disposition). Keap’s tag category grouping makes your library navigable as it grows.

Practical notes from implementation:

• Build all Stage tags before building Skill or Availability tags — Stage tags connect to your primary automation sequences and should be tested first.
• If your team has multiple recruiters, hold a 30-minute sync to walk through the taxonomy before anyone applies tags to live records. Inconsistent application of even a well-designed taxonomy produces bad data.
• Do not import existing tags from a prior system without auditing them first. Legacy tag names rarely map cleanly to a structured taxonomy.

Step 4 — Wire Tags to Automation Sequences in the Campaign Builder

Tags without automation are data entry. This step is where the system pays off.

In Keap’s campaign builder, create one sequence per Stage tag. Each sequence follows the same structural pattern:

1. Tag applied → sequence starts. The trigger is the Stage tag application.
2. Immediate action fires. This is typically an email to the candidate (confirmation, prep materials, or status update) and an internal task or notification to the recruiter.
3. Custom field updated. The Current Stage Date field is updated to today’s date, starting your time-in-stage clock.
4. Trigger tag removed. At sequence start or on day one, the tag that launched the sequence is removed. The candidate’s permanent taxonomy tags (Skill, Availability) remain. Only the transient trigger tag is cleared.
5. Decision node evaluates custom fields. For sequences that require branching (e.g., salary range routing), insert a decision diamond that reads the relevant custom field and routes accordingly.

For candidate follow-up campaigns, the tag-trigger-remove loop is non-negotiable. Teams that skip the removal step end up with candidates re-entering sequences on their next pipeline move and receiving duplicate outreach — one of the fastest ways to damage candidate experience.

The healthcare staffing team documented in our 90% interview show-up rate case study ran this exact architecture: one tag per pipeline transition, each tag triggering a short confirmation and reminder sequence, trigger tag removed on day one. Interview no-shows dropped from industry average to near zero within 60 days of deployment.

Step 5 — Configure Bulk Tagging for Candidate Imports

New candidate records enter Keap through three paths: manual entry, web form submission, and batch import. Each path needs a defined tagging protocol or your taxonomy degrades immediately.

Manual Entry

Require recruiters to apply Stage, Availability, and at least one Skill tag at the point of record creation. Build a Keap internal form template with these tag fields pre-listed as a checklist. Manual records without taxonomy tags should not exit the creation step.

Web Form Submission

Configure Keap web forms to apply tags automatically on submission. A candidate who fills out a job interest form should automatically receive Stage: Application Received and the Availability tag that matches their form response. Map form dropdown options directly to tag applications inside the form builder — no manual tag application required after submission.

Batch Import

Add a dedicated import column to your CSV named “Import Batch Tag” and apply a single batch identifier tag during import (e.g., Source: Job Board Import Q1 2026). Use that batch tag to trigger a post-import segmentation sequence that reads custom fields already populated in the CSV and applies the correct taxonomy tags automatically. Never tag large imports individually — it introduces inconsistency and consumes hours that automation should own.

Step 6 — Build Your Talent Pool Search Protocol

A well-tagged candidate pool is only valuable if your team knows how to query it. The payoff for all the taxonomy work above is the ability to surface qualified candidates in seconds when a role opens — a direct counter to the sourcing delays that SHRM research associates with extended time-to-fill costs.

In Keap’s contact search, build and save searches using tag combinations. Examples:

• Immediate availability, Python skill: Filter for Skill: Python + Availability: Immediate. This search, saved and bookmarked, gives any recruiter a live list the moment a Python role opens.
• On-hold candidates for revisit: Filter for any Hold: tag. Run this search monthly. Apply a re-engagement sequence tag to candidates whose hold reason may have changed.
• Pipeline velocity check: Filter for any Stage tag + Current Stage Date older than your target time-in-stage threshold. These are stalled candidates who need a manual recruiter touch.

Save these searches by name inside Keap and document them in a team playbook. Turnover in a recruiting team should not reset institutional knowledge of how to query the talent pool. The talent pool segmentation guide covers advanced search patterns beyond these basics.

Step 7 — Schedule Quarterly Tag Audits

Tag debt accumulates silently. A system with 20 well-maintained tags outperforms one with 200 that have drifted from their original intent. Build a standing quarterly audit into your team calendar.

The audit checklist:

• Export the full tag list from Keap’s tag management area.
• Flag any tag with fewer than five contacts currently assigned — these are candidates for consolidation or deletion.
• Identify tags that have no corresponding automation sequence — document why they exist or delete them.
• Check for naming inconsistencies (e.g., Stage: Round 2 vs. Round2Interview vs. 2nd Round). Consolidate to the canonical name.
• Review custom field completion rates. If fewer than 70% of active candidate records have a core field populated, the data collection process (form, import, manual entry) needs fixing before the automation logic built on that field can be trusted.

This audit takes 90 minutes for a team with a well-maintained system and up to half a day for a system that has accumulated debt. Do it quarterly and it stays at 90 minutes. Skip two quarters and you are rebuilding.

How to Know It Worked

A properly functioning tag-and-field system produces four measurable signals within 30-60 days of deployment:

1. Zero orphaned tags on audit. Every tag in your library has an associated automation and active contacts assigned.
2. Pipeline stage queries return accurate results. A search for Stage: Round 2 Interview returns only candidates currently in that stage — not candidates who were there two months ago and advanced.
3. Time-in-stage data is populated. The Current Stage Date field is consistently populated for active candidates, enabling velocity reporting without manual extraction.
4. Recruiter triage time drops. When a role opens, the team can produce a shortlist from existing talent pool searches in under 10 minutes. If it still takes hours, the taxonomy or search protocol needs refinement.

Common Mistakes and How to Fix Them

Mistake: Creating tags inside Keap before designing the taxonomy

Fix: Freeze tag creation in Keap until the taxonomy document is complete and reviewed by everyone who will apply tags. Retroactively restructuring a live tag library mid-recruiting cycle is expensive and error-prone.

Mistake: Not removing trigger tags after sequences fire

Fix: Add a “Remove tag: [trigger tag name]” action as the first step inside every sequence. Make this a non-negotiable template standard so no sequence can be published without it.

Mistake: Building custom fields for aspirational data you don’t currently collect

Fix: Audit your data collection touchpoints (application forms, recruiter intake notes, ATS imports) before creating a field. If there is no current collection mechanism for a data point, the field will sit empty and the automation logic built on it will never fire correctly.

Mistake: Treating Keap as a standalone ATS replacement

Fix: Use Keap for what it does best — relationship management and automated communication — and pair it with a purpose-built ATS for compliance tracking and requisition management. The Keap versus a traditional ATS breakdown covers the right boundaries between systems.

Mistake: Skipping the quarterly audit

Fix: Put it on the calendar now, before you finish deployment. Tag debt that accumulates for 12 months requires a remediation project, not an audit. Gartner’s research on data quality consistently shows that prevention costs a fraction of remediation — the same principle applies to tag library maintenance.

Practical Implications for GDPR and Data Retention

Custom fields that store candidate data carry compliance obligations. Before you build salary range or assessment score fields, confirm your data retention policy is documented and that Keap’s automation can enforce it. A tag-triggered sequence on an annual schedule that flags candidate records past your retention threshold for review or deletion is a minimum control. For full guidance on structuring Keap candidate data within GDPR requirements, see the dedicated GDPR compliance for candidate data in Keap satellite.

The tag-and-field architecture described in this guide is the structural foundation for everything else in your Keap recruiting system — the automated candidate feedback sequences, the passive talent nurture campaigns, and the pipeline reporting that leadership needs to make resourcing decisions. Build it deliberately, maintain it consistently, and the compounding returns on recruiter time and candidate quality show up within a single hiring cycle.