Thank You Page Redirect Pattern

Overview

When a user submits a form on a WordPress site, the default behavior for many form plugins is to display an inline success message on the same page — the page "refreshes" and a confirmation appears in place of the form. This pattern consistently causes user confusion: visitors perceive the page as having "popped back up" or failed to process their submission, because the surrounding page content remains visible and unchanged.

The recommended pattern is to redirect the user to a dedicated Thank You page after form submission. This provides a clear, unambiguous confirmation that their action was completed.

The Problem with Inline Success Messages

• The page never actually navigates away — the URL stays the same and the surrounding content remains visible
• Users interpret the refresh as a failure or loop, not a success
• There is no clear "you are done" signal; the form area simply transforms in place
• Clients and end-users frequently report this as a bug even when it is working as intended

From the field: During a VCEDC Events Connect review, the client reported that "when you submit your form, everything just pops right up again." The team confirmed the inline message was functioning correctly, but the UX perception was of a broken flow. The fix was to redirect to a dedicated Thank You page. See ^[1].

The Solution: Dedicated Thank You Page

Implementation (Gravity Forms + WordPress)

1. Create a standard WordPress page titled "Thank You" (or event-specific equivalent). Keep it simple — a short confirmation message is sufficient.
2. Write clear confirmation copy. Example:

   Thank you for registering. We look forward to having you attend our event. Should you have any questions, or if we can ever be of service, please feel free to contact [Name] at [email].
   - Make the contact email a clickable mailto: link

3. Configure the form to redirect to this page on successful submission (in Gravity Forms: Form Settings → Confirmations → set type to "Redirect" and enter the Thank You page URL)
4. Exclude the Thank You page from site navigation so it is only reachable via form submission redirect

Why This Works

• The browser navigates to a new URL — users receive an unambiguous signal that something happened
• The Thank You page can be bookmarked, shared, or revisited without re-triggering the form
• It cleanly separates the "registration experience" from the "confirmation experience"
• It is a familiar, expected pattern for users across the web

What Not to Put on the Thank You Page

Some features that seem natural on a Thank You page are technically constrained:

• "Add to Calendar" widgets — calendar plugins that pull event data (date, time, location) from the originating event page cannot access that data on a separate Thank You page. The widget will render broken or empty. If calendar functionality is needed, it should remain on the event page itself, or a static .ics download link should be used instead.

From the field: The VCEDC team attempted to move an "Add to Calendar" plugin widget to the Thank You page redirect. Ishaque confirmed the widget requires event data from the source page context and cannot function independently. The feature was removed entirely, as it was non-essential and had not existed in the client's prior workflow.

Reusable Workflow Considerations

When the same Thank You page serves multiple events or campaigns:

• A single generic Thank You page can be reused across events if the confirmation copy is not event-specific (e.g., "Thank you for registering — watch your email for details")
• If event-specific details are needed on the Thank You page, create a separate page per event
• The form redirect URL must be updated each time a new form is created for a new event

For per-event form management in Gravity Forms, see ^[2].

Related

• ^[1]
• ^[2]