Connect Gravity Forms. Send every lead to Benchmark Email.

How the Gravity Forms Benchmark Email integration works

Set up the Gravity Forms Benchmark Email integration with ClickSyncr for Benchmark Email. Choose a list in the form’s settings, map the contact data, and decide whether visitors must consent before the plugin sends anything.

Each form has its own connection and destination. These steps follow the plugin code checked on 10 November 2026.

Prepare the form and account

You need WordPress, an active Gravity Forms installation, and permission to install and configure plugins. Have a Benchmark Email account and credentials for the platform your account uses. Classic keys and new-platform keys follow different connection paths. Prepare an email input and a consent checkbox if subscriptions require permission.

Install the named plugin

In WordPress, open Plugins > Add New. Search for ClickSyncr for Benchmark Email – Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms, Formidable & Forminator. Choose Install Now, then Activate.

Connect the account in Gravity Forms

Open the Gravity Forms form’s Settings and choose ClickSyncr for Benchmark Email. Create or edit its feed and enter a Feed Name. Connect the account, select the list, and map the inputs. The feed also has Conditional Logic, so review any conditions before saving and testing it.

For a classic account, open Benchmark Email, Integrations, API and copy the key. For a key beginning with bme_, open Benchmark Settings > API Keys. Copy both the key and its HTTPS API base URL. Enter that URL in API base URL; the current settings code requires contacts:write permission for this connection. Click Connect to verify and save the credential. Then select the Benchmark Email list that should receive this form’s submissions.

Match the fields you want to send

For a classic list, the mapping code includes FirstName, MiddleName, and LastName. It then reads the selected list’s named custom slots, Field1 through Field24, with text, number, boolean, or date types. A list’s actual labels determine which choices appear. New-platform accounts load field labels and requirements from the selected contact structure; map the required fields shown for that structure.

Gravity Forms exposes individual inputs from compound fields in the mapping choices. Use the specific name input you want to send, rather than assuming every part of a Name field becomes one value. The field labels help distinguish those inputs when you map Benchmark Email fields. Leave optional fields unmapped when the form does not collect that information.

Set consent and confirmation deliberately

Open Subscription and consent and choose the form’s Consent field when a visitor must opt in. A ticked choice allows the sync; an unticked choice sends nothing to Benchmark Email. Classic Benchmark lists apply their own subscription settings. The plugin does not choose a different confirmation rule for each classic subscription. With a new-platform key, the settings state that double opt-in is unavailable through that API. New contacts are Active, while existing inactive contacts stay inactive. Save the settings after choosing the behavior you need.

Test the destination and the refusal path

Submit an entry that matches any feed conditions. If a condition intentionally excludes an entry, do not treat the missing subscription as a failed connection. Use a test contact you control and compare the mapped values in Benchmark Email. If you require consent, also submit once with the checkbox unticked. Confirm that the second submission does not add a contact. Check the sync result as well as the form’s confirmation.

Use the error message to narrow the check

“Nothing was sent. This form has no API key.” means this form still needs its credential. “not configured or email missing/invalid” points to the selected destination or email mapping. “Nothing was sent. Consent was not given.” records the unticked consent path; it is not a reason to remove the consent requirement.

“Benchmark returned a different list.” means the returned list does not match the selected list. Refresh the list choices and select the intended destination again. For a new-platform key, “Enter the HTTPS API base URL from Benchmark Settings > API Keys.” points to the required account-specific URL.

The Benchmark Email integration hub covers the service across builders. Use the Gravity Forms integration guide to compare destinations for this builder. For additional product options, review ClickSyncr Pro.

When a test entry reaches Benchmark Email with the right fields and consent, the Gravity Forms Benchmark Email integration is ready for real visitors.

Frequently asked questions

How do I connect Gravity Forms to Benchmark Email?

Install ClickSyncr for Benchmark Email, then open the ClickSyncr for Benchmark Email feed under the form’s Settings. Connect the account for this form and select the list. Map Email before the optional fields, review consent, and save. Submit the public form and check Benchmark Email to confirm that the saved configuration sends the expected contact data.

Which Benchmark Email fields can I map from Gravity Forms?

For a classic list, the mapping code includes FirstName, MiddleName, and LastName. It then reads the selected list’s named custom slots, Field1 through Field24, with text, number, boolean, or date types. A list’s actual labels determine which choices appear. New-platform accounts load field labels and requirements from the selected contact structure; map the required fields shown for that structure. Recheck the saved mapping after changing the form or destination.

Can I require consent before sending Gravity Forms submissions?

Yes. Select a supported consent field from this Gravity Forms form in Subscription and consent. When you choose that field, a ticked answer allows the sync and an unticked answer sends nothing to Benchmark Email. Save the form’s settings, then test both paths with distinct test contacts so you can tell the results apart.

Does a bme_ API key work with this WordPress integration?

The current code recognises a key beginning with bme_ and uses a separate connection path. It also requires the HTTPS API base URL from Benchmark Settings > API Keys. A key alone is not enough. Check that the credential has contacts:write permission, then connect and select the intended contact list before mapping its fields.