Campaigns Section Is Deprecated: Migrate to Tasks

The Campaigns section is now marked as deprecated and will be removed in a future release, although a specific timeline has not been established yet.

Why We Are Deprecating Campaigns

When we first developed Convert Forms, we introduced the "Campaigns" section to enable form submissions to be synced with third-party apps like MailChimp. Creating a campaign involved naming it, selecting the service, entering API keys, and choosing an audience list (e.g., a MailChimp list). This setup allowed users to automate their email marketing efforts efficiently.

However, over the years, several limitations became apparent:

1. No Conditional Execution: Campaigns run automatically without any conditional logic. For example, if you want to add a user to MailChimp only when they check a specific checkbox, Campaigns cannot handle this.
2. Strict Email Field Requirement: The email field in the form had to be explicitly named "email." If a form used a different name, the integration would fail.
3. Limited Field Mapping: Campaigns required specific field names (e.g., "name" for a user's name). Custom fields couldn’t be mapped flexibly, making it harder to send user data correctly.
4. Only One Integration Per Form: Each form could only be linked to a single campaign. If you wanted to send data to both MailChimp and GetResponse, it wasn’t possible.
5. Static Audience Lists: The audience list had to be predefined when setting up the campaign. If you needed to dynamically assign a user to different lists based on their input, this wasn’t possible.

What Will Be Removed

As part of the deprecation process, the following elements and functionality will be removed:

• The entire Campaigns section in the backend.
• The Collect Submissions Using the Campaign option in the form builder's Submission panel.
• The Campaigns endpoints in the JSON-API
• The Campaign step in the Zapier integration will be updated to select a Form instead of a Campaign. This change still needs some review.
• All campaign-based plugins from the installation package.

Transitioning to Tasks

To overcome these limitations, we introduced the Tasks feature. Tasks are far more flexible and address all the shortcomings of Campaigns:

• They support conditional execution, so you can decide when and how a form submission is processed.
• You can map any form field to any integration field, eliminating the need for predefined field names.
• Forms can have multiple integrations, allowing submissions to be sent to multiple services simultaneously.
• Audience lists can be dynamically assigned, ensuring that users are added to the correct lists based on their form input.
• Tasks come with a feature called Connections. A connection is the authentication to a service, including API Keys or passwords. Connections are shared and can be used across multiple forms. Therefore, you only need to authenticate with your service once, just like you did with Campaigns.

Supported Integrations

The following table showcases which integrations were supported in Campaigns and whether they are now available in the Tasks section:

How to Migrate from Campaigns to Tasks

If you are still using Campaigns, we strongly encourage you to migrate to Tasks as soon as possible. This transition will not only future-proof your setup but also give you far greater control over your form integrations. If you are currently using a MailChimp Campaign (or any other integration), follow these steps to transition to Tasks:

1. Create a dummy Campaign with the Sync Submissions option set to Disabled. This is required because the Campaigns section is still present, and the form must still be assigned to a campaign.
2. Edit your form and go to the Tasks section. Click New, select MailChimp from the apps list, and follow the steps to integrate your form with MailChimp.
3. Go to the Submissions panel and select the dummy campaign you created in step #1.
4. Save and test your form to ensure everything is working correctly.

If you need assistance with the migration, feel free to check our documentation or reach out to our support team.