gwp_eeid
The gwp_eeid merge tag enables the retrieval of entry properties using an encrypted entry ID from a URL parameter. It provides a secure way to display dynamic Gravity Forms entry data on confirmation pages, posts, or WordPress pages, without exposing raw IDs. This merge tag is designed for browser-based output and is not suitable for emails.
Usage of the gwp_eeid merge tag
The basic syntax is:
The gwp_eeid merge tag can target either entry properties or specific field IDs, depending on your output needs.
{gwp_eeid:property}Where property can be either:
- An entry property such as id, ip, date_created, created_by, or is_approved.
- A field ID to display the value of a specific form field.
Example:
{gwp_eeid:1}This outputs the value of Field ID 1 from the entry passed via the ?eeid= parameter.
Using custom URL parameters
The gwp_eeid merge tag also supports custom URL parameters, and you can pass multiple encrypted entries to the same page. You can even pass multiple encrypted entries to the same page.
Example URL:
?eeid=encrypted-entry1&task=encrypted-entry2&entry=encrypted-entry3To access Field ID 1 from the task entry (the second parameter):
{gwp_eeid_task:1}How to pass an entry via the URL
To securely pass an entry ID, use the gwp_encrypt modifier on the entry ID. This ensures the raw ID is never exposed.
Example redirect URL in a Gravity Forms confirmation:
https://yourdomain.com/page/?eeid={gwp_entry:id:gwp_encrypt}On that page, you can display the user’s name from Field ID 1 like this:
Hello, {gwp_eeid:1}!With this redirect in place, you can safely reference values using the gwp_eeid merge tag on the destination page.
Examples with the gwp_eeid merge tag
Outputs the value of Field ID 1 from the entry in the eeid parameter:
{gwp_eeid:1}Shows the value of Field ID 2 from the entry in the task parameter:
{gwp_eeid_task:2}Returns the date_created value for the entry in the eeid parameter:
{gwp_eeid:date_created}Using modifiers with the gwp_eeid merge tag
You can apply regular or advanced modifiers to the gwp_eeid merge tag, just like you would with normal field merge tags.
Advanced chaining with gwp_eeid:
Additionally, you can chain advanced modifiers when you need to look up related entries.
{gwp_eeid_epid:7:gwp_get_matched_entry_value form_id=93 match_id=1 return_id=13}This does the following:
- Decrypts the epid parameter
- Retrieves the value of Field ID 7 from that entry
- Uses the value to find a matching entry in Form ID 93
- Returns the value from Field ID 13 of the matched entry
This creates a secure and flexible way to link related entry data.
Frequently Asked Questions
The gwp_eeid merge tag allows you to safely display Gravity Forms entry data on a page, based on a secure, encrypted entry ID passed via a URL. It’s ideal for situations where you want to personalize or show form data on confirmation pages or standalone WordPress pages without exposing raw entry IDs. This tag cannot be used in emails.
Think of it like this: you encrypt the entry ID with gwp_encrypt, send it in the URL, and gwp_eeid decodes and uses it to show specific values.{gwp_eeid:1}
This fetches the value of Field ID 1 (e.g., a user’s name) from the entry ID provided in the ?eeid= URL parameter.
Use the {gwp_entry:id:gwp_encrypt} modifier inside your form’s confirmation redirect URL to safely send an encrypted entry ID. Then, access its data using gwp_eeid on the next page.
Here’s a working example of a secure confirmation redirect:https://yourdomain.com/page/?eeid={gwp_entry:id:gwp_encrypt}
On that page, display the name from Field ID 1 like this:
Hello, {gwp_eeid:1}!
This setup ensures the entry ID is never exposed, keeping your form data secure.
Absolutely! gwp_eeid supports standard entry properties such as:
-id
-ip
-date_created
-created_by
-is_approved
These are all valid values to use in your merge tag.
Example:Submitted from IP: {gwp_eeid:ip}
Or display the date the entry was created:Submitted on: {gwp_eeid:date_created}
These are especially useful for approval workflows or logs.
You can specify custom URL parameters by inserting the parameter name after gwp_eeid_.
Let’s say your URL looks like this:https://yourdomain.com/page/?entry=ENCRYPTED_ID_STRING
Then your merge tag should be:{gwp_eeid_entry:1}
This will pull the value from Field ID 1 using the encrypted ID inside the entry= parameter.
This also works if you’re passing multiple entries on the same page using different parameters like ?eeid=…&task=…&entry=….
Yes and it’s very powerful. You can stack gwp_eeid with other advanced modifiers like gwp_get_matched_entry_value to dynamically pull related data based on a value inside the encrypted entry.
Here’s an advanced example:{gwp_eeid_epid:7:gwp_get_matched_entry_value form_id=93 match_id=1 return_id=13}
This does the following:
-Decrypts the epid parameter
-Gets the value from Field ID 7 in that entry
-Uses that value to find a match in Form ID 93
-Returns the value from Field ID 13 of the matched entry
-It’s a dynamic chain that makes secure data linking easy and readable.
Last updated: 29-08-2025
