Keap CRM Glossary: Essential Terms for Recruiters and HR

Keap CRM™ has a vocabulary problem — not in the platform itself, but in how recruiting teams approach it. Terms get used interchangeably in internal conversation. Tags proliferate without a taxonomy. Custom Fields get skipped. Six months into a live system, automations fire on the wrong contacts and the team concludes the CRM doesn’t work. The platform works. The vocabulary wasn’t locked in before the build started.

This glossary defines every essential Keap CRM™ term through a recruiting lens — what each component is, what it does, and how it connects to the next layer of your automation architecture. Before you explore how Keap CRM™ automation transforms candidate nurturing or invest time in Keap CRM™ tagging and segmentation for recruiters, establish shared vocabulary across your team. That step is not optional background reading — it is the contract your team signs before touching the system.

Jump to a term: Contact Record · Tag · Campaign · Sequence · Pipeline · Opportunity · Custom Fields · Lead Scoring · Form · Automation Trigger · Broadcast · Task · Segmentation

What is a Contact Record in Keap CRM™?

A Contact Record is the master profile for every individual in your Keap CRM™ database — candidates, clients, and hiring managers alike. Every automation in the platform runs off Contact Record data.

Contact Records store name, email, phone, interaction history, applied tags, custom field values, lead scores, linked documents, and campaign membership status. For recruiters, this means a candidate’s entire journey — every email sent, every form submitted, every pipeline stage reached — lives in one record accessible to every team member.

The practical consequence: a Contact Record is only as useful as the data inside it. Incomplete records produce incorrect automation outcomes. A tag that should segment a candidate into a “Java Developer” pool only fires correctly if that tag was applied when the Contact Record was created or imported. Our guide on importing candidate data covers how to structure records correctly at the point of entry — before a single automation runs.

Parseur’s Manual Data Entry Report estimates that manual data entry costs organizations approximately $28,500 per employee per year in lost productivity. Clean Contact Records built through automated form capture and structured import eliminate the bulk of that cost at the source.

What are Tags in Keap CRM™?

Tags are descriptive labels applied to Contact Records that power segmentation and trigger automations. A tag tells Keap CRM™ who a contact is and what should happen to them next.

When a tag is applied — whether manually, by a form submission, or by an automation — Keap CRM™ can immediately fire a Campaign, assign a Task, move a Pipeline stage, or update a score. Recruiters use tags to categorize candidates by:

• Skill set: Java-Developer, Bilingual-Spanish, AWS-Certified
• Pipeline stage status: Interviewed-Round-1, Offer-Extended, Hired
• Availability: Active-Now, Passive-Q3, Not-Available
• Sourcing channel: Referral, Job-Board, Event-2025
• Geographic preference: Open-Remote, Pacific-Northwest-Only

The single most expensive tagging mistake: creating tags ad hoc as needs arise. Recruiting teams that skip building a tag taxonomy before go-live routinely end up with 150–300 overlapping, duplicated, or contradictory labels within six months. When tags conflict, automations fire on wrong contacts, compliance audit trails become unreliable, and the only fix is a full database audit. Build the taxonomy in a spreadsheet before you create a single tag in the platform.

What is a Campaign in Keap CRM™?

A Campaign is the overarching automation journey — the complete map of steps, branches, decisions, and outcomes a contact moves through over time. Campaigns are the strategic layer of Keap CRM™ automation.

In a recruiting context, a Campaign governs the full candidate lifecycle for a defined scenario:

• An Applicant Nurture Campaign that runs from initial application through first-round interview scheduling
• A Passive Candidate Campaign that delivers industry insights over 90 days, converting passive prospects into active applicants
• A New Hire Onboarding Campaign that fires from the moment an offer is accepted through day 90

Campaigns can branch based on contact behavior. If a candidate opens a scheduling link, they enter one Sequence. If they do not open it within 48 hours, a different Sequence fires with a follow-up. This conditional logic is what makes Campaigns fundamentally different from simple email blasts — and fundamentally more powerful for candidate experience at scale.

What is a Sequence in Keap CRM™?

A Sequence is a linear chain of automated actions — emails, tasks, delays, field updates — that lives inside a Campaign. Sequences execute deterministically: action one, then action two, then action three, with defined time delays between each.

Campaign and Sequence are not synonyms. The Campaign is the orchestration layer. The Sequence is the execution layer. A single Campaign typically contains multiple Sequences that fire based on different triggers or branching conditions.

Common recruiting Sequences include:

• Interview Follow-Up Sequence: Immediate thank-you email → 48-hour expectation-setting email → 5-day status update email
• Offer Acceptance Sequence: Congratulations email → document checklist email → hiring manager introduction email
• Passive Re-Engagement Sequence: Industry article → salary benchmark report → role announcement for a matched opening

The most common Sequence mistake is building one monolithic Sequence that tries to handle every candidate scenario. Sequences that branch are Campaigns. Keep Sequences linear and reusable — build them modularly so the same “Interview Confirmation” Sequence can be called by multiple Campaigns.

What is a Pipeline in Keap CRM™?

A Pipeline is Keap CRM™’s visual stage-tracking feature that shows every active Opportunity moving through defined stages toward a hire or placement. It functions as your real-time recruiting operations dashboard.

Each Pipeline stage represents a discrete decision milestone. A well-designed recruiting Pipeline might include: Applied → Phone Screened → Hiring Manager Interview → Reference Check → Offer Extended → Hired. Each stage move can trigger automations, making the Pipeline the connective tissue between your visual workflow and your backend automation logic.

The most common Pipeline configuration mistake: creating a stage for every interaction point rather than every decision point. A stage should represent a moment where something definitively changes — the candidate either advances, stalls, or exits. If moving from one stage to the next does not trigger a different action or communication, those two stages should be one. Our guide on building custom Keap CRM™ pipelines walks through stage architecture for recruiting, HR, and client management simultaneously.

What is an Opportunity in Keap CRM™?

An Opportunity is a distinct record representing a specific potential placement, job order, or business deal — separate from, but linked to, the Contact associated with it.

One Contact can have multiple concurrent Opportunities: a candidate placed in a contract role while also being considered for a permanent position at a different client. Opportunities carry their own data — job title, projected placement fee, expected close date, linked hiring manager Contact, and Pipeline stage. They are the unit that Pipeline reporting runs on.

Recruiters who track placements solely at the Contact level lose the ability to report on pipeline revenue by role, measure time-to-fill per position, or manage multiple concurrent placements per candidate without data collisions. Opportunities are not optional for agencies with any volume — they are the structural requirement for accurate recruiting operations reporting.

What are Custom Fields in Keap CRM™?

Custom Fields are user-defined data fields added to Contact or Opportunity Records to capture information the platform does not store by default. Standard Keap CRM™ fields cover name, email, phone, company, and address. Everything recruiting actually needs lives in Custom Fields.

Essential Custom Fields for recruiting include:

• Years of Experience (number field)
• Primary Skill Set (text or dropdown)
• Certifications Held (checkbox list)
• Availability Date (date field)
• Desired Salary Range (number range)
• Work Authorization Status (dropdown)
• Placement History (text or linked record)
• Last Contacted Date (date field, auto-updated by automation)

Custom Fields are what make your Contact Records filterable, segmentable, and automation-ready beyond basic tag logic. If a key data point is stored in a notes field instead of a Custom Field, you cannot filter on it, trigger automations from it, or report against it. Our dedicated resource on Keap CRM™ Custom Fields for HR covers field types, naming conventions, and the configurations that drive the highest automation ROI.

McKinsey Global Institute research consistently identifies poor data structure as a primary driver of automation failure in knowledge work functions — recruiting included. Custom Fields are where you solve that problem upstream.

What is Lead Scoring in Keap CRM™?

Lead Scoring is a numeric ranking system that quantifies how engaged or qualified a contact is, based on behaviors and attributes you define. Keap CRM™ assigns point values to actions — email opens, link clicks, form submissions, page visits — and to attributes stored in Custom Fields.

For recruiters, a high Lead Score signals a warm candidate: someone who has opened multiple emails, clicked a scheduling link, holds a required certification, and is flagged as actively available. When a score crosses a threshold you define, Keap CRM™ can automatically assign a high-priority follow-up Task to a recruiter, launch a personalized outreach Sequence, or move the Contact to an active Pipeline stage.

The practical benefit is significant: your team stops manually hunting through a database for engaged candidates. The system surfaces them. Gartner research on talent acquisition technology consistently identifies automated candidate prioritization as one of the highest-ROI applications of recruiting CRM investment.

What is a Form in Keap CRM™?

A Keap CRM™ Form is an embeddable or hosted data-capture tool that creates or updates Contact Records automatically on submission — with no manual entry required.

Recruiters embed Forms on career pages, job posting landing pages, event registration pages, and referral portals. The moment a candidate submits a Form, Keap CRM™ can apply tags, update Custom Fields, increment a lead score, launch a Campaign, notify the assigned recruiter, and move an Opportunity to a new Pipeline stage — simultaneously, in seconds.

Form field architecture matters as much as the Form itself. Every Form field should map directly to a Contact Record field — either a standard field or a Custom Field — that drives downstream automation. A field that captures data no automation uses is clutter. A missing field that an automation depends on breaks the trigger chain. Our strategic guide to Keap CRM™ lead forms covers field architecture and trigger mapping in depth.

What is an Automation Trigger in Keap CRM™?

An Automation Trigger is the specific event or condition that starts a Sequence or Campaign. Without a trigger, nothing in Keap CRM™ fires automatically.

Trigger types available in Keap CRM™ include:

• Form submission — A candidate submits an application form
• Tag applied — A recruiter manually tags a contact “Offer-Accepted”
• Pipeline stage change — An Opportunity moves to “Reference Check”
• Date-based — 30 days before a contract end date
• Link clicked — A candidate clicks a scheduling link in an email
• Score threshold crossed — A lead score exceeds 80 points

Trigger design is the most technically demanding part of a Keap CRM™ implementation. A trigger that is too broad fires on the wrong contacts and generates noise. A trigger that is too narrow misses candidates who should have been captured. Testing every trigger against real Contact Records — not hypothetical ones — before go-live is non-negotiable. Our guidance on Keap CRM™ data clean-up strategy explains why trigger reliability depends entirely on data integrity upstream.

What is a Broadcast in Keap CRM™?

A Broadcast is a one-time, manually sent communication — typically an email — deployed to a defined segment of your Contact database at a specific moment. Unlike Campaign Sequences, Broadcasts are not recurring and not triggered by contact behavior.

Recruiters use Broadcasts for time-sensitive, non-repeatable outreach: announcing a newly opened senior engineering role to a tagged pool of qualified passive candidates, for example, or sending a market compensation report to a client segment ahead of a contract renewal conversation.

Broadcasts are powerful because they feel personal at scale — but only when the segmentation driving them is accurate. A Broadcast sent to the wrong tag group damages candidate relationships, wastes recruiter credibility, and cannot be recalled. Segment carefully before sending. Always preview the Contact count your segment returns before deploying.

What is a Task in Keap CRM™?

A Task in Keap CRM™ is an assigned action item linked to a Contact or Opportunity Record, with a defined owner, due date, priority, and completion status. Tasks can be created manually or triggered automatically by Campaigns and Sequences.

Automated Tasks are where Keap CRM™ eliminates the invisible cognitive overhead of recruiting. When a candidate completes a first-round interview, the system auto-creates a Task for the recruiter to collect hiring manager feedback within 24 hours. When an Opportunity moves to “Reference Check,” a Task fires for the recruiter to send the reference authorization form. No manual tracking required. No follow-up forgotten.

Completed Tasks feed directly into the Contact Record’s interaction history, giving the full recruiting team real-time visibility into what has been done and what is pending. SHRM research identifies missed follow-up and inconsistent candidate communication as primary drivers of candidate drop-off during active searches — automated Tasks directly address that failure point.

What is Segmentation in Keap CRM™?

Segmentation is the practice of dividing your Contact database into precise subsets based on shared attributes or behaviors, so communications and automations target the right contacts — and only the right contacts.

In Keap CRM™, segmentation is executed through two primary mechanisms: Tags and Custom Field filters. A well-segmented database lets a recruiter instantly identify all contacts who hold a specific certification, are actively available, and are located within a defined geography — and launch a targeted outreach Sequence to that group and no one else.

Without deliberate segmentation architecture established at implementation, every Broadcast goes to everyone, every automation fires indiscriminately, and the candidate experience degrades into noise. Asana’s Anatomy of Work Index identifies unnecessary coordination work as one of the largest drains on knowledge worker productivity — undisciplined segmentation creates exactly that coordination drag inside your recruiting operation.

Segmentation is not a configuration task you return to after go-live. It is an architecture decision you make before building anything else. The tag taxonomy, Custom Field schema, and filter logic all need to be mapped offline — in a spreadsheet or whiteboard session — before a single contact is imported.

How These Terms Work Together

Every term in this glossary represents a distinct layer of your Keap CRM™ recruiting architecture:

• Contacts hold the data.
• Tags and Custom Fields structure and segment it.
• Forms capture it at source.
• Triggers fire on it.
• Sequences execute the actions.
• Campaigns orchestrate the full journey.
• Pipelines visualize stage-by-stage progress.
• Opportunities track individual placements.
• Tasks assign human accountability.
• Lead Scores prioritize recruiter attention.
• Broadcasts enable precise one-time outreach.
• Segmentation ties all of it together with targeting precision.

These components are not independent features you adopt one at a time. They are an interconnected system where the quality of every upstream layer determines the reliability of every downstream automation. This is exactly why implementing Keap CRM™ for automated recruiting demands a sequenced architecture approach — pipeline stages, custom fields, and trigger logic built before automation runs, not after.

Master the vocabulary first. Then build the system. That sequence is the difference between a CRM that replaces hours of manual work every week and one that creates expensive new problems to manage.