Integration for Engaging Networks and Gravity Forms

Help! I can’t get this plugin to get any data from Engaging Networks! What should I do?

There are typically two hurdles to successfully getting this plugin and Engaging Networks to communicate. The first and most common problem is that the API key you’ve entered isn’t properly configured to be used from the IP address of the server you’re using this plugin on — make sure to check with your host if you have questions about what IP address to enter into Engaging Networks.

A second, less-common problem is that your EN account is on a different server than this plugin assumes. If you normally log in to your Engaging Networks account at us.e-activist.com, us.engagingnetworks.app, or ca.engagingnetworks.app, you’ll need to change the “EN URL” setting in the plugin settings (Forms > Settings > Engaging Networks) to the appropriate URL. If you log in at either e-activist.com or www.e-activist.com, use the default URL setting (www.e-activist.com).

In the unlikely event that your EN account is on a server other than www.e-activist.com, us.e-activist.com, us.engagingnetworks.app, or ca.engagingnetworks.app, you’ll need to add some code to your site (either in your theme or a plugin) to set the URL using a filter. The filter is called gf_en_api_base_url and here’s an example use:

function mytheme_change_en_url( $url ) {
    return 'https://mars.engagingnetworks.app/ens/service';
}
add_filter( 'gf_en_api_base_url', 'mytheme_change_en_url' );

Does this work with Ninja Forms, Contact Form 7, Jetpack, etc?

Nope. This is specifically an Add-On for Gravity Forms and will not have any effect if installed and activated without it.

What version of Gravity Forms do I need?

You must be running at least Gravity Forms 1.9.3.

What kinds of data can this pass to Engaging Networks?

As of 2.0, this Add-On can pass basic constituent data to EN as well as Page Builder form submissions.

Page submissions can include custom supporter fields and Opt-Ins, although as of now the EN API does not provide a way for this plugin to “know” which fields are present or required on a given Page. (We hope the EN API will eventually expose a list of optional and required fields shown on a given Page so that we can simplifyy this Add-On’s interface and be more confident form submissions will be successful, but until then, you’ll have to wing it.)

Hide FAQ

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.