gwp_entry
The gwp_entry merge tag of GravityWP Advanced Merge Tags returns a property of the current entry, like its ID, status or creation date, and lets you apply advanced modifiers to that value. Use it when you need an entry property in a place where a regular Gravity Forms merge tag cannot take a modifier, for example to encrypt the entry ID for a link: {gwp_entry:id:gwp_encrypt}.
Syntax
{gwp_entry:property}
{gwp_entry:property:modifier option=value}
- property (required): the entry property or field ID to return. See the table below.
- modifier (optional): any Advanced Merge Tags modifier, with its options after it. Nested modifiers (modifier1, modifier2, …) work too.
Without a modifier, the stored value is returned as is.
Entry properties
| Property | Value |
|---|---|
id | The entry ID. |
form_id | The ID of the form. |
date_created | Date and time the entry was created, in UTC, like 2025-01-31 14:46:51. |
date_updated | Date and time the entry was last updated, in UTC. |
created_by | User ID of the logged-in user who submitted the entry; empty for visitors. |
status | active, spam or trash. |
ip | IP address of the user who submitted the form. |
source_url | URL of the page where the form was submitted. |
user_agent | Browser of the user who submitted the form. |
is_starred, is_read | 1 or 0. |
currency | Currency of the entry, like USD. |
payment_status, payment_date, payment_amount, payment_method, transaction_id | Payment details, when a payment add-on processed the entry. |
| Entry meta | Values that other plugins store with the entry, like is_approved (GravityView approval status) or workflow_final_status (Gravity Flow). |
| Field ID | The stored value of a field, like 3, or of one input, like 1.3. For choice fields this is the choice value. |
An unknown property returns nothing, or the error “property does not exist” if you show errors in the plugin settings. A merge tag without a property, like {gwp_entry}, returns nothing or the error “invalid property”.
Examples
| Merge tag | Result |
|---|---|
{gwp_entry:id} | 42 |
{gwp_entry:id:gwp_encrypt} | The encrypted entry ID, safe to use in a URL for gwp_eeid. |
{gwp_entry:status:gwp_case to=upper} | ACTIVE |
{gwp_entry:date_created:gwp_substring start=0 length=4} | 2025, the year the entry was created. |
{gwp_entry:date_created:gwp_date_format field_format="Y-m-d H:i:s" field_timezone="UTC" format="d-m-Y H:i"} | The creation date in the site timezone, like 31-01-2025 15:46. |
{gwp_entry:ip:gwp_replace search="." replace="-"} | 192-168-1-10 |
{gwp_entry:id:gwp_append before="Ticket #"} | Ticket #42 |
{gwp_entry:created_by:gwp_count_matched_entries form_id=5 match_id=created_by} | The number of entries in form 5 submitted by the same user. |
Pass the entry to another page
Add the encrypted entry ID to the redirect URL of a confirmation:
https://example.com/thank-you/?eeid={gwp_entry:id:gwp_encrypt}
On that page, {gwp_eeid:1} shows the value of field 1 of this entry. See gwp_eeid.
Where gwp_entry works
gwp_entry reads the current entry, so it works where Gravity Forms has an entry: notifications, confirmations (also in a redirect URL), GravityView, Gravity Flow steps and GP Populate Anything templates. In a field’s default value the entry does not exist yet, so the merge tag returns nothing there.
date_created and date_updated are stored in UTC. To show them in another format or timezone, use gwp_date_created and gwp_date_updated, or gwp_date_format with field_timezone="UTC" as in the example above.
Frequently Asked Questions
{entry_id} only returns the entry ID and cannot take advanced modifiers; {gwp_entry:id} returns the same ID and accepts any Advanced Merge Tags modifier, like {gwp_entry:id:gwp_encrypt}.
Yes, {gwp_entry:3} returns the stored value of field 3, but a regular field merge tag like {Name:3:gwp_case to=upper} already accepts advanced modifiers and shows the formatted value, so use gwp_entry mainly for entry properties.
Gravity Forms stores date_created in UTC; use {gwp_date_created format=”d-m-Y H:i”} or add field_timezone=”UTC” to gwp_date_format to show it in the site timezone.
Yes, add nested modifiers after the first one, like {gwp_entry:ip:gwp_replace search="." replace="-" modifier1='gwp_append before="IP "'}.