Integration for Engaging Networks and Gravity Forms Plugin

If you’re using the Gravity Forms plugin, you can now integrate it with the Engaging Networks platform. This Add-On supports creating or updating basic supporter records, either as standalone or within the context of EN Page Builder pages.

To use this Add-On, you’ll need to:

1. Have an licensed, active version of Gravity Forms >= 1.9.3
2. Have a working Engaging Networks instance
3. Configure your Engaging Networks account to have an API key and support connections from your server’s IP address(es).

If you meet those requirements, this plugin is for you, and should make building new forms and passing supporter data into EN much easier than manually mucking with HTML provided by Engaging Networks.

Initial development of this plugin was funded in part by Access Now. Subsequent development was funded in part by Amnesty International USA.

Need custom support on Engaging Networks or WordPress? Contact Cornershop Creative to get help with a custom designed donation form, email marketing support, or supporting your WordPress website. Contact us.

1. Log into your WordPress account and go to Plugins > Add New. Search for “Gravity Forms Engaging Networks” in the “Add plugins” section, then click “Install Now”. Once it installs, it will say “Activate”. Click that and it should say “Active”. Alternatively, you can upload the gravityforms-en directory directly to your plugins directory (typically /wp-content/plugins/)
2. Navigate to Forms > Settings in the WordPress admin
3. Click on “Engaging Networks” in the lefthand column of that page
4. Enter your organization’s ID as well as a valid API key for your Engaging Networks account.
5. Once you’ve entered your Engaging Networks account details, create a form or edit an existing form’s settings. You’ll see an “Engaging Networks” tab in settings where you can create a feed. This allows you to pick and choose which form fields you’ll send over to EN from the form, including the Page Builder page to assign responses to. You also have the option of setting some conditional logic to pick and choose which information gets sent.

2.2.7

• Fixed a bug that could cause supporter data not to be sent to Engaging Networks if a user submitted a form that had opt-ins mapped to form inputs, but the user left all opt-in fields empty or unchecked.

2.2.6

• Added a warning to all Gravity Forms-related pages when the plugin is running on a server that doesn’t support any of Engaging Networks’ required TLS ciphers

2.2.5

• Fixed potential fatal errors on sites running WordPress 6.2 and above, caused by breaking changes to the WordPress Requests library

2.2.4

• Added additional info to the plugin settings screen

2.2.3

• Fixed another bug that could cause fatal errors under PHP 8.0+ (“Uncaught ArgumentCountError”)

2.2.2

• Fixed a bug that could cause fatal errors under PHP 8.0+ (“Uncaught TypeError: count()”)

2.2.1

• Added two new options for the “EN URL” setting for the two new Engaging Networks server URLs: us.engagingnetworks.app and ca.engagingnetworks.app.

2.2.0

• Improved the context-sensitive display of mapping fields (based on EN Page type) for Gravity Forms >=2.5
• Fixed passing “Page” fields (such as Tracking ID) to Engaging Networks
• Basic coding standards cleanup

2.1.4

• Make it easier to determine if the Engaging Networks API connection did not work during the plugin setup
• Log when a API token is successfully retrieved from the Engaging networks API
• Show the website IP address on the settings page so users can easily whitelist their website when setting up a API user in Engaging Networks

2.1.3

• Bugfix to address issue with Engaging Networks accounts whose supporter email field had been renamed, which could result in supporter data not being sent to Engaging Networks.
• Notes will now be added to Gravity Forms entries when Engaging Networks feeds are processed, indicating whether or not supporter data was successfully sent to Engaging Networks.

2.1.2

• If the API auth token is expired, attempt to renew the auth token and send the form submission data to Engaging Networks

2.1.1

• Correcting datacenter labels in the admin to include hyphens. No functional changes.

2.1

• Added a new configuration setting to control for which EN datacenter is used.

2.0.71

• Updated the plugin settings page. Fixed the URL to the article that instructs users how to generate a API key for Engaging Networks.

2.0.7

• Refactored code for mapping email addresses and added a new potential EN field name for Email.

2.0.6

• Introduced gf_en_api_base_url filter to facilitate changing the base URL for connecting to the ENS API.
• Improved admin screen for inputting API key to suggest the proper IP address and remove superfluous client_id field.

2.0.5

• Bugfix to address issue with country and state fields not being properly converted to abbreviations before being sent to EN.

2.0.4

• Bugfix to address issue with passing “Opt-in” questions with empty values rather than Y or N; empty values are no longer passed to EN.

2.0.3

• Bugfix to address issue with email addresses not properly mapping to EN email fields due to capitalization inconsistencies.

2.0.2

• Bugfix to eliminate unnecessary “Register your copy of Gravity Forms” message in plugin list.

2.0.1

• Bugfix for handling field mapping of email address under some circumstances.

2.0.0

• Support introduced for Engaging Networks’ Page Builder system, which deprecates previous campaigns. This support includes the ability to identify which Page a given form should submit to as well as the ability to map Opt-Ins and custom supporter fields.

1.1.2

• Initial public release.