When Gravity Forms saves an entry but displays the wrong success message or thank-you page, inspect the confirmation rules against that entry's actual values. Editing email notifications will not fix the browser's confirmation branch.
Identify which confirmation ran
Give each confirmation an administrative name that describes its purpose, such as Sales enquiry, Support request and Default receipt. On staging, use a short, distinct test sentence in each branch so you can identify the selected one without guessing from the destination design.
Gravity Forms distinguishes on-page or redirect confirmations from email notifications. The default confirmation remains available as a fallback when additional confirmation rules do not apply. Its conditional behavior differs from additional confirmations.
Capture one controlled entry ID, the form ID and the fields involved in the rule. A visible choice label and its stored value may differ. A rule built around the label you remember is not sufficient evidence about the value the submission actually supplied.
Make the branches unambiguous
Read the conditional-confirmation documentation alongside the installed form configuration. Prefer mutually exclusive rules. Do not depend on an undocumented ordering assumption when two branches could both match.
| Test submission |
Intended result |
Evidence to retain |
| Enquiry type is Sales |
Sales confirmation |
Stored choice value and branch name |
| Enquiry type is Support |
Support confirmation |
Same two details |
| Choice omitted when permitted |
Default receipt |
Empty value and default result |
| Another condition contradicts the first |
Explicitly defined branch or fallback |
Complete rule evaluation |
Review whether the rule requires all conditions or any condition. A sales rule that matches Sales OR a broadly shared country can accidentally capture support enquiries from that country.
Entry: Stored values inspected. Branches: All / any logic reviewed. Fallback: Clear default acknowledgement. Destination: Correct safe URL opens. Explanatory checklist, not a customer test result.
Separate routing from destination failures
If the right branch selects the wrong page, check the selected page or redirect URL. If the page list is incomplete, Gravity Forms notes that REST API restrictions can affect the page selector. Do not disable the entire security layer; identify the blocked request and the specific policy.
If the right URL receives a 404, inspect its query parameters. Reserved WordPress names can alter routing. Avoid passing names, phone numbers or email addresses through a thank-you URL merely to personalize a message. Such URLs can be retained in browser history, logs and analytics.
If the form has multiple embeds, reproduce the same page, popup and AJAX configuration as the complaint. A second form with a similar title may have different confirmation settings.
Verify without contacting real leads
Test with controlled addresses and mark the submissions as tests. Check that every permitted route displays a clear acknowledgement, that the fallback does not claim a task was completed when it was only received, and that one submission does not produce duplicate conversion events.
Use our notification diagnosis if the missing acknowledgement is actually an email. HandL WP can repair conditional routing when legacy rules, multiple embeds and custom callbacks make the selected branch hard to explain.
References reviewed October 8, 2026. Examples are explanatory, not customer test results.