How to Set Up Your First Keap Campaign for HR Automation: A Step-by-Step Guide

Keap’s campaign builder is the operational engine behind every HR automation sequence described in the Keap recruiting automation pillar. This guide shows you how to build your first working campaign from a blank canvas — structured around candidate acknowledgment — so you have a repeatable pattern for every workflow you build after it.

The build takes under four hours. It eliminates the manual follow-up tasks that consume the first hour of most HR mornings. And the same logic applies to every subsequent campaign you add: interview scheduling, offer delivery, onboarding initiation.

Before You Start

Skip this section and your campaign will fire incorrectly on the first live contact. Spend 30 minutes here and every subsequent build gets faster.

What You Need

• A Keap account with Campaign Builder access. Keap Pro or higher includes the visual campaign builder. Keap Lite does not.
• A mapped process on paper. Write out every manual step you currently take when a candidate applies — every email, every note, every reminder. This list becomes your campaign structure.
• At least three contact tags already created. You need a “Candidate – New,” a “Candidate – Active,” and a “Candidate – Inactive” tag minimum before your first campaign references them. Tags you define inside a campaign but haven’t created globally will break other workflows.
• A test contact record. Create a dummy contact using an email address you control. You will use this to run every campaign end-to-end before it touches a real candidate.
• 30 minutes of uninterrupted time for the logic stage. Asana research consistently finds that task-switching costs the equivalent of a full workday per week — campaign logic requires sustained focus, not multitasking.

Risks to Know Before You Build

• Duplicate enrollment: A contact can enter the same campaign twice if your trigger fires on a tag that gets re-applied. Build the deduplication guard rail in Step 4.
• Time-offset errors: Keap sequences count time from when a contact enters the sequence, not from when the campaign started. A “Day 3 follow-up” fires 72 hours after sequence entry, not 72 hours after form submission. Plan your offsets accordingly.
• Orphaned contacts: Contacts who enter a campaign but never hit a goal sit in the sequence indefinitely. Every campaign needs an exit tag or a maximum wait timer.

Step 1 — Define the Single Outcome This Campaign Must Produce

One campaign, one outcome. The candidate acknowledgment campaign has exactly one job: confirm receipt of an application and move qualified candidates to the next pipeline stage without manual intervention.

Write your outcome in one sentence: “Every candidate who submits an application receives an acknowledgment within five minutes, receives two follow-up touchpoints over seven days, and is either tagged ‘Interview Ready’ or ‘Candidate – Inactive’ by Day 8.”

If your sentence has more than one outcome, split it into two campaigns. HR teams that build monolithic campaigns — one campaign attempting to handle acknowledgment, screening, scheduling, and onboarding — produce campaigns that are impossible to troubleshoot when a single step fails.

Checkpoint: Your outcome sentence is written. It has one endpoint. Move to Step 2.

Step 2 — Map Your Logic on Paper Before Opening the Builder

Open a blank document or a whiteboard. Sketch the following before touching Keap:

1. Trigger: What event starts the campaign? (Example: “Web form submitted — Application Form v2”)
2. Entry tag check: Does the contact already carry a “Candidate – Active” tag? If yes, exit immediately. If no, proceed.
3. Sequence 1 — Acknowledgment: Immediate email (Day 0), follow-up email (Day 3), final check-in email (Day 7).
4. Goal 1 — Candidate Advances: Contact clicks the “Schedule a Call” link in any email. When this fires, the contact exits Sequence 1 and enters Sequence 2 (handled by a separate campaign).
5. Goal 2 — Candidate Goes Cold: Day 8 timer fires without Goal 1 being reached. Apply “Candidate – Inactive” tag. Remove “Candidate – Active” tag. Exit campaign.

This five-item map is your entire campaign. Everything in the Keap builder is just a visual representation of what you’ve already decided on paper.

For a deeper look at how tags drive this logic, see the guide on Keap tags and custom fields for candidate management before proceeding.

Checkpoint: Your paper map has a trigger, at least one sequence, at least one goal, and an exit path. Move to Step 3.

Step 3 — Understand the Three Mechanical Components

Before you touch the canvas, lock in the definitions of the three components you will use in every campaign you ever build:

Sequences

A Sequence is a container holding a series of timed steps: emails, SMS messages, internal tasks, tag applications, and field updates. Steps inside a Sequence fire relative to when the contact entered that Sequence — not relative to when they entered the campaign. Every Sequence needs a name that reflects its function (“Sequence 1 — Acknowledgment Emails”), not a generic label.

Goal Tiles

A Goal tile is a behavioral checkpoint. When a contact completes the action defined in the Goal — clicks a link, submits a form, receives a tag — they are pulled out of whatever Sequence they are currently in and moved to the next element connected to the Goal’s output. Goals are what make Keap campaigns responsive rather than robotic. Without Goals, every contact completes every sequence regardless of what they actually did.

Decision Diamonds

A Decision Diamond evaluates a yes/no condition on a contact record — “Does this contact have tag X?” — and routes them down one of two paths. Use Decision Diamonds for deduplication (Step 4) and for branching logic when different candidate profiles need different messaging.

Checkpoint: You can define all three components without referencing this guide. Move to Step 4.

Step 4 — Build the Deduplication Guard Rail First

This step prevents duplicate enrollment before any candidate ever touches your campaign.

1. Open Keap → Campaigns → New Campaign. Name it “01 — Candidate Acknowledgment.”
2. Drag a Web Form tile onto the canvas. Connect it to your application form.
3. Drag a Decision Diamond immediately after the Web Form tile. Label it “Already Active?”
4. Configure the Diamond: If contact has tag “Candidate – Active” → YES path → drag to a Stop tile (no further action). If contact does NOT have tag “Candidate – Active” → NO path → continue to next step.
5. Connect the NO path to a Sequence tile. Label it “Sequence 1 — Acknowledgment.”

The Diamond is now your gate. A returning applicant hits the YES path and exits silently. A new applicant hits the NO path and enters your sequence. This five-minute step eliminates the most common beginner error in Keap campaign construction.

Checkpoint: Your canvas has: Web Form → Decision Diamond → (YES: Stop) / (NO: Sequence 1). Move to Step 5.

Step 5 — Build Sequence 1: The Acknowledgment Sequence

Double-click the Sequence 1 tile to enter the sequence editor.

Step inside the Sequence: Apply Entry Tag

Add a Tag Application step as the first action: apply “Candidate – Active.” This fires the moment the contact enters the sequence and blocks the deduplication guard rail from sending them through again if the web form fires a second time before they exit.

Email 1 — Day 0: Immediate Acknowledgment

• Subject: “We received your application — here’s what happens next.”
• Content: Confirm receipt, set a clear timeline (“Our team reviews applications within 3 business days”), include one link to your scheduling page for candidates who want to be proactive. Keep it under 150 words.
• Timing: Send immediately (0-minute delay).

Email 2 — Day 3: Culture Touchpoint

• Subject: “While you’re waiting — a look inside [Company Name]”
• Content: One paragraph about the team or mission. One link to a culture video or team page. Include the scheduling link again.
• Timing: 3-day delay from sequence entry.

Email 3 — Day 7: Final Check-In

• Subject: “Still interested? Here’s how to move forward.”
• Content: Direct ask. “If you’re still interested in the role, click below to schedule a 15-minute call with our team.” One link. No fluff.
• Timing: 7-day delay from sequence entry.

Exit the Sequence editor and return to the main canvas.

For email copy frameworks that convert at each of these stages, the Keap email templates for recruiting automation satellite covers subject lines and body structures in detail.

Checkpoint: Sequence 1 has a tag-apply step and three emails with correct day offsets. Move to Step 6.

Step 6 — Add Goal Tiles and Exit Logic

Goal 1 — Candidate Advances (Link Click)

1. Drag a Goal tile onto the canvas. Position it above Sequence 1 so it can intercept contacts at any point during the sequence.
2. Configure: Goal type: Email Link Click. Link: your scheduling page URL. This goal can be achieved while in: Sequence 1.
3. Connect Goal 1’s output to a Sequence 2 tile (you will build this in your interview scheduling campaign — for now, connect it to a Tag Application step that applies “Interview Ready” and exits).

Goal 2 — Candidate Goes Cold (Timer)

1. Drag a second Goal tile. Configure: Goal type: Timer. Fires 8 days after campaign entry if Goal 1 has not been reached.
2. Connect Goal 2’s output to a Sequence that applies tag “Candidate – Inactive” and removes tag “Candidate – Active.”

Your canvas now has a full flow: Web Form → Diamond → Sequence 1 (with Goal 1 intercepting early movers) → Goal 2 (catching non-responders at Day 8).

For more on how this integrates with interview scheduling automation with Keap, see the dedicated how-to satellite in this series.

Checkpoint: Your canvas has two Goal tiles. Both have defined output paths. Move to Step 7.

Step 7 — Test With a Live Contact Record, Then Publish

Do not use Preview mode as your sole test. Preview simulates email rendering — it does not simulate timing offsets, tag applications, or goal triggers. Use your test contact record.

Test Protocol

1. Publish the campaign (set status to Active).
2. Submit your application test form using the dummy contact’s email address.
3. Verify in the contact record: “Candidate – Active” tag applied, Email 1 queued in the contact’s email history.
4. Manually trigger Goal 1 by clicking the scheduling link in Email 1. Verify: contact tagged “Interview Ready,” Sequence 1 activity halted.
5. Reset the dummy contact (remove all tags), re-enter the campaign, and this time do not click any link. Fast-forward by temporarily reducing the Day 8 timer to 8 minutes for testing purposes. Verify: “Candidate – Inactive” tag applied, “Candidate – Active” tag removed.
6. Restore the Day 8 timer. Re-publish.

The 90% interview show-up rate case study on this site was built on this exact modular, tested approach — one campaign per pipeline stage, each verified before the next was constructed.

Checkpoint: All three test scenarios (immediate advance, Day 8 cold exit, duplicate entry blocked) fired correctly. Your campaign is production-ready.

How to Know It Worked

Check these metrics after your first 20 real contacts have moved through the campaign:

• Email 1 open rate above 60%: Acknowledgment emails to people who just applied have the highest open rates of any email type. Below 60% signals a subject line problem or a delivery delay.
• Goal 1 completion rate above 15%: At least 15% of candidates clicking through to schedule a call means your messaging is working. Below that, review Email 3’s call-to-action copy first.
• Zero contacts stuck in Sequence 1 beyond Day 9: If contacts are still in Sequence 1 after nine days, your Day 8 timer Goal is misconfigured. Check the goal type and achievement window.
• Zero duplicate tag applications: Open any contact who applied twice. They should show exactly one “Candidate – Active” tag application, not two. If you see two, the Decision Diamond is not positioned correctly relative to the Web Form trigger.

Common Mistakes and How to Fix Them

Mistake 1 — Building Email Copy Before Campaign Logic

Beautiful email copy inside a broken campaign logic structure still produces broken results. Always complete Steps 1 through 4 before writing a word of email content.

Mistake 2 — Using Calendar Date Timers Instead of Relative Timers

Calendar date timers fire at a fixed date — not relative to when the contact entered. For candidate journeys, always use relative timers (“3 days after sequence entry”) unless you are running a fixed-date recruiting event campaign.

Mistake 3 — Skipping the Exit Tag on Goal 2

If “Candidate – Active” is not removed when a candidate goes cold, that contact is permanently blocked from re-entering the acknowledgment campaign if they apply again in six months. Always pair an “apply tag” with a corresponding “remove tag” on every exit path.

Mistake 4 — Running Only Preview Tests

Keap Preview shows you what the email looks like. It does not test tag logic, goal triggers, or timing offsets. A campaign that passes Preview and fails on a live contact is the most common debugging scenario. Always run a live contact test before your campaign touches real applicants.

Mistake 5 — Mixing Multiple Outcomes Into One Campaign

HR teams that build one large campaign — acknowledgment through onboarding — spend four times as long debugging a single failing step because they cannot isolate which sequence is at fault. Keep campaigns modular. For the candidate follow-up campaign and subsequent pipeline stages, build a new campaign for each distinct stage.

What to Build Next

Your acknowledgment campaign is running. The next highest-ROI build for most HR teams is interview scheduling automation — the manual scheduling loop (email, calendar check, reply, confirm) is where recruiters lose the most unrecoverable time. Gartner research on HR technology consistently identifies scheduling coordination as one of the top targets for automation ROI in talent acquisition functions.

After scheduling, move to onboarding initiation. SHRM data indicates that structured onboarding processes improve new hire retention — and a Keap onboarding campaign delivers that structure without adding to HR’s workload. The Keap HR onboarding automation satellite covers that build step by step.

For data-protection requirements that apply to your candidate contact records — particularly if you operate in or recruit from the EU — review the GDPR compliance for HR data in Keap satellite before expanding your tag library.

Finally, when you’re ready to evaluate how Keap fits your broader HR tech stack — alongside your ATS, HRIS, and any AI tooling — that satellite covers the integration architecture decisions that determine whether automation compounds or creates new bottlenecks.

The candidate acknowledgment campaign you built today is the pattern. Everything else is repetition with different content.