Gravity Forms 文件

Enabling Conditional Logic for Confirmations

SummaryConfirmations SettingsExample

Summary

Sometimes you may want to send a user to a different page or display different information to them based on what they submit within the form. Here we will show you how to use conditional logic within your form confirmation messages.

Confirmations Settings

You will need to create a new confirmation as conditional logic is only available in additional confirmations.

Note: The Default Confirmation doesn』t have support for logic. This is intended as the form always needs to process one confirmation. The Default Confirmation will be used if the logic failed in additional confirmations.

Go to the Confirmations settings page of the form.

Here you can determine the criteria for sending the Confirmation.

Example

In this example we are using conditional logic to determine which confirmation the user should see based on their answer to the question 「Do you own a pet?」.

First we create a form with a field containing the question 「Do you own a pet?」.

Then we create a new confirmation for the people who answer yes.

Then we set the conditional logic accordingly. We set the condition to 「Do you own a pet?」 is 「Yes」.

The users who answer no will receive the default confirmation.

Emma Feed Meta

IntroductionUsagePropertiesCustom Field Properties

Introduction
The Feed Object meta for the Emma add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feed_name' => 'Your Feed Name',
'email_address' => '2',
'custom_fields' => array(),
'feed_condition_conditional_logic' => true,
'feed_condition_conditional_logic_object' => array(
'conditionalLogic' => array(),
),
);

Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.:
$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );

Properties

feed_name string
The feed name which appears on the add-ons feeds tab.

group string
The Emma Group ID this feed will add the member to.

email_address string
The ID of the form field containing the member email.

custom_fields array
A multidimensional array containing the Emma contact fields. See Custom Field Properties.

double_optin boolean
Should Emma send a confirmation email to the member. Default is false.

feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.

feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.

Custom Field Properties
array(
'key' => 'address-full',
'value' => '3',
)

Each custom field is an associative array containing the following properties:

key string
The Emma contact fields Shortcut name.

value string
The ID of the form field or entry meta item containing the value for this custom field.

Emma Change Log

1.5 | 2021-05-071.4 | 2020-09-211.3 | 2020-03-171.2 | 2017-04-281.1 | 2015-08-261.0 | 2015-04-29

1.5 | 2021-05-07

Fixed a deprecation notice with PHP 8.

1.4 | 2020-09-21

Added support for Gravity Forms 2.5.

1.3 | 2020-03-17

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added additional logging statements.
Updated the order of the API settings on the Forms > Settings > Emma page.
Updated API library to public property in support of Emma block.
Fixed PHP 7.4 notices which occur when the API is initializing and the settings are empty.
Fixed a PHP 7.4 notice which occurs on the feed configuration page when saving a new feed.
Fixed a fatal error which can occur if the Emma class is included by another plugin.

1.2 | 2017-04-28

Added security enhancements.
Added translations.
Added feed duplication support.
Fixed strings for translations

1.1 | 2015-08-26

Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Added gf_emma() for easily getting an Emma instance.
Added Spanish (es_ES) translation.
Updated 'Opt-In Condition' setting label to 'Conditional Logic'.
Updated feed processing to use get_field_value() when retrieving mapped field values, enabling support for GF_Field::get_value_export with GF 1.9.12.4 and later.
Updated feed processing to abort if email is empty or invalid.
Fixed PHP notice caused by Add-On Framework change in Gravity Forms 1.9.10.19.

1.0 | 2015-04-29

It's all new!

Setting Up the Emma Add-On

Pre-RequisitesSetup

Pre-Requisites

Download and install the add-on
An Emma account

Setup

Log into your WordPress admin dashboard.
On the left side navigation menu, hover over Forms and click on Settings.
From this page, click the Emma tab.
Enter your Public API Key, Private API Key, and Account ID. Your Emma API account information can be found by logging into your Emma account. Go to your Account Settings page and access your API key information. Please be aware that the Private API Key will only be displayed the first time it is generated by Emma, so be sure to copy-n-paste the Private API Key as soon as it is displayed.
Click Update Settings. If you』ve entered your account information correctly, you will be notified by green check marks beside each box. If you do not see green check marks, please double check this information and try again.

Once you have entered your API key, you』re ready to begin creating a feed for the Emma Add-On.

{embed_url} Merge Tag

SummaryUsage

Summary
The {embed_url} merge tag in Gravity Forms displays the URL from which the form was submitted. Gravity Forms uses merge tags to allow you to dynamically populate submitted field values and other dynamic information in notification emails, post content templates and more.
Usage
{embed_url}

{embed_post} Merge Tag

SummaryUsageMember VariablesExamples

Summary

Displays the member-variable data specified for the singular post or page from which the entry was submitted.

Note: This is not designed for use with forms embedded on blog or archive type pages.

Usage

{embed_post:[member_variable]}

Member Variables

For a list of all the member variables of a post object that you can use in your merge tag, review this WordPress reference document.

Examples

ExampleDescription{embed_post:ID}Display the ID of the post/page.{embed_post:post_title}Display the title of the post/page.{embed_post:post_author}Display the author ID of the post/page.

Below is a confirmation created with the above example merge tags:

This is what the user will see when they submit the form:

EmailOctopus Change Log

1.2 | 2020-09-081.1 | 2020-03-161.0 | 2020-01-15

1.2 | 2020-09-08

Added support for Gravity Forms 2.5.

1.1 | 2020-03-16

Added translation files
Fixed a PHP notice and warning which occur when editing an existing feed when the add-on is connected to a different EmailOctopus account.

1.0 | 2020-01-15

It's all new!

Email

SummaryCommon SettingsGeneral SettingsMerge TagsUsageModifiers

Summary

The Email field allows you to present a field that captures email data. It is available under the Advanced Fields section within the form editor.

Email field as displayed in the Field Library

Email field as displayed in the Form Editor.

Common Settings

This field uses only common field settings for the Appearance and Advanced settings. For a description of each of the common field settings, refer to this article. Below you will find description of specialty settings that are particular to this field.

General Settings

SettingDescriptionEnable Email ConfirmationPrompts the user to confirm the email address.

Merge Tags

For more information on the use of merge tags, refer to these articles.

Usage

{Field Name:2}

Modifiers

This merge tag does not have any modifiers.

Email Tracking with Postmark

By using the Postmark Add-On to send form notifications, you have the ability to take advantage of additional email features within Postmark. These features include the ability to track data within the form notifications, such as if the notification has been opened. In this article, we』ll show you how to enable tracking within your form notifications.

Access the form notification that is configured to use Postmark. If you don』t already have a notification that is using Postmark, see our article on sending form notifications with Postmark.Scroll down in the settings until you see an option labeled Email Tracking.Check the box labeled Enable open tracking for this notification to enable tracking of who has opened your form notifications.Save your settings.

That』s all there is to it! With tracking settings enabled, you will be able to better track if a form notification has been opened.

Email Tracking with Mailgun

In addition to being able to send your notifications using Mailgun, the Mailgun Add-On also includes the ability to integrate with Mailgun』s email tracking. With email tracking, you』ll be able to see if the notification was opened or links were clicked, allowing for better management of your notifications. In this article, we』ll show you how to enable email tracking in the Mailgun add-on for Gravity Forms.

Access the form notification that is configured to use Mailgun. If you don』t already have a notification that is using Mailgun, see our article on sending form notifications with Mailgun.Scroll down in the settings until you see an option labeled Email Tracking.To enable tracking of link clicks, check the checkbox labeled Enable click tracking for this notification.To enable tracking of who has opened your form notifications, check the checkbox labeled Enable open tracking for this notification.Once complete, save your notification settings.

That』s all there is to it! With tracking settings enabled, you will be able to better track if a form notification is opened or a link within the notification is clicked.