Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Gravity Forms Confirmation Redirect Not Working: Causes and How to Fix It

Gravity Forms Confirmation Redirect Not Working: Causes and How to Fix It

Short answer

A Gravity Forms redirect usually fails because the confirmation type is still set to Text, a conditional confirmation runs first, or the URL is wrong. AJAX script errors, caching and custom code that filters the confirmation can also stop the redirect from happening.

Key takeaways

  • Set the confirmation type to Redirect and use a full https URL.
  • Conditional confirmations run before the default one.
  • JavaScript errors with AJAX often stop the redirect.
  • Exclude form pages and scripts from caching and script delay.
  • Search custom code for confirmation filters that override settings.

Why is the Gravity Forms confirmation redirect not working?

The redirect usually fails because the confirmation type is not set to Redirect, a conditional confirmation overrides it, AJAX or caching interferes, or a plugin or theme script breaks the page.

You might notice one of these symptoms:

  • The form submits but shows the default Thanks for contacting us message instead of moving to a new page.
  • The page reloads and stays on the same form.
  • The redirect works for you but not for logged-out visitors.
  • The visitor lands on the wrong page or a 404.
  • The redirect URL is missing the query string values you expected.

Each symptom points to a different cause. Work through the checks below in order, because the first three fix most cases.

If the form itself will not submit at all, start with our guide on the Gravity Forms submit button not working first.

Is the confirmation type actually set to Redirect?

Open the form, go to Settings > Confirmations, edit the confirmation, and make sure the type is Redirect with a full, valid URL saved.

Gravity Forms gives each confirmation three types: Text, Page and Redirect. The Gravity Forms confirmations documentation explains each one.

Here is what to check:

  1. Go to Forms and hover over your form.
  2. Click Settings, then Confirmations.
  3. Edit the Default Confirmation (or whichever one you expect to run).
  4. Choose Redirect as the confirmation type.
  5. Paste the full URL, including https://.
  6. Click Save Confirmation.

A common slip is editing the confirmation but leaving the type on Text. Another is pasting a relative path like /thank-you/ instead of a full URL. Use the full address to rule that out.

If you only need to send people to a page on the same site, the Page type is often more reliable. It picks a page from a dropdown, so the link cannot be mistyped.

Could another confirmation be running instead?

Yes, if a form has more than one confirmation with conditional logic, Gravity Forms runs the first one whose conditions match, which may not be your redirect.

Gravity Forms lets you add extra confirmations that only fire when certain field values are selected. The default confirmation runs only when none of the conditional ones match.

Check these points:

  • Open the Confirmations list and look for more than one entry.
  • Check whether any conditional confirmation is active and matches the test values you submitted.
  • Confirm your redirect is on the confirmation that should run for your test.

Conditional confirmations often use the same field logic as the form. If you have trouble with that logic, our guide to Gravity Forms conditional logic not working covers the usual mistakes.

Is the redirect URL built correctly?

A redirect URL with a typo, a missing scheme, spaces or a broken merge tag can send visitors to a 404 or nowhere at all.

Look closely at the URL field:

  • Scheme: it should start with https://.
  • Spaces: a trailing space can break some redirects.
  • Merge tags: if you add field values to the URL, make sure each merge tag points to a field that still exists.
  • Encoding: values with spaces or special characters should be URL encoded. MDN explains percent-encoding if you need a refresher.

Gravity Forms has a Pass Field Data Via Query String option in the redirect settings. It adds field values to the end of the URL. If a field was deleted or renamed, the merge tag can come through empty.

Test the URL by pasting it into a browser on its own. If it fails there, the problem is the URL, not the form.

Is AJAX submission causing the problem?

AJAX submissions can fail to redirect when a JavaScript error, script delay or optimization plugin stops Gravity Forms from processing the response.

When a form is embedded with AJAX turned on, Gravity Forms sends the data in the background and then tells the browser where to go. If a script breaks along the way, the browser never gets that instruction.

To test this:

  1. Open the page with your browser's developer tools on the Console tab.
  2. Submit the form.
  3. Look for red JavaScript errors.

WordPress.org has a short guide to using your browser to diagnose JavaScript errors if you have not done this before.

If you see errors, the cause is often a script optimization setting. Read our guide to Gravity Forms AJAX not working for the specific fixes.

A quick test is to embed the form without AJAX. In the block editor, open the Gravity Forms block settings and turn AJAX off. If the redirect then works, the problem is on the JavaScript side.

Are caching or script optimization plugins in the way?

Caching and optimization plugins can serve an outdated copy of the form or delay the scripts that handle the redirect, so exclude the form page and Gravity Forms scripts.

Look at these settings in your performance plugin:

  • Delay JavaScript execution: exclude Gravity Forms and jQuery.
  • Combine or minify JavaScript: exclude Gravity Forms files.
  • Page cache: exclude the form page if the redirect works when you are logged in but fails for visitors.

Logged-in users often bypass the page cache. That is why a redirect can work for you but fail for everyone else.

After changing settings, clear every cache layer, including any server cache and CDN. Our guide on how to clear cache in WordPress walks through each layer.

Is a plugin or theme conflict blocking it?

A plugin or theme that hooks into form submission or changes redirects can override the Gravity Forms confirmation, so test with other plugins turned off.

Some plugins change where WordPress sends users after an action. Membership plugins, login redirect tools and some security plugins are common examples.

The safest way to test is on a staging copy:

  1. Switch to a default theme such as Twenty Twenty-Five.
  2. Deactivate every plugin except Gravity Forms.
  3. Submit the form and check the redirect.
  4. Turn plugins back on one at a time until it breaks.

The full method is in our guide to fixing a plugin conflict. Gravity Forms support also asks for this test before looking deeper.

Has custom code changed the confirmation?

Code using the gform_confirmation filter can replace or rewrite the confirmation, so check your theme's functions file and any snippet plugins for it.

The gform_confirmation filter reference shows how developers can return a redirect, a message or custom output. If an old snippet targets your form ID, it can override what you set in the form settings.

There is also a filter that can stop a redirect on purpose. The gform_suppress_confirmation_redirect hook lets code turn the redirect off. Search your code for both names.

Places to look:

  • Your child theme's functions file.
  • A code snippets plugin.
  • Must-use plugins in the wp-content folder.
  • Add-ons that add their own confirmation handling.

If you are not sure what a hook does, our guide to WordPress hooks, actions and filters explains the basics.

Is the redirect blocked by a server or redirect rule?

Server redirect rules, a redirect plugin or an HTTPS mismatch can bounce the visitor away from the target page after Gravity Forms sends them there.

If the visitor arrives at the wrong page, the form may be working fine. Something else changes the address after the redirect.

Check for:

  • Rules in a redirect plugin that match your thank-you page.
  • Rules in the .htaccess file or server config.
  • A target page that is private, in draft, or password protected.
  • An http link on an https site, which adds an extra hop.

If the browser shows a loop error, see our guide on fixing too many redirects.

Quick reference: symptom, likely cause and fix

Use this table to match what you see with the most likely fix.

SymptomLikely causeFix
Default text message showsType still set to TextSet type to Redirect and save
Wrong page for some answersConditional confirmation matchedReview confirmation order and logic
Page reloads, no redirectJavaScript error with AJAXCheck console, exclude scripts from delay
Works logged in, fails for visitorsPage cacheExclude form page, clear cache
Lands on 404Bad URL or deleted pageFix the URL or use Page type
Query values missingBroken merge tagsRe-add merge tags for current fields
Redirect replaced by textCustom code filterSearch for gform_confirmation snippets

What should you send to Gravity Forms support?

If the redirect still fails, send support your Gravity Forms version, the form export, the redirect settings, any console errors and the result of a conflict test.

Gravity Forms includes a System Status page under Forms > System Status. Copying that report saves a lot of back and forth.

It also helps to turn on debug logging, as described in the WordPress debugging handbook. Our guide on how to enable debug mode in WordPress shows how to capture PHP errors that might explain the problem.

Include the exact steps you took, what you expected, and what happened. A short screen recording of the submission is often the fastest way to show the issue.

Frequently asked questions

Why does my Gravity Forms redirect work for me but not visitors?

This usually points to page caching. Logged-in users often skip the cache, so they see a fresh form that redirects correctly. Visitors may get an old cached copy. Exclude the form page from caching, clear all caches, and test again in a private browser window.

Should I use the Page or Redirect confirmation type?

Use Page when the thank-you page is on the same WordPress site, because you choose it from a list and cannot mistype the address. Use Redirect when you need to send people to an external site or add field values to the URL as a query string.

Can I redirect to different pages based on answers?

Yes. Add extra confirmations in the form settings and give each one conditional logic based on field values. Gravity Forms runs the first conditional confirmation that matches, and uses the default confirmation only when no conditions match.

Why are field values missing from my redirect URL?

The merge tags in the query string probably point to fields that were deleted, renamed or left empty. Open the redirect settings, remove the old merge tags, and insert them again from the merge tag picker so they match your current fields.

Does turning off AJAX fix redirect problems?

It can help you find the cause. If the redirect works with AJAX off, a JavaScript error or optimization setting is breaking the AJAX response. You can leave AJAX off, or fix the script conflict and turn it back on.

Sources

  1. Confirmations Gravity Forms
  2. gform_confirmation Gravity Forms
  3. gform_suppress_confirmation_redirect Gravity Forms
  4. Using Your Browser to Diagnose JavaScript Errors WordPress.org
  5. Debugging in WordPress WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.