How to Connect Omnisend to WordPress


In this video, you will learn how to install WP Fusion and set up a direct connection to your Omnisend account. To get started install and activate the WP Fusion plugin, then navigate to Settings » WP Fusion.

From the ‘Select Your CRM’ dropdown choose ‘Omnisend’.

To enable the connection to Omnisend we need to locate your API Key.

This can be found by logging into your Omnisend account and clicking on Store Settings

Then choose ‘API Keys’ and click ‘Create API key’.

Copy the API key and paste it into the appropriate field in WP Fusion. Then, click on ‘Connect’.

WP Fusion will now establish a direct connection to your Omnisend account and import your tags and custom fields. To finalize the process click on ‘Save Changes’.

#Connect your store to Omnisend

To use automations, first you need to enable Site tracking in WP Fusion.

Go to your Omnisend account, navigate to Automation, and click ‘Connect your store’.

Select ‘Other’, enter your store URL, and click ‘Connect Store’.

Then click ‘Verify and Connect’.

This will check if the tracking snippet is installed and then the store is connected.

Note: In some cases it can take up to 24 hours to validate the tracking script and enable automations in Omnisend. If Omnisend was unable to automatically verify your store, you will see a banner across the top of your account.

If your store does not appear validated after 24 hours, please contact Omnisend support.


#Omnisend tags

At the moment it’s not possible to remove tags via the Omnisend API.

To get around this, when a tag is removed WP Fusion will update a custom property on the subscriber with the tag name, and the value set to false.

When loading tags, WP Fusion will also check the subscriber’s custom property values to generate an accurate list of the subscriber’s tags.

This makes Omnisend fully functional with all of WP Fusion’s features and integrations. If you would prefer not to see this custom properties in your account, you can also create an automation to remove the associated tag when the custom property is updated.

Was this helpful?