How to Set Up Keap Custom Fields and Dynamic Tags for Recruiting: A Step-by-Step Guide

Generic CRM databases treat every contact the same. Recruiting doesn’t work that way. A candidate has a notice period, a preferred work arrangement, a certification stack, a compensation expectation, and a dozen other structured attributes that determine whether they belong on a shortlist or in a passive nurture sequence. The moment you try to track those attributes in free-text notes or informal spreadsheets, your segmentation collapses — and so does your time-to-hire.

This guide walks you through the exact process for building a Keap custom field and dynamic tagging architecture purpose-built for recruiting. It is the foundation layer that the dynamic tagging architecture in Keap for HR and recruiting covered in our parent pillar depends on. Get this right first. Everything downstream — automated nurture sequences, AI-assisted scoring, pipeline reporting — operates on the data structure you build here.

Before You Start

This process requires direct access to Keap admin settings and the automation builder. Budget two to four hours for the audit and architecture design phase before you create a single field or tag in the live system. Mistakes made at the field and tag level cascade into every automation that references them.

What you need before starting:

• Keap admin credentials with full contact and automation permissions
• A current export or documented list of every data point your team collects during a candidate screening
• A list of every active automation currently running in your Keap account (to identify dependencies before you change anything)
• At least one test contact record to validate automation logic without touching live candidates
• A naming convention decision made in advance — see Step 3

Risks to flag before you proceed:

• Changing an existing custom field’s data type will orphan data already stored in that field and break automations that reference it.
• Keap enforces limits on the number of custom fields per account tier — verify your limit before designing a large field set.
• Tags cannot be merged natively in Keap; a poorly designed tag taxonomy must be manually corrected contact by contact or via automation workarounds.

Parseur’s Manual Data Entry Report estimates that manual data handling costs organizations an average of $28,500 per employee annually when compounded across rework, errors, and retrieval time. The architecture you build here directly reduces that burden by making structured data capture automatic rather than manual.

Step 1 — Audit Your Candidate Data Requirements

List every data point your team consults when making a hiring, screening, or placement decision. Do not start with what Keap offers — start with what your recruiters actually use.

Collect this audit by interviewing the recruiters and HR professionals who make daily decisions. Ask one question: “What information do you need to know about a candidate before you decide whether to advance them or not?” Document every answer. Then apply a filter: if a data point is never consulted in a real decision, remove it from the list.

Common recruiting data points that translate well to Keap custom fields:

• Years of relevant experience (number field)
• Primary technical skills (multi-select dropdown)
• Certifications held (multi-select dropdown)
• Preferred work arrangement: onsite, hybrid, remote (radio select)
• Availability / notice period in weeks (number field)
• Desired compensation range — floor and ceiling (two number fields)
• Visa sponsorship required (yes/no)
• Geographic region preference (dropdown)
• Placement client suitability tags (for staffing firms — multi-select)
• Initial screen score or rating (number or dropdown)
• Source channel (dropdown: referral, job board, inbound, outreach)
• Last active engagement date (date field — populated by automation, not manually)

APQC benchmarking on HR process efficiency consistently shows that teams with structured, queryable candidate data make placement decisions measurably faster than teams relying on unstructured notes. The audit step is where you decide which data becomes queryable and which stays buried in notes fields.

Target outcome: a finalized list of 15–30 custom fields, each with a defined data type and a clear business question it answers.

Step 2 — Build Your Custom Field Architecture in Keap

With your audited field list in hand, create each field in Keap using the correct data type. Field type determines what automation logic you can build on top of it — this decision is not cosmetic.

Field type guide for recruiting use cases:

• Text (single line): Use only for fields that genuinely require open input — a previous employer name, a referral source contact. Do not use text for anything you intend to filter or segment on.
• Dropdown (single select): Use for mutually exclusive attributes — work arrangement preference, visa sponsorship status, hiring stage. Automation triggers can evaluate “equals” conditions on dropdown values.
• Multi-select / checkbox list: Use for attributes a candidate may hold multiple values of — technical skills, certifications, role types. Automation can trigger on “contains” conditions.
• Number: Use for years of experience, compensation values, availability in weeks. Enables greater-than/less-than conditions in automation rules.
• Date: Use for availability date, last screening date, offer expiration. Enables date-based automation sequences.
• Yes/No (radio): Use for binary attributes — visa sponsorship required, open to relocation, active job seeker. Clean binary fields fire the most reliable automation triggers.

To create a custom field in Keap: navigate to CRM → Contacts → Custom Fields, select the appropriate field type, name the field using your chosen naming convention (covered in Step 3), and save. Group related fields into labeled sections for recruiter usability.

What we’ve seen go wrong: Teams that create skill fields as free-text instead of multi-select cannot build automation filters on them. A text field containing “Python, JavaScript, React” is invisible to Keap’s automation engine unless the exact string matches. A multi-select field with “Python” as one option fires reliably every time. Make the right type choice now — changing it later requires a full field migration.

Once all fields are created, populate them for five to ten real candidate records manually. This validates that the field options are complete and that your team can input data consistently — before automation depends on those values.

Step 3 — Define Your Tag Taxonomy Before Creating Any Tags

Tags must be designed on paper before they exist in the system. A tag created in isolation becomes an orphan within weeks. A tag built within a documented taxonomy remains useful for years.

Gartner research on CRM data governance identifies undisciplined tag and label growth as a leading cause of CRM adoption failure in mid-market organizations. Keap databases are not immune — we have audited accounts with over 600 tags where fewer than 100 could be reliably interpreted by the team that created them.

The prefix-based naming convention for recruiting tags:

Structure every tag as: [CATEGORY] | [ATTRIBUTE OR STAGE] | [VALUE]

• SKILL | Python | Advanced
• SKILL | Project Management | PMP Certified
• STAGE | Interview | Phone Screen Completed
• STAGE | Offer | Extended
• ENGAGE | Email | Opened Last 30 Days
• ENGAGE | Ghosted | No Response 14 Days
• SOURCE | Inbound | Job Board
• SOURCE | Referral | Employee
• STATUS | Active Candidate
• STATUS | Placed | Do Not Solicit

Document every tag in a master taxonomy spreadsheet before creating it in Keap. Include: tag name, category prefix, the automation or manual action that applies it, the automation or condition that removes it, and the date created. This document becomes your system of record.

For the complete naming framework and governance rules, see our guide on Keap tag naming and organization best practices. For the specific tags most recruiting operations need at minimum, see 9 essential Keap tags every HR team needs.

Governance rule before you proceed: No recruiter creates a tag manually in Keap without first adding it to the taxonomy document. Enforce this from day one. A taxonomy that allows ad-hoc tag creation without documentation degrades within 60 days.

Step 4 — Wire Automation Triggers to Field-Value Conditions

This step is where custom fields become dynamic tags. The goal is to remove manual tag application from every recruiter workflow. Tags should apply and remove automatically based on field-value changes, form submissions, link clicks, and engagement signals — not because a recruiter remembered to click a checkbox.

McKinsey research on workforce automation found that HR and recruiting functions contain a high share of repetitive, rule-based tasks that are prime candidates for automation — and data classification is explicitly named among them. Manually applying tags is exactly that kind of task.

How to build a field-to-tag automation in Keap:

1. Navigate to Automation → Campaign Builder (or the legacy Legacy Automation depending on your Keap version).
2. Create a new automation with the trigger: Contact field value changes. Select the specific custom field you want to monitor.
3. Add a condition: Field value equals [specific dropdown option] or Field contains [multi-select value].
4. Add the action: Apply tag → [the corresponding tag from your taxonomy].
5. Add a second branch for the inverse condition: if the field value changes away from the trigger value, Remove tag. Tags that are never removed create false positives in segmentation over time.
6. Name the automation using the same naming convention as your tags so dependencies are traceable.

Practical automation examples for recruiting:

• When Preferred Work Arrangement field = “Remote Only” → Apply tag PREF | Remote | Only
• When Visa Sponsorship Required field = “Yes” → Apply tag STATUS | Visa Required
• When Years of Experience field is greater than or equal to 5 → Apply tag TIER | Senior | 5+ Years
• When Availability Weeks field = 0 → Apply tag AVAIL | Immediate Start
• When candidate opens a specific email sequence → Apply tag ENGAGE | Email | Active; when 14 days pass with no open → Remove tag, apply ENGAGE | Ghosted | 14 Day

For building your first complete workflow end-to-end, see the guide on building your first Keap dynamic tagging workflow. For the scoring logic that runs on top of these tags, see candidate lead scoring with Keap dynamic tagging.

Asana’s Anatomy of Work research found that knowledge workers spend a significant share of their week on work about work — status updates, manual data entry, and tracking that adds no strategic value. Automating tag application from field changes directly reclaims that time for sourcing and relationship work.

Build one automation per logical rule. Avoid combining multiple field conditions into a single automation — it makes debugging nearly impossible when a tag misfires.

Step 5 — Validate Every Logic Path Before Going Live

A misconfigured automation trigger does not fail visibly. It silently applies the wrong tag — or fails to apply the right one — to every candidate who meets its condition. By the time a recruiter notices the segmentation is wrong, hundreds of records may be affected.

Validation is non-negotiable. Run every automation path against test contacts before activating it for live candidates.

Validation checklist:

• Create three to five test contact records with deliberately varied field values.
• Manually set each field to a trigger-condition value and confirm the expected tag is applied within the automation’s processing window.
• Change the field value away from the trigger condition and confirm the tag is removed (if your rule includes removal).
• Run a Keap segment filter using the applied tag and confirm only the intended test contacts appear in the results.
• Check the automation history log for each test contact to confirm the trigger fired on the correct action.
• Confirm that no unintended tags were applied as side effects of other automations watching the same field.

After validation, activate automations one at a time rather than all at once. This preserves your ability to isolate any unexpected behavior to a single automation.

For ATS-connected environments where tags must also reflect data passed from an external system, see the guide on Keap ATS integration and dynamic tagging ROI.

How to Know It Worked

The system is operating correctly when all of the following are true:

• A recruiter can run a Keap segment filter using two or more tag conditions and return a precise candidate list in under 30 seconds without manual review.
• Every candidate record has at least one stage tag, one skill or attribute tag, and one engagement signal tag — applied by automation, not manually.
• No recruiter is applying or removing tags manually as part of their standard daily workflow.
• The master taxonomy document accounts for every tag that exists in the live system — no undocumented tags appear in the Keap tag list.
• Automation history logs show clean trigger-fire records with no missed fires or duplicate applications over a 7-day monitoring window.

SHRM research on recruiting efficiency identifies time-to-shortlist as a key process metric. When your field-and-tag architecture is working correctly, generating a qualified shortlist from your existing candidate pool should require a segment filter, not a manual database review.

Common Mistakes and Troubleshooting

Mistake 1: Building tags before fields

Tags that are not anchored to structured field values must be applied manually. Manual tag application is inconsistent by nature — different recruiters apply different tags to similar candidates, destroying segmentation reliability. Always define fields first, then build tags that automation applies based on field values.

Mistake 2: Using text fields for filterable attributes

A text field containing “5 years Python experience” is invisible to Keap automation conditions. If you need to segment on an attribute, that attribute must live in a dropdown, multi-select, number, or yes/no field — never free text. Audit existing text fields and migrate filterable data to structured field types before building automation.

Mistake 3: No tag removal logic

Tags applied without corresponding removal rules accumulate. A candidate tagged STAGE | Interview | Scheduled three months ago who completed and failed the interview still carries that tag if no removal trigger was built. Over time, stale tags make segmentation filters unreliable. Every apply rule needs a corresponding removal condition.

Mistake 4: Ad-hoc tag creation by individual recruiters

Once a taxonomy exists, undisciplined tag creation by individual team members is the single fastest path to taxonomy collapse. Enforce the documentation rule: no tag is created in Keap without a corresponding entry in the master taxonomy document. Conduct a quarterly audit to identify and retire orphaned tags.

Mistake 5: Skipping the test-contact validation step

Automation logic that looks correct in the builder sometimes misfires in practice due to condition ordering, field-type mismatches, or conflicting rules. Always validate on test contacts before activating against the live database. The cost of a validation session is two hours. The cost of mis-tagging 500 candidates is a full-day cleanup and a damaged pipeline.

Next Steps: From Architecture to Intelligence

The custom field and dynamic tag architecture built in this guide is the prerequisite for every advanced recruiting automation in Keap. Candidate lead scoring, AI-assisted engagement sequencing, dormant talent pool reactivation, and pipeline analytics all depend on the structured data layer you have now created.

For the broader strategy that connects this architecture to AI-driven candidate scoring and engagement, return to the full dynamic tagging strategy for recruiting teams. For advanced segmentation techniques that build on this foundation, see the guide on advanced Keap tagging for talent pipeline segmentation.

The architecture you build in a single focused session becomes the infrastructure your recruiting operation runs on for years. The teams that invest the upfront time in OpsMap™-driven field and tag design consistently outperform those that build reactively — because their automation actually fires on clean, structured, trustworthy data.