GetResponse Integration

3 min readUpdated June 20, 2026

GetResponse is an email marketing platform with a strong set of automation and campaign management tools. WP Smart Consent integrates with GetResponse via the Contacts API v3, forwarding opted-in contacts to your selected campaign in real time.

Enabling the Integration#

In the WP Smart Consent dashboard, go to CRMs & ESPs, find the GetResponse card, and open the Connection tab. Paste in your API key and toggle the integration on, then save. WP Smart Consent connects to your account and populates the list picker with your available campaigns.

To generate an API key, log into GetResponse and go to Tools → Integrations & API → API, then create a new key.

Custom Fields#

GetResponse custom fields are referenced by their system-assigned customFieldId, not a human-readable slug. To find a custom field’s ID, go to Contacts → Custom fields in GetResponse, open the field, and check the URL or use the GetResponse API explorer.

In WP Smart Consent’s Custom fields tab, add a row, select the WPSC source field on the left, and enter the GetResponse customFieldId as the destination key. WP Smart Consent sends these as customFieldValues in the API payload, formatted as [{customFieldId, value}].

A screenshot of the GetResponse integration settings page. The "Custom fields" tab is selected, showing an option to add a custom field and a green "Save GetResponse" button below. The integration status is set to "Inactive" in the top right.

Field Mapping#

The Field mapping tab maps WPSC fields to GetResponse contact properties. GetResponse’s contact model is minimal — the API accepts email, name (a combined first + last string), and customFieldValues. First name and last name are joined automatically into the name field. Additional fields beyond those are sent as custom field values using the destination key as the customFieldId.

How It Works#

WP Smart Consent sends a POST to https://api.getresponse.com/v3/contacts for each selected campaign. GetResponse’s contact endpoint is scoped to one campaign at a time, so if multiple campaigns are selected the call is made once per campaign. Authentication uses the X-Auth-Token: api-key {KEY} header format.

If a contact is already subscribed to the campaign, GetResponse returns error code 1008. WP Smart Consent treats this as a success and continues without logging an error.

Options#

The Options tab has three settings.

Update existing contacts — controls whether existing contacts are updated on each opt-in.

Send on unchecked — when enabled, contacts are forwarded to GetResponse even when the opt-in checkbox was not ticked.

Tags — a comma-separated list of GetResponse tag IDs to apply to every contact. Tags in GetResponse are referenced by their ID, not name. Find tag IDs in Contacts → Tags or via the GetResponse API.

Screenshot of the GetResponse Options tab. “Update existing contacts” toggle is on, “Send on unchecked” is off. There’s a text box labeled “Tags” with a placeholder for comma-separated tags. Bottom left shows a green “Save GetResponse” button.

Troubleshooting#

Campaign list not populating — confirm the API key is correct and saved. The list is fetched from GET /v3/campaigns at save time. A wrong key returns a 401 and the list stays empty.

Contact not appearing in campaign — check the WPSC Logs tab to confirm the opt-in event fired. If it did, check the GetResponse campaign’s subscriber settings — campaigns can be configured to reject contacts that don’t meet certain conditions.

Custom field values not saving — confirm the destination key is the GetResponse customFieldId, not the field label. IDs are numeric strings assigned by GetResponse.