WS Form PRO Omnisend

A saved contact is not necessarily a subscriber

A quote form collects a name and an email. Another one, the newsletter, collects the same. In your contact database they end up equally well filled in, but the two people did not ask you for the same thing.

The contact's status in Omnisend is a setting of the action, so each form can create a subscriber or a non-subscribed contact.

The Omnisend integration for WS Form Pro adds an action that creates contacts in your account. Its Status setting takes three values: Subscribed, Unsubscribed and Non Subscribed. That way each form on the site decides the state the person enters with, instead of inheriting the same one for everybody.

What the Omnisend action does

• When it runs: on save, on submit or in both cases.
• Opt-in field: the field that serves as opt-in; a single checkbox that starts unchecked is the natural choice.
• Status: Subscribed, Unsubscribed or Non Subscribed.
• Send Welcome Email: asks Omnisend for the welcome email, which only goes out if the welcome workflow is turned on in your account.
• Field mapping: pairs a form field with an Omnisend field, for example email with email.
• Custom mapping: assigns an Omnisend field a fixed value or a WS Form variable, useful for a hidden field with the contact's source.
• Custom properties: name and value pairs added to the contact. The name only accepts Latin characters, numbers and underscores, and can carry WS Form variables.
• Tags: you add them one by one to organize contacts.

An idea of use: a quote form with Status on Non Subscribed

Imagine a quote request form whose data you want in Omnisend without the person entering as a subscriber. With Status on Non Subscribed, a custom property naming the service requested and a tag with the form's name, the contact is identified and classified.

This is only a starting point; adjust it to your forms.

For the newsletter the approach changes: Status on Subscribed, an unchecked consent box and, if you want the welcome email, Send Welcome Email together with the workflow turned on in Omnisend.

Requirements and a welcome email detail

It works with WS Form Pro, not with WS Form Lite, and it needs an Omnisend account and an API key. That key is created in Omnisend, under Store Settings, API Keys, Create API Key.

An easy detail to miss: ticking Send Welcome Email is not enough. If the welcome workflow is off in Omnisend, the email does not go out. And because of the character rule for properties, "Service requested" will have to be written as Service_requested.

Connecting to the Omnisend account

1. Install the add-on the same way as WS Form Pro.
2. In Omnisend, open Store Settings, API Keys, press Create API Key and copy the key.
3. In WS Form, Settings, Omnisend tab, paste the key and save.
4. For a ready-made form, go to WS Form, Add New, Omnisend tab, Contact template. If it does not appear, use the refresh icon.
5. For an existing one, open the Actions icon, the Add icon and choose Add to a Omnisend; set Status and the mapping, and save.

Email connectors in the catalog

For the base form plugin, see WS Form Pro. If you work with other email services from a form, the catalog includes Ninja Forms Constant Contact Extension and WPForms Mailchimp Addon.

Answers about WS Form Omnisend

Which states can the contact created by the action have?

Subscribed, Unsubscribed or Non Subscribed, chosen in the Status setting.

Why does the welcome email not go out?

Omnisend only sends it if the welcome workflow is turned on in your account.

What do I need from Omnisend to connect?

An account and an API key created in Store Settings.

Can I keep the contact's source?

Yes, with a custom mapping or with a custom property that carries a fixed value or a variable.

Does it work with WS Form Lite?

No. It requires WS Form Pro.