Gravity Forms CleverReach - WordPress Plugin

A Setup Guide to Gravity Forms CleverReach for WordPress Form Subscriptions

Gravity Forms CleverReach is useful when a standard WordPress form needs to do more than collect a submission - it also needs to send that contact to CleverReach for follow-up email campaigns. In this guide, we are not covering the plugin as a sales pitch. Instead, we will walk through the practical workflow: how to prepare the site, where to connect the account, how to create a feed, which fields to map, how to verify that a subscriber was sent successfully, and what to do if the contact never appears in the list.

The integration looks simple when a form contains only an email field. On a real website, there is usually a name field, marketing consent, different subscriber groups, conditional logic, admin notifications, and the risk of adding someone to a mailing list who should not be there. That is why this article focuses not just on buttons and settings, but on the data flow itself: what data leaves Gravity Forms, what CleverReach accepts, and where the result shows up.

This guide is written for a site owner, marketer, or webmaster who already uses Gravity Forms and wants to connect email marketing without creating chaos in the contact database. If you are setting up the form for the first time, work through the sections in order. If the integration is already in place, it is more useful to start by checking the feed, the field map, and the troubleshooting section.

What Problem This Form and Email Marketing Setup Solves

Gravity Forms handles the form itself: fields, validation, post-submit confirmations, notifications, and entries in the admin panel. CleverReach handles email campaigns, recipients, groups, subscription confirmation, and follow-up communication with the audience. The add-on connects these two parts through a feed. In Gravity Forms terminology, a feed is a rule that processes an entry after the form is submitted: where to send the data, which fields to map, and under what conditions the integration should run.

In practice, this is especially useful in three situations. The first is a blog or newsletter signup form where the user submits an address and is added to the correct group. The second is a lead form where the contact is added to an email sequence after submission, but only if the visitor agreed to receive messages. The third is interest-based segmentation: the same site can collect different subscriber groups through different forms or through conditional logic inside a single form.

The key difference between this approach and a manual export is that the subscriber reaches CleverReach immediately after the form is submitted. But automation requires care. If the fields are mapped incorrectly, the name may not be sent. If the consent condition is not configured, extra contacts may end up in the list. If the wrong list or group is selected, the marketer may see the data later but have no idea which form it came from. That is why the setup should be treated as a small workflow, not a one-time connection.

Quick reality check: if all you need is to store submissions in WordPress, the add-on is not required. It becomes useful when a form entry needs to become a recipient in CleverReach or update an existing recipient's data.

Who This Integration Fits, and When Another Approach Is Better

Gravity Forms CleverReach is a strong fit for sites where Gravity Forms is already the main form builder and CleverReach is already the email marketing service in use. In that situation, the add-on preserves the normal workflow inside WordPress: you create a form, configure the fields, add a feed, and test the result without building a separate custom handler.

The clearest use case is a content-driven site collecting subscribers for news, blog updates, events, webinars, or gated resources. The user fills out the form, sees a confirmation on the site, and the team receives the contact in CleverReach. If the form already includes consent for data processing and email signup, the feed can be triggered only when that condition is met.

This integration may not be the best choice if you need complex two-way data exchange, full CRM-style logic, deal-stage synchronization, or deep form personalization based on data coming from CleverReach. In that case, a simple feed may not be enough. Another questionable scenario is a site where marketing runs in a different platform altogether. In that case, it is better not to complicate the system and instead choose an add-on that matches the actual email service being used.

It is also worth thinking through the operational side. CleverReach works with groups, signup forms, and confirmation rules. Gravity Forms works with form fields and submit events. If different people manage those systems, decide in advance who owns the list, who owns the form, who writes the consent text, and who verifies the final result. Without that division of responsibility, the integration may work technically, but the recipient database will get messy very quickly.

What to Check Before Installing and Connecting the Account

The prep work matters. Problems at this stage often show up later as "the plugin is not working," when the real issue is permissions, a server dependency, the wrong CleverReach account, or a confusing list structure.

Basic Requirements on the WordPress Side

Make sure Gravity Forms is installed, active, and correctly handling a normal form submission. The add-on should not be the first thing you test. First create a simple form, submit a test entry, and confirm that the entry appears in Gravity Forms. If the base form already throws an error, the email marketing integration will only add another layer of uncertainty.

The official Gravity Forms documentation for CleverReach lists requirements for the installed version of Gravity Forms, the add-on itself, the CleverReach account, and PHP Soap support on the server. If your hosting provider restricts PHP extensions, check the WordPress system information in advance or ask hosting support to confirm that the required dependency is available. One detail worth noting in your source notes: the add-on changelog also mentions a move to the REST API, so if you see conflicting information, rely on the documentation for your installed version and the current system status.

Get CleverReach Organized Before Creating the Feed

Before connecting the integration, it helps to prepare more than just your CleverReach login. Plan the recipient structure first. Decide which group website subscribers should go into, which fields you need beyond email, and which confirmation flow should be used. In CleverReach, recipient groups, signup forms, and double opt-in are usually important for subscriptions. Do not leave those decisions until the testing stage, or you will not know whether the problem is in WordPress or on the email marketing side that was never prepared properly.

Minimum prep checklist:

• Make sure CleverReach already has the group or list where contacts should be added.
• Decide which extra fields are needed: first name, last name, interest, form source, or another segmentation marker.
• Confirm what consent text will appear on the WordPress form and who is responsible for storing proof of consent.
• Prepare a test email address that you do not mind using for subscription checks.
• Disable aggressive JavaScript optimizations only for troubleshooting if the form is already behaving inconsistently.

Admin Permissions and Access to Settings

It is best to do the setup as a WordPress user with administrator permissions. You need to install the add-on, activate it, open Gravity Forms settings, create feeds, and check logs during troubleshooting. If the site is maintained by an agency, coordinate access ahead of time. Do not share account secrets with third-party generators, chat tools, or untrusted utilities. It is enough to open the settings locally in the admin panel and work through the standard Gravity Forms interface.

Installing the Add-On and Verifying the Initial Connection

The installation process is the same as with a typical Gravity Forms extension: add the add-on to WordPress, activate it, and open the integration settings. The exact menu path may vary depending on how the site is set up and how the add-on was installed, but the general order stays the same: first the plugin is active, then Gravity Forms shows a CleverReach settings section or menu item, and then the account is connected.

General Installation Flow

1. Back up the site, or at minimum make sure you have a fast rollback path for plugins.
2. Install the add-on using your normal WordPress workflow and click Activate.
3. Open the Gravity Forms settings and find the CleverReach integration section.
4. Enter the connection details or complete authorization using whatever method your version of the add-on provides.
5. Save the settings and wait for a successful connection message if the interface shows one.

Do not create a feed until you are sure the add-on is actually connected to the account. If the global connection is not working, the feed will not be able to load CleverReach lists, forms, or fields. This is a common reason for empty dropdowns in the feed settings.

What Counts as a Successful Initial Check

The initial check is not just whether the plugin appears in the active plugins list. A successful start looks like this: WordPress shows no critical errors, Gravity Forms opens the add-on settings, the integration can see the CleverReach account, and the related CleverReach entities are available when you create a feed. If one of those pieces is missing, do not move forward yet. Fix the connection first, and only then continue to the field map.

Practical tip: before sending a test form submission, create a separate test group in CleverReach. That keeps real contacts separate from test addresses and lets you delete test entries without putting a live campaign list at risk.

The Feed as the Main Control Center

The most important screen in Gravity Forms CleverReach is not the list of installed plugins. It is the feed attached to a specific form. That is where you decide which form sends data, where it goes, and under what conditions. In Gravity Forms, a single form can have multiple feeds for different services or different workflows, so use clear feed names. For example, a feed for a general newsletter signup and a feed for webinar registrations should not have the same name.

What Is Usually Configured in a Feed

The official documentation for creating a CleverReach feed describes a standard setup structure: feed name, recipient group selection, CleverReach form selection, field mapping, and conditional logic. It is worth understanding the purpose of each item before saving, otherwise a test submission may look successful in WordPress while still failing to produce the correct result in CleverReach.

How to Map Fields Without Creating Problems

Start with the required email field. It should be a dedicated email field in Gravity Forms, not a generic text field with no format validation. Then map first name and last name only if they are actually needed for the campaign. Do not send extra data just in case. The more fields you send, the higher the risk of errors, outdated segments, and unnecessary personal data in your email marketing platform.

For additional attributes, use a clear and practical scheme. If the form includes an interest selector, map it to a field the marketer actually uses in CleverReach. If you need a subscription source, it is better to send a short value like blog_form, webinar_signup, or download_gate than a long text comment. Short values are easier to filter and verify.

How to Name a Feed So It Still Makes Sense a Month Later

The feed name may seem minor, but it is what lets you quickly understand which workflow is attached to the form. A vague name like "CleverReach" explains nothing, especially if the form has multiple integrations. It is better to use a name that shows both the action and the group: "Newsletter Signup - Main List," "Webinar - Topic Interest," or "Lead Magnet - Consent Checked." This is especially useful on sites where the person editing the form later is not the same person who created it.

When to Use a Hidden Source Field

If the site has several similar forms, add a hidden source field in Gravity Forms and pass it to CleverReach. This is not a mandatory add-on feature, just a clean form management practice: the field is invisible to the user, but it helps the team understand where the contact came from. The important part is not to fill it with random text. Use short, stable values that do not change every time the page headline is edited. If the same form is embedded on multiple pages, you can set the source separately for each copy or use different forms if that is easier to maintain.

How to Keep Duplicates and Test Addresses from Polluting the Database

Before the public launch, set a rule: all checks should be done with separate test addresses and inside a test group, or with a clearly marked source value. If you use your own working email that has already been in CleverReach for a long time, the test can be misleading. The contact may be updated, remain in an older status, or fail to appear in the expected segment because of existing data. For a clean test, use a fresh address and go through the full subscription flow again.

Conditional Logic as Protection Against Unwanted Signups

Feed conditional logic is especially important when the form includes a consent checkbox. The correct setup usually looks like this: the user can submit the request, but they are added to the mailing list only if they explicitly checked consent to receive emails. That separates two tasks: processing the request on the site and avoiding a subscription unless the user clearly chose it.

In the Gravity Forms interface, conditional logic is built around form field values. Make sure the condition points to the correct field and the correct checkbox value. If you later rename the answer choices or replace the field, the feed also needs to be checked again. Otherwise it may stop running altogether or start running too broadly.

Practical Scenario: A Signup Form for Useful Resources

Let us walk through a scenario that is common on sites with a blog, knowledge base, or product catalog. The goal is to create a form where the user enters an email address, a name, and consent to receive email updates. After submission, the entry should be stored in Gravity Forms, and the contact should be added to the correct CleverReach group. This is a strong test case because it immediately covers all the important parts: the form, the feed, the condition, the field map, the user-facing message, and the final result in the email platform.

Goal and Preparation

The goal is to create a working subscription flow without manually moving contacts. Before you begin, prepare a group in CleverReach, a test address, and a Gravity Forms form with email, name, and a consent checkbox. If the site already has a privacy policy, confirm that the consent text does not conflict with it. If the consent wording has not been approved yet, do not make the form public.

Setup Steps

1. Create or open the form in Gravity Forms and add an email field as required.
2. Add a name field if campaign personalization is actually needed.
3. Add a consent checkbox for email signup with wording that is clear to the user.
4. Open the form settings and create a new CleverReach feed.
5. Select the required recipient group and CleverReach form, if that option is available in your add-on version.
6. Map email to the email field, name to the name field, and the additional source value to a prepared field or a static value, if the interface supports it.
7. Enable feed conditional logic so the data is sent only when the consent checkbox is checked.
8. Save the feed and submit the test form using a new address.

What to Do with Gravity Forms Notifications

The admin notification and sending a contact to CleverReach are two different actions. Do not disable notifications just because email marketing is enabled. For a lead form, the administrator may still need an email about a new request, while the marketer needs the contact to appear in CleverReach. Check both outcomes separately. If the admin email does not arrive, the issue may be with WordPress mail delivery or SMTP settings rather than the CleverReach feed.

How to Choose the Right Post-Submission Confirmation Text

The confirmation text shown on the site should describe the next step honestly. If the subscription requires email confirmation, do not say "you are already subscribed." It is better to say that the request was received and that the subscription will be completed after the user confirms the address through email. This reduces confusion and makes it easier for support to explain why the contact is not active in the mailing list yet.

Expected Result

After the form is submitted, the user should see a correct confirmation message on the site. A new entry with completed fields should appear in Gravity Forms. A new recipient should appear in the selected CleverReach group, or the subscription confirmation process should begin if it is enabled on the CleverReach side. If double opt-in is being used, the absence of an active subscriber immediately after submission does not always mean something is broken. First check whether the confirmation email was sent and what status the contact has.

The Detail That Most Often Breaks the Test

The most common confusion is mixing up "the form was submitted" with "the subscriber is active in the mailing list." Those are different events. Gravity Forms may successfully accept the entry, while CleverReach may still be waiting for confirmation, rejecting a duplicate, or storing the contact in a status that is not visible in the usual segment. That is why you should check the whole chain: the entry in WordPress, whether the feed ran, the contact status, the confirmation email, and final placement in the group.

Practical Use Ideas for Different Types of Sites

The integration does not have to be limited to one small form in a sidebar. If you stick to the real capabilities of the form, the feed, the groups, and the conditions instead of inventing extra complexity, you can build several clean workflows that help marketing operate more precisely.

Content Site: Interest-Based Subscriptions

For a blog or knowledge base, add a topic selector to the form: product news, educational content, catalog updates, or event invitations. In Gravity Forms, that is just a standard choice field, and in CleverReach it can be used as an additional recipient attribute if the corresponding field is prepared in advance. The result is a cleaner audience segmentation model where users do not receive everything by default.

The test is simple: submit several test entries with different interests and check whether the value is stored in the recipient record. If the marketer cannot see that attribute, the problem is usually in the field mapping rather than the form itself.

Lead Form: Request Separate, Email Signup Separate

On a service page, a user may want to submit an inquiry without subscribing to email updates. In that case, the entry stays in Gravity Forms and goes to the administrator through a notification, while the CleverReach feed runs only when consent is checked. This setup respects the user's choice and helps keep sales inquiries separate from the subscriber database.

A good configuration for this scenario is a required email field for the inquiry and an optional subscription checkbox. The confirmation text on the site should not promise email marketing to everyone who submits the form. It should say separately that the request was received and that the subscription will be confirmed only if the user selected that option.

Lead Magnet Delivery: Provide Access Cleanly

If the site offers a checklist, guide, or presentation after a form submission, Gravity Forms can display the link in the confirmation message or send it by email, while CleverReach receives the contact for future communication. In this scenario, it is especially important not to confuse content delivery with a subscription. The resource can be delivered after the form is submitted, but adding the person to the mailing list should still depend on consent and the CleverReach rules.

How to Verify the Result After Setup

It is better to test the setup as a short sequence rather than with a single click. That helps you distinguish a form issue from an integration issue, and a confirmation issue from a contact visibility issue in CleverReach. This matters even more on sites that already have caching, anti-spam tools, a complex theme, or several similar forms.

Mini Checklist for a Test Submission

1. Open the page with the form as a regular visitor, not only from the admin panel.
2. Fill in the fields using a new test address that is not already in the target CleverReach group.
3. Submit the form with consent checked and make sure the on-site confirmation does not show an error.
4. Check the Gravity Forms entry: email, name, consent, and additional fields should be saved.
5. Check CleverReach: the contact should appear in the expected group or show a pending confirmation status.
6. Repeat the submission without consent and confirm that the entry exists in Gravity Forms, but the feed did not add the contact to the mailing list.
7. Check the confirmation email if double opt-in is enabled, and complete the confirmation through the link.

If the test succeeds only partway through, do not change every setting at once. Identify the exact step where the chain breaks. That will save time, because the form, the feed, the API connection, the confirmation email, and the recipient group each need to be diagnosed differently.

Short Test Log for a Live Form

For a form that is already published, it is useful to keep a small test log. Five lines are enough: the test address, whether consent was checked, whether an entry appeared in Gravity Forms, what contact status CleverReach shows, and what action was taken after the test. This is especially helpful when a marketer and an administrator are testing together. One sees the form and the entry, the other sees the email platform and recipient status. Instead of messages like "it did not show up for me," the team can see the exact step where the process stopped.

When to Repeat the Test After a Change

You should repeat the test after any change that affects fields, conditions, or the outer layer of the form. That includes renaming checkbox options, deleting a field, copying a form, changing the selected CleverReach group, enabling a new script optimization, moving the form to another page, or changing the confirmation text. Not all of these changes will break the integration, but each of them can change the user path. Without another test submission, the problem may only become visible after real subscribers start using the form.

What to Look For in Gravity Forms Entries

The form entry is your first source of truth. If the entry does not contain an email address or consent, CleverReach will not receive correct data. If the entry exists but the feed did not run, check the conditional logic and the global add-on connection. If the entry and the feed both look correct but the contact is missing in CleverReach, move on to the recipient status, double opt-in, and logs.

When to Enable Logs

Gravity Forms supports logging for add-on troubleshooting. There is no need to leave it on permanently on a live site, but it is useful while investigating a problem. Logs help you see whether the add-on ran after submission, what responses came back from the external service, and where the process stopped. After troubleshooting, logging should be turned off or returned to its normal level so you do not accumulate unnecessary technical data.

Double Opt-In, Consent, and a Clean Recipient Database

In email marketing, it is not enough just to deliver the contact. The quality of consent matters too. As an email platform, CleverReach supports subscription confirmation workflows, and Gravity Forms lets you collect an explicit user action through a checkbox, a text field, or a separate consent block. The integration should connect those pieces in a way that makes it clear to the user what they are agreeing to, while also giving the team a reliable way to confirm the source of the subscription.

Do Not Mix Technical Consent with Marketing Consent

A user may submit a contact request without wanting to receive email campaigns. That is why the subscription checkbox should not be hidden, pre-checked, or vague. If the form has two purposes, separate them clearly in the wording: the request will be processed either way, while the email subscription is enabled only through a separate choice. This reduces the risk of complaints and makes the database easier to manage.

Where to Store Source Markers

It is often useful to pass a short subscription source value into CleverReach. That can be a field value, a hidden field, or a separate form field if the site already uses that pattern. The source makes it easier to understand later which form produced the contact. But do not turn CleverReach into a warehouse for every detail collected in the request. For email marketing, email, name, source, and interest are usually enough. Comments, phone numbers, and request details are often safer to keep in Gravity Forms or in a CRM if one is being used.

Testing Double Opt-In

If subscription confirmation is enabled, the test does not end when the form is submitted. You need to open the inbox for the test address, find the confirmation email, click the link, and then check the recipient status again. If the email never arrives, review the CleverReach settings, the spam folder, the address itself, and the state of the signup form. Do not try to solve that kind of issue only by changing Gravity Forms fields: the confirmation email belongs to the email platform side of the process.

Safe Enhancement: Normalize a Value Before Sending It

For most sites, the standard field map is enough. But sometimes it helps to lightly normalize a value before sending it to CleverReach: trim extra spaces, convert the source to lowercase, or replace an unstable field value with a short code. Gravity Forms documents the gform_slug_field_value family of filters, and add-ons use a version with the integration short name. For CleverReach, that filter is documented as gform_cleverreach_field_value.

Use a snippet only if you understand exactly which field you are modifying. It is safer to add it through the Code Snippets plugin or a child theme file instead of editing WordPress core, Gravity Forms, or the add-on directly. Below is an example that normalizes the source field. It does not touch the email address and does not affect form submission itself. It only converts one additional value into a stable format.

add_filter( 'gform_cleverreach_field_value', function( $value, $form_id, $field_id, $entry, $feed ) {
    // Replace 12 with the Gravity Forms field ID that stores the subscription source.
    if ( (int) $field_id !== 12 ) {
        return $value;
    }

    $value = trim( (string) $value );
    $value = strtolower( $value );
    $value = preg_replace( '/[^a-z0-9_\\-]/', '_', $value );

    return $value;
}, 10, 5 );

After adding the snippet, submit a test form and check the recipient in CleverReach. The expected result is that the source field now looks stable, for example blog_form, while the other fields are still passed as before. To roll it back, disable the snippet and repeat the test. If the problem disappears after disabling it, the logic was too broad or the wrong field ID was used.

Do not use a snippet to bypass consent or force a subscription. Code changes are acceptable only for careful data preparation, not for overriding the user's choice.

Why a Subscriber Does Not Reach CleverReach and How to Diagnose It

The easiest way to troubleshoot is to follow the full chain: the form accepted the data, the entry was created, the feed ran, the external service accepted the contact, the subscriber confirmed the email, and the contact became visible in the correct group. If you jump randomly between settings, it is easy to fix the wrong part and create a new problem.

The Form Submits, but the Contact Is Missing from the Group

Symptom: the user sees the Gravity Forms confirmation, the entry exists in the admin panel, but no new contact appears in CleverReach. Possible causes include a disabled feed, the wrong list being selected, conditional logic not being met, the contact waiting for confirmation, or the contact already existing in a different status.

Start by opening the Gravity Forms entry and checking the field values. Then open the feed and make sure it is active. If a consent checkbox is being used, submit two test entries: one with consent and one without it. If both submissions behave the same way, the condition is configured incorrectly or it is checking the wrong field. If the contact is waiting for confirmation, complete the double opt-in process and check the group again.

CleverReach Lists or Forms Do Not Appear in the Feed

Symptom: the feed settings page opens, but the CleverReach dropdowns are empty or do not refresh. This is usually related to the account connection, permissions, a server dependency, or a temporary connection issue. Check the global add-on settings, save the connection again, and make sure the required groups and forms actually exist in CleverReach.

If the issue keeps happening, enable Gravity Forms logging temporarily and see whether the request reaches the external service. Do not change the form structure until the connection is restored. Missing lists are not caused by the form fields.

Email Is Sent, but Name or Additional Fields Are Missing

Symptom: the contact appears, but the recipient record is almost empty. The cause is usually field mapping or a data-type mismatch. Check that the Gravity Forms field is connected to the correct CleverReach field and that the test entry actually contains a value. If the field is optional, run one test with a value and one without it so you can see the difference.

If you are using a normalization snippet, disable it temporarily. A code tweak should be the last layer of troubleshooting, not the first guess. After fixing the field map, send a new test address, because updating an existing contact may depend on CleverReach rules.

The User Does Not Receive the Confirmation Email

Symptom: the form was submitted, the contact was created or is waiting for confirmation, but no email arrives. Check the CleverReach side: signup form settings, recipient status, spam folder, email address accuracy, and sending limits. In this situation, Gravity Forms has already done its part, and the confirmation email belongs to the email marketing workflow.

The Integration Worked Before, Then Stopped After Changes

Symptom: the subscription used to work, but after changes to the form, theme, cache, or JavaScript optimization, the tests no longer pass. Start with the most recent changes. If the form fields were changed, review the field mapping. If optimization was enabled, temporarily exclude the form page from aggressive minification and test again. If the add-on was updated, compare the feed settings and enable logs for a single test submission.

Limitations and Questionable Decisions You Should Know About in Advance

The integration is useful, but it does not turn Gravity Forms into a full email operations platform, and it does not turn CleverReach into a CRM for all of the site's data. It is a bridge between form submission and email recipients. The more clearly you understand those boundaries, the fewer surprises you will have after launch.

Do not send too much personal data into the mailing platform. For email marketing, an address, a name, a source, and an interest are often enough. If the form collects a phone number, a detailed comment, a budget, an address, or other sensitive information, keep that data only where it is truly needed to process the request. Sending the entire data set into an email service makes privacy management and database maintenance harder.

Do not assume the add-on will solve email deliverability by itself. Delivery of confirmation emails, domain reputation, and email infrastructure settings depend on CleverReach and the mail environment, not on Gravity Forms. If users do not receive messages, separate a form problem from a mail problem first.

Another limitation is form structure changes. If you removed a field, changed checkbox options, or duplicated a form, check the feed again. Visually, the form may look almost the same, but the internal field IDs and conditions may already be different. After any major form change, always run a test submission.

When Gravity Forms CleverReach Is the Right Choice

Gravity Forms CleverReach is worth using if you already build forms with Gravity Forms, run email campaigns in CleverReach, and want to connect those systems through a clear feed-based workflow. The main strength of the solution is the familiar Gravity Forms logic: the form collects data, the feed decides where it goes, and conditional logic helps prevent subscriptions without the required user action.

Before launch, verify three things: the base form must reliably accept entries, CleverReach must already have the required groups and confirmation flow prepared, and the feed must have a clean field map plus a consent condition. After that, you can download Gravity Forms CleverReach, install it on a staging site or a site protected by a reliable rollback plan, and test the full chain described in this guide.

If your email marketing already lives in another platform, do not choose the CleverReach add-on just for the sake of installing another plugin. First decide where the subscriber database will actually live. If that system is CleverReach, the Gravity Forms integration provides a clear and maintainable path from a WordPress form to an email recipient. If not, it is better to choose the add-on built for the platform you really use so you do not end up maintaining extra databases and manual transfers.