Every submission ends
on a page they can keep.

The form ends on a page that belongs to your site, with the visitor’s submitted details already in place. Its link works again when they need to look back.

Your registration Submitted
/thanks/?eid=…
Registration received Moonlight Gardening

Merry Mergefield

Your submitted details appear in this site’s own page layout.

Save the link. Return to the same registration.

Illustrative experience

  • Submitted details in your page layout
  • A confirmation link they can keep
  • One layout across multiple forms

The finished experience

A useful record after the form is done.

One page layout shows each visitor the details from their own submission, and a saved confirmation link brings those details back.

A good fit for
Registration teams, service businesses, and anyone whose customers need to refer back to what they submitted.

  1. 1

    Create the page they should reach

    Build a WordPress page for the confirmation and choose it in the form’s Page confirmation settings. Enable Merge Tags in Page Content.

    GP Post Content Merge Tags

  2. 2

    Put their answers in the layout

    Insert the submitted fields as merge tags alongside your next-step instructions. To share the page across forms, use global label-based tags and keep the corresponding field labels consistent.

    GP Post Content Merge Tags

  3. 3

    Give them a way back

    Use the confirmation URL in the notification so the visitor can save it. The entry identifier in the URL lets the page display the same submission when they return.

    GP Post Content Merge Tags

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

Taking it further

Add these optional plugins when your project calls for more.

Before you start

  • A published confirmation page. Keep the entry available for its confirmation page to read.
  • Use matching field labels or admin labels when multiple forms share a page. Page builders may need the [eid] shortcode around merge-tag content.
  • For owner-only access, require signed-in submissions and install the free Lock Down by Entry Creator snippet; a saved link alone does not require a login.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

  • GP Post Content Merge TagsPerks

Optional

Gravity Perks Basic $59 /year

Covers this on one site. More sites need Advanced or Pro.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

Can several forms use the same confirmation page?

Yes. Use global merge tags matched by field label instead of one form’s field IDs. The corresponding labels must match across forms; consistent admin labels can keep the template stable while visible labels change.

Will this work in a page builder?

Merge tags normally run through WordPress’s content filter. If your visual builder does not use that filter, wrap the content in the [eid] shortcode where shortcodes are supported. Dynamic blocks such as ACF blocks may need the additional filter snippet shown in the plugin’s Known Limitations documentation.

Is the saved page private to the person who submitted?

The entry ID is obfuscated in the URL, but that is not a login requirement. For entries created while signed in, the Lock Down by Entry Creator snippet permits the original creator and staff with permission to edit entries. Require signed-in submissions for that setup; it does not provide owner-only protection for guest entries.

  • Clay, CTO
  • Dan, Content Sorcerer
  • Dani, Product Manager
  • David, Founder & CEO
  • Matt, Senior Support Wizard
  • Roxy, Support Wizard

Not quite your build?

Tell us what you are making and we will work out which pieces it takes — or tell you straight if this is not something we can do.

Ask the wizards