Conditional logic fields merger with MailChimp

Hi @leelalee

There is no conditional logic available “inside” MailChimp integration but there can be conditions set to select which integration(s) should be executed.

So what you could possibly do would be this:

On “Forminator -> Integrations” page you can configure MailChimp integration multiple times. For example, if you have three possible scenarios (“new members’, “renewing members”, “renewing members updating information) you would configure the same MailChimp connection there three times – just make sure to give an easily recognizable name to each of these connections.

Then you go to form to its “Integrations” settings and

1. add first MailChimp integration (e.g. the one for “new members”) from Connected Apps to “Active Apps”

– select your list, tags etc
– and in field mapping map all the fields that need to be added (“new members (many fields are entered in MailChimp)“)
– once all set, click on “Conditions” button next to that MailChimp “Active app” and set some rule that will only use this integration if it’s a new member.

You can read more about setting conditions for integrations here
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#sending-data-conditionally

2. add second MailChimp integration from Connected Apps to Active Apps (e.g. the one for “renewing members”)

– select the same list, tags etc
– and in field mapping map only those fields that need to be updated (“only one field needs to be updated in MailChimp”)
– then again, set “Conditions” for this integration accordingly to use it only in case of those renewing members.

3. and then in the same way (just using different fields mapping and different condition) add the third integration.

This way depending on the choices made on the form only one of those integrations will be executed, resulting in sending only selected data to MailChimp.

Note though: you need to make sure about “required fields”. if any of the field is set to required in MailChimp, it also needs to be mapped in MailChimp integration in the plugin; or you need to set it as not require in Mailchimp instead.

Best regards,
Adam

Fantastic, Adam! I am most grateful to you for your timely and very helpful response!

May I trouble you to clarify the following questions for me, also (much obliged):

– When do Forminator entries overwrite existing Mailchimp fields? Is that always the case, is it even possible? As mentioned, I would like to add new contacts, but I would also like to overwrite existing information in case information is being updated. I am wondering if that is possible at all?

In the documentation, there is a phrase:

“From now on all the data, from the forms you have chosen to set this up, will be also sent to your Mailchimp Audience?:)”

Just to clarify: the information will not be sent as an email to my audience, but the information will be added to my audience list on MailChimp. It sounds like a silly one, but I really do not want to accidentally share personal information with my whole mailing list ??

Many thanks!

Hi @leelalee

When do Forminator entries overwrite existing Mailchimp fields? Is that always the case, is it even possible? As mentioned, I would like to add new contacts, but I would also like to overwrite existing information in case information is being updated. I am wondering if that is possible at all?

As you can see in Adam reply above, scenario 1 & 3 already covers this.

An additional part that should be taken into account is this: https://mailchimp.com/help/update-a-contact-profile/ as a separate solution

Every email campaign you send should include an update your preferences link so your contacts always have an opportunity to make changes. We automatically include the |UPDATE_PROFILE| merge tag in the default footer content block. You can also add a preferences link to any other section of your email.

When it comes to:

From now on all the data, from the forms you have chosen to set this up, will be also sent to your Mailchimp Audience ??

it means that the fields you have set up in your form and merged with Mailchimp, will be sent to the correct Mailchimp Audience list, not Mailchimp Audience emails that exist in that Audience ??

Kind Regards,
Kris

Hi Kris @wpmudevsupport13 & Adam @wpmudev-support8,

Thank you both so much for your support.

I think I wasn’t very clear in my last message. I think your suggestion would work very well. However, because I have conditional form fields in the form’s front end (i.e., fields appear or disappear depending on the user selecting ‘new membership’ – many fields, ‘renewing’ – few fields, or ‘updating details’ – many fields), I may not need to have seperate conditional logic fields for the integration. I tried a simpler set-up without any conditions, and fields appear to merge and update in MailChimp correctly.

However, and apologies, this may be a seperate issue – I discovered when testing, that some contacts successfully transfer to MailChimp, while others do not. I tested many different scenarios and I can not see any rationale behind when users are or are not successfully subscribed. Some test emails work very well, while some emails did not come through (and it is stated as such on the Forminator submission page, which makes me think that the transfer is already blocked on the Forminator side). As mentioned, I tried many different scenarios and I can not see what the issue may be.

I am providing the form here for your reference:

https://drive.google.com/file/d/1zE3LqjZ0dOclifJNsOvVqyIx3X-sBpxc/view?usp=sharing

As always, I much appreciate your help.

Please let me know if you require more detail.

Many thanks

• This reply was modified 9 months, 1 week ago by leelalee.

Update: I just thought I found out that the issue is the optional address field, now making it a required field to avoid the issue, which still means some contacts simply do not get transferred. The error message in Forminator: “Failed adding or updating member on Mailchimp list”. :-/

Could you let me know how I can fix this error?

Many thanks

• This reply was modified 9 months, 1 week ago by leelalee.

Hi @leelalee

Thank you for response!

I took a look at the shared form and I can see that there are fields with conditional logic.

However, note please that this export does not include any settings related to MailChimp integration – exports in general do not include such settings/data (as well as they do not include any submissions data). This means also that I, unfortunately, cannot check integrations configuration.

I could try to replicate integration settings with my own MailChimp on my end but I don’t know how it’s set on your end.

I still suspect that the issue with some contacts working and some not is related to required fields settings vs fiels that are conditionally visible (or not) and most likely this requires further review. In general, you need to make sure that

a) in any given MailChimp integration all the fields that are marked as required at MailChimp end – do have form fields mapped to them (there is no exceptions, lack of even one single required field would cause issues)

b) that those fields are also required on the form (again, if optional form field is mapped to required MailChimp field and user doesn’t fill it in, this will fail to transfer contanct)

c) and, finally, conditional logic – even if the form field (which is mapped to required MailChimp field) is set to be required but at the moment of submission it’s hidden, it would cause same issue, just like case B above.

That being said, perhaps you could share screenshots of fields mapping (note: don’t share credentials! only field mapping) in your MailChimp integrations for this form, as well as screenshots of MailChimp integrations rules for the same form?

Kind regards,
Adam

Hi Adam,

Many thanks for looking into it. From what I can see, only email, first, and last name are required: https://drive.google.com/file/d/1rKU-d5PdiNvH1lMoBkIsRn5FEBN0RcCZ/view?usp=sharing

Other fields are ticked as visible (which applies to a separate signup form).

The weird thing is that depending on the email it appears to be at random when it does/ does not merge and it states so within the Forminator plugin ‘submissions’ tab, which makes me think that it didn’t even try to send it.

Is it possible that this issue is caused by me testing this on a staging site?

As always, your help is much appreciated.

Best regards

Hi @leelalee

Thank you for response!

I don’t think it’s related to staging site in general.

On that screenshot it does seem to require only two fields so if those are always passed – it should be working.

But I also asked if you could provide screenshots of mapping setttings from MailChimp integration configuration on your form. Would you mind sharing that? I mean the screen where you actually have form fields assigned to mailchimp fields.

I’d still like to take a look at that to make sure it’s all fine.

Kind regards,
Adam

Hi Adam @wpmudev-support8,

Many thanks for your help and for looking into it.

I now established the form live on https://www.lcnau.org/membership/

This is the final form: https://drive.google.com/file/d/1C_CQpT_LWcC7sVQ1zhRb4388nFbKarHu/view?usp=sharing

The final MailChimp set-up:

https://drive.google.com/file/d/1u2TuEBpWYIck6tXfckBZPLRUtxTK7YX-/view?usp=sharing

The integration set-up from Forminator: https://drive.google.com/drive/folders/1qOHkKsMTxeMwXfYEUlxmCsVhQD8js8Tp?usp=sharing

Because there is a payment attached to the final form I ran limited tests with test cards and it may still persist.

One way I had the problem was when I included a ‘hidden field’ in the form with the ‘submission ID’, which I wanted to use to create a unique membership number in MailChimp. This is a functionality I urgently need. However, when I set it up, data was not transferred to MailChimp. It seems that there may be a problem as soon as I set up a ‘hidden field’ in Forminator. But this is all speculation.

Your help is much appreciated. Many thanks for all this. Overall I think it is such a great plugin and I am thankful for the integration. I just hope it will be reliable.

Many thanks!

Hi @leelalee

Thank you for response and providing all the additional materials, that was very helpful!

I’ve watched your video carefully and if I correctly understand this is a staging site with a simplified integration configuration. It does seem to be working just fine – even on your video it shows it updates the fields correctly.

Then you mention the hidden field and it seems you’re spot on with this:

1. I did some more testing on my end using my own MailChimp for integration. I’ve added some of the fields (Merge Tags) based on your MailChimp screenshot and then added and mapped the hidden field to the form to pass submission ID to MailChimp.

2. With it, integration immediately stops working no matter what. Submission itself works and is saved on the site, with correct submission ID number in a hidden field.

But integration status says MailChimp wasn’t updated and on MailChimp end I can see no changes.

When I make it to not send that hidden field to MailChimp – all works fine again.

3. The value of a hidden field is a number and so it’s set in MailChimp but just to see what it actually sends I have changed the type of Merge Tag/Field in MailChimp from “number” to “text” and…

Turns out, Forminator’s integration doesn’t sent the expected number from that hidden field but just the raw test: “submission_id”. Obviously update fails when MailChimp merge tag is of type “number” and instead it gets “text”.

—-

So yes, hidden field is blocking these updates – breaking MailChimp submission in this case.

It is a bug on Forminator’s end of which we weren’t aware yet as it’s quite a specific case. We do have some bugs related to use of hidden fields to pass submissions ID but those identified so far where only related to some specific uses of the form without MailChimp integration (e.g. use of such hidden field in form redirects or e-mail subject).

Unfortunately, I don’t have a workaround for that either, I’m afraid. I have reported it as a bug to our Forminator Team so developers would look into it and work on the fix but at this point I’m not quite able to predict how soon/fast it will be fixed.

Kind regards,
Adam

Hi @leelalee

I hope you are doing well.

I would like to update you regards the current issue, we confirmed it is a bug in the plugin and happens when ___ Describe the issue __, unfortunately, the fix requires updating the plugin code but we already reported it to our developers.

We can’t give an estimated time yet for the fix but subscribing to our roadmap https://wpmudev.com/roadmap/ is a good way to be posted about upcoming versions, once they are released, it is going to be described at changelog found on https://www.ads-software.com/plugins/forminator/#developers

Since the bug was acknowledged, reported and tasked to be fixed, we are marking this as resolved, but feel free to let us know if you have any additional questions.

Best Regards
Patrick Freitas

Hi together,

Many thanks for looking into the issue, flagging it, and adding it to the queue – I very much appreciate all your efforts. I just checked the roadmap and changelog to see if it may have been resolved. I was not able to identify if this issue has now been resolved or not, very sorry to check with you. Could you let me know if it is now possible to use hidden fields (i.e., the Forminator submission ID) to be inetgrated to MailChimp fields?

Many thanks and warm regards

Hi @leelalee,

I checked the plugin backlog and can confirm a fix for the bug is ready. It is expected to be released in the upcoming update. Please keep an eye on the plugin changelog for further details.

Kind Regards,
Nebu John

Fantastic, thank you so much for your quick response @wpmudevsupport14 ??