Ecomail

A complete email marketing integration that connects Fluent Forms with Ecomail, a popular marketing platform for small businesses in Central Europe. This integration allows you to automatically add form submissions to your Ecomail campaigns with advanced field mapping, double opt-in support, and conditional logic.

Setup instructions

1. Enable the integration in Form Enhancer
   • Navigate to WordPress Dashboard → Settings → Form Enhancer → Fluent Forms tab
   • In the Integrations section, toggle Ecomail Integration on. It is a PRO feature and is switched off by default — until it is on, Ecomail does not appear anywhere in Fluent Forms.
2. Connect your Ecomail account
   • Navigate to Fluent Forms → Integrations, locate the Ecomail card and toggle it on.
   • Click the settings (cog) icon — it takes you to Fluent Forms → Global Settings → Ecomail Settings.
   • Now paste the Ecomail API key that you grab from Ecomail → Account (Správa účtu) → For Developers (Pro vývojáře) → the API key (API klíč) section. Do not share it.
   • The system will immediately check if the key is correct and if the connection is working. If there’s an issue (e.g., if you type random stuff), you’ll see an error message. If it works, you’re connected and on the safe side.
3. Add the Ecomail Integration to a Specific Form
   • Choose the Fluent Form you want to use to send information to Ecomail.
   • Go to that form’s Settings & Integrations tab, then click on “Integrations“.
   • Click on Add a new Integration and select Ecomail Feed from the list.
   • Give this integration a name you’ll recognise (e.g., “Website Newsletter Signups”).
   • Select the specific Ecomail list where you want new contacts from this form to be added.
   • Match your form fields to your Ecomail fields (this is called “mapping”):
     •  For example, connect your form’s “Email” field to Ecomail’s “Email” field.
     •  If your form has “Name” or “Surname” fields, match them to the correct fields in Ecomail. You will also see any custom fields you have enabled in Ecomail.
     •  Always pick the form field from the dropdown next to each input — it inserts a smart code like {inputs.email}. Sub-fields of the Address field (City, ZIP, …) are available in the dropdown too. Hand-typed input names are not smart codes and would be sent to Ecomail as literal text.
     •  Click the “Save” button to store these settings.

How Data is Sent and Checked

After someone fills out your form, the information isn’t sent to Ecomail right away. It’s usually a scheduled cron action that runs in the background when the website is not busy, ensuring no delay for your visitors. You need to wait a couple of seconds.

You can check if the data was sent by looking at the “Entry Details” for your form submissions in the API calls section. You might first see “pending,” meaning it’s waiting to be sent. If you refresh, it should change to “success” or “failure“.

Troubleshooting

If it fails, you’ll get a description of what went wrong (e.g., you sent a string to a number field). If you fix the problem, you might see an option to “resend” the data.

When a single mapped value can’t be sent — a birthday that isn’t a valid date, a gender that isn’t male or female — the contact is still created, and an info entry “Some mapped fields were not sent to Ecomail” is added to the entry’s Submission Logs with the reason. One unusable value never costs you the subscriber.

Feed options

Besides the field mapping, each Ecomail feed offers these options:

• Double Opt-in – Ecomail sends the contact a confirmation email and only subscribes them once they confirm. Note that Ecomail welcome automations and autoresponders fire only after the contact confirms.
• Trigger Autoresponders – triggers your Ecomail autoresponders when the subscriber is added to the list.
• Trigger Notifications – triggers Ecomail notifications when the subscriber is added to the list.
• Update Existing – updates a contact that already exists in the list. Only fields with a submitted value are sent, so the contact’s existing data in Ecomail is never erased by unmapped or empty form fields.
• Tags – a dedicated comma-separated input (e.g. new lead, web). Supports smart codes like {inputs.field_name} and dynamic conditional routing. When updating an existing contact, tags are merged with the contact’s existing tags so nothing is lost (disable via the formenhancer/fluentform/ecomail/merge_existing_tags filter).
• ReSubscribe – re-adds contacts who are inactive or previously unsubscribed. Use with caution and only when appropriate.

Supported Ecomail Fields

• Standard Fields
  • Name (Jméno)
  • Surname (Příjmení)
  • Email (required)
  • Gender (Pohlaví) – Ecomail stores male or female. Your form doesn’t have to: Muž/Žena, M/F, Male/Female, Mr/Mrs and their upper- and lower-case variants are recognised and converted. A value that fits neither (e.g. “Prefer not to say”) is skipped and logged, and the rest of the contact is still sent — teach it your own wording with the formenhancer/fluentform/ecomail/gender_aliases filter.
  • Company (Společnost)
  • Phone (Telefon)
  • Birthday (Narozeniny) – automatically converted to the YYYY-MM-DD format Ecomail requires. The mapped date field’s own configured format is used first, then YYYY-MM-DD, DD.MM.YYYY, D. M. YYYY, DD/MM/YYYY and MM/DD/YYYY; anything else is parsed as a last resort. Ambiguous values such as 03/04/1990 are read day-first (3 April). A value that can’t be read as a date is skipped and logged (see Troubleshooting).
• Address Fields
  • Street (Ulice)
  • City (Město)
  • Country (Země)
  • ZIP (PSČ)
• Advanced Fields
  • Source (Zdroj) – defaults to fluent_forms when not mapped, so contacts always carry a source in Ecomail; customizable via the formenhancer/fluentform/ecomail/default_source filter
  • Vokativ – first name in the Czech vocative (5th case), Ecomail merge tag *|VOKATIV|*
  • Vokativ S – surname in the Czech vocative, Ecomail merge tag *|VOKATIV_S|* (e.g. “Vážená paní *|VOKATIV_S|*,”)
  • Nameday (Svátek) – automatically converted to the MM-DD format Ecomail requires, the same way as Birthday
  • Pre Title (Titul před)
  • Sur Title (Titul za)
  • Tags – configured via the dedicated Tags feed option (see Feed options above), not in the field mapping. Feeds created before version 1.3.1 kept their tags inside the mapping; those are moved into the Tags option automatically, so there is nothing to do by hand. (A feed that uses dynamic tag routing is left as it is — there the routing decides the tags.)
• Custom Fields – Any custom fields configured in your Ecomail list will automatically appear in the field mapping options.

Developer filters

Three filters let you adjust the integration in code: merge_fields adds, renames or removes rows in the field mapping, default_source changes the source sent when the Source field is not mapped, and merge_existing_tags restores Ecomail’s own behaviour of overwriting a contact’s tags instead of merging them.

add_filter('formenhancer/fluentform/ecomail/merge_fields', function ($fields, $listId) {
    unset($fields['vokativ_s']);
    return $fields;
}, 10, 2);

add_filter('formenhancer/fluentform/ecomail/gender_aliases', function ($aliases) {
    return $aliases + ['pán' => 'male', 'paní' => 'female'];
});

add_filter('formenhancer/fluentform/ecomail/default_source', function ($source, $feedData, $form) {
    return 'website_form';
}, 10, 3);

add_filter('formenhancer/fluentform/ecomail/merge_existing_tags', '__return_false');