Keap order forms don’t expose a stable thank-you URL, so standard web-page automation breaks. The fix is a hidden web form acting as a landing page, seeded with Keap’s tracking script, then linked from the order form’s redirect. These 7 steps walk through the full setup so every submission fires the right tag or automation.

If you sell the same product through multiple order forms — say, company-specific discount portals for employee sign-ups — you need a way to identify which form a contact used, not just which product they bought. Keap’s built-in order form automation fires on the product, not the form. That gap costs you segmentation accuracy and forces manual cleanup.

The workaround covered here is battle-tested: a lightweight web form stands in as a landing page, and Keap’s web-page automation handles the trigger. It’s the same pattern useful for teams evaluating automation platforms — the cleanest solutions rarely use the most obvious path. For broader context on building reliable automated workflows, see our guide to automation-first thinking and our breakdown of 7 questions to ask before you automate anything.

Before diving in, note that Make.com is the automation platform we endorse for all external workflow orchestration. The steps below cover Keap’s native campaign builder for internal tagging; where cross-platform automation is involved, Make.com is the right tool. See the Make.com FAQ for a quick orientation.

Why Keap’s Order Form Thank-You URL Breaks Standard Automation

Keap generates the thank-you URL for order forms dynamically. That means the URL changes per session and cannot be reliably registered inside a web-page automation rule. If you try to paste it directly into the “Add URL” field in your campaign, the trigger will fail silently — contacts complete checkout and nothing fires.

The workaround routes contacts through a stable, hosted web form URL instead. That URL never changes, so the web-page automation rule works every time. The web form itself is invisible to the user — it functions purely as a tracking endpoint.

What You Need Before You Start

• Access to Keap’s Campaign Builder
• An existing order form (or one ready to configure)
• The ability to create a new web form inside the same campaign
• A tag already created in Keap (or a sequence ready to trigger)
• Basic access to your order form’s redirect/thank-you settings

The 7 Steps

Step 1 — Create a New Web Form Inside Your Campaign

Open your campaign in Keap’s Campaign Builder and add a new web form. This form is not for data collection — its only job is to serve as a trackable landing page. Give it a descriptive internal name so you know which order form it corresponds to (e.g., “CompanyA Order Confirm — Tracking Only”).

Add a logo image and a brief paragraph of text to make the page look like a legitimate confirmation screen if a contact ever lands on it directly. This prevents confusion if someone bookmarks or revisits the URL.

Step 2 — Hide the Submit Button

The web form has a default Submit button. Since this page isn’t accepting form submissions, the button is confusing and unnecessary. Navigate to the Submit button’s advanced styling settings and change all color values to white (FFFFFF). Set rounded corners to zero. When saved, the button becomes invisible against a white background while remaining in the DOM — the form still functions technically, but visitors see a clean landing page.

Step 3 — Publish the Web Form and Copy the Hosted URL

Publish the web form and navigate to its hosted URL options. Copy the ugly (system-generated) hosted URL — not the pretty URL. The reason: if you ever rename or update the pretty URL slug for any reason, the web-page automation rule that depends on it breaks immediately. The system-generated URL is permanent and will never change regardless of what you rename the form.

Step 4 — Create a Web Page Automation Rule Pointing to That URL

Inside your campaign, add a Web Page Automation trigger. In the “Add URL” field, paste the hosted URL you copied in Step 3. Press Enter — do not just click Save. Keap requires an explicit Enter keystroke to register the URL; clicking Save without pressing Enter discards the entry silently.

Once the URL is registered, click “Copy” to copy the JavaScript tracking snippet that Keap generates for this rule.

Step 5 — Embed the Tracking Script in the Web Form

Return to the web form editor. Add an HTML snippet element (typically available in the “Other” or “Advanced” section of the form builder). Paste the JavaScript tracking snippet you copied in Step 4 into that HTML element. Position it toward the bottom of the form layout. Save the form.

This script is what tells Keap “someone has visited this URL” — without it, the web-page automation rule has no mechanism to fire. The script and the URL registration work together; neither functions without the other.

Step 6 — Connect the Automation to Your Tag or Sequence

In the campaign, connect the Web Page Automation trigger to whatever action you want to fire. The most common setup: apply a tag. That tag then triggers downstream sequences, email campaigns, or CRM updates. You can also connect directly to a sequence if you don’t need intermediate tagging.

For multi-form setups, build one hidden web form and one web-page automation rule per order form. Each fires its own tag, so your segmentation stays clean across company portals, discount tiers, or product variants. This is the same principle behind mapping processes before automating — one trigger, one outcome, zero ambiguity.

Step 7 — Set the Order Form’s Thank-You Redirect to the Web Form URL

Open the order form’s settings and find the thank-you page or redirect URL field. Paste the hosted web form URL (the ugly system URL from Step 3) as the redirect destination. When a contact completes checkout, Keap sends them to that URL. The tracking script fires, the web-page automation detects the visit, and the tag or sequence triggers.

The contact sees a clean confirmation-style page. The automation fires in the background. No manual follow-up required.

How to Know It Worked

After completing setup, run a test transaction through the order form using a test contact record. After checkout completes:

• The browser should redirect to your hidden web form page
• The confirmation-style content (image, paragraph text) should display
• Within a few minutes, the test contact’s record in Keap should show the applied tag or show entry into the connected sequence
• The campaign history for the contact should show the web-page automation as the trigger source

If the tag does not appear, verify that: (a) you pressed Enter after pasting the URL in the web-page automation rule, (b) the tracking script is saved inside the web form HTML element, and (c) the order form redirect URL exactly matches the hosted URL registered in the rule.

Common Mistakes That Break This Workflow

• Clicking Save instead of pressing Enter in the URL field. The URL appears to save but is not registered. The rule never fires.
• Using the pretty URL instead of the system URL. Works until someone renames the slug, then breaks silently.
• Forgetting to embed the tracking script in the web form. The URL visit is never detected without it.
• Building one web form for multiple order forms. All orders trigger the same tag, destroying segmentation. Build one tracking form per order form.
• Testing with the same contact record repeatedly without clearing tag history. Keap may not re-apply a tag to a contact who already holds it, making tests appear to fail when setup is correct.

Scaling This to Multiple Order Forms

The same pattern scales cleanly. For each additional order form:

1. Duplicate the hidden web form inside the campaign
2. Rename it to match the new order form
3. Create a new web-page automation rule with the new form’s hosted URL
4. Embed the new tracking script in the new web form
5. Set the new order form’s redirect to the new hidden form’s URL
6. Connect to a unique tag or sequence

This architecture supports any number of company portals, pricing tiers, or product variants — each with clean, independent automation chains. Teams managing this level of workflow complexity often find that external orchestration in Make.com handles the downstream logic (CRM updates, notifications, data routing) more reliably than chaining Keap sequences alone. See 10 automations that are easy to build with Make and AI for examples of what that downstream layer looks like in practice.

For teams evaluating whether to keep building inside a CRM’s native campaign builder or move more logic into a dedicated automation platform, the DIY automation vs. hiring a Make partner guide covers that decision in detail. And if manual data processes are still creating gaps that automation can’t fill, the manual data entry cost breakdown quantifies what those gaps actually cost.

Frequently Asked Questions

Why can’t I just use the order form’s built-in thank-you page URL?

Keap generates the order form thank-you URL dynamically per session. The URL changes with every transaction, so it cannot be registered as a stable trigger in a web-page automation rule. The hidden web form approach uses a fixed, hosted URL that never changes regardless of transaction volume.

Do contacts see the hidden web form?

Yes — they land on it after checkout. That’s why adding a confirmation-style image and paragraph text matters. The Submit button is styled white to disappear, so the page looks like a standard order confirmation screen. Contacts see a clean page; the tracking script fires invisibly in the background.

What happens if I use the pretty URL?

The automation works until the pretty URL slug is changed. At that point, the web-page automation rule holds the old URL, the order form redirect points to the new URL, and the trigger breaks silently. No error surfaces in Keap — contacts just stop receiving the tag or entering the sequence. Use the system-generated URL to eliminate this risk entirely.

Can I trigger a full sequence instead of just a tag?

Yes. The web-page automation rule connects to any campaign sequence, not only tag actions. Tags are the most common choice because they offer flexibility — a tag applied here can drive multiple sequences across different campaigns. But if the action is simple and self-contained, connecting directly to a sequence is valid.

How do I test without corrupting my live contact records?

Create a dedicated test contact in Keap. After each test, manually remove the applied tag from the test contact before running the next test. Keap won’t re-apply a tag to a contact who already holds it, so clearing between tests ensures each run accurately reflects the automation state.

Does this work if I’m also using Make.com for downstream automation?

Yes. The Keap-side setup handles tagging inside the CRM. Make.com picks up from there — a tag applied in Keap can trigger a Make scenario via webhook or polling, which then handles downstream steps: updating other systems, sending notifications, routing data to spreadsheets or other platforms. The two layers work independently and complement each other cleanly.

Additional Reading

• What Is Automation-First? Why You Should Automate Before You Add AI
• 7 Questions to Ask Before You Automate Anything (The OpsMap Checklist)
• How to Run an OpsMap Audit Before Automating Anything
• Make.com FAQ: Everything Zapier Users Ask Before Switching
• 10 Automations That Are Finally Easy to Build With Make + AI — No Developer Needed
• DIY Automation vs. Hiring a Make Partner in 2026: When to Do Each
• Manual Data Entry: The Silent Killer of Business Productivity and Profit
• Make vs Zapier: A Straight Pricing and Feature Breakdown for 2026
• Implement AI Workflow Automation: A Step-by-Step Business Guide
• What Is OpsMap? The Discovery Step That Prevents Automation Mistakes