GDPR compliant fields in MailChimp are not showing up in the integration

  • Profile Image
    Asked on May 17, 2018 at 01:15 PM


    I use jotform to front-end mailchimp but i can't see how to add the GDPR fields into my jotforms that map to the GDPR fields in mailchimp

    how can this be done?


  • Profile Image
    Answered on May 17, 2018 at 03:08 PM

    You will have to do the integration in the form builder. Here's a guide that would help you do the integration:

    Note that Jotform is GDPR compliant. Learn more about it here

    You do not need to do anything regarding GDPR if you are using our forms to collect data from EU citizens. If you need a DPA, you can get it here

  • Profile Image
    Answered on May 17, 2018 at 03:58 PM

    That works if I create specific fields in mailchimp, however i'm using the GDPR feature for signup forms as some users come in through those and the others via my Jotform. Because i have automations in mailchimp that are based on what the user enters into the mailchimp GDPR fields i need to be able to fill those fields from Jotform.
    When i go through the integration builder, the GDPR fields are not shown

  • Profile Image
    Answered on May 17, 2018 at 05:08 PM

    To be honest, I am not aware of the fields that you've mentioned. But I searched Mailchimp and found related articles. Let me check this first and get back to you. Companies around the world have changed systems to be compliant with GDPR and look like I missed some updates from MailChimp. Again, I'll keep you posted.

  • Profile Image
    Answered on May 17, 2018 at 05:24 PM

    Ok, still, I cannot replicate the problem. Here's my MailChimp Form:

    Integration allows me to map the fields, see screenshot:

    In MailChimp, you need to select Form Builder to create the form;

    I've followed the steps here

    I hope that helps. 

  • Profile Image
    Answered on May 17, 2018 at 06:11 PM

    So when you add the GDPR fields to the signup forms it add a section - mine is this:

    1526594511mc gdpr.JPG

    and this then adds entries to the database here:

    1526594596mc opts.JPG

    which i can then create segments or mail conditions using the Contact Permissions entry here:

    1526594676mc filts.jpg

    but I can't map to the contact permissions fields using the integration in JotForm:


    So what i am looking for is a direct link from JotForm to the Contact Permissions field in mailchimp - is this possible?

  • Profile Image
    Answered on May 17, 2018 at 07:50 PM

    That is possible, I'm sure. But the way how you understand that section inside MailChimp is somewhat wrong. That was just a way to make your MailChimp form to be compliant with GDPR. Notice the wording "consent" there. 

    The Contact Permission or Marketing Permissions section is the GDPR field as a whole. The options as shown in your first screenshot is where your subscribers will select how they want to get the consent campaign. In short, they are not the actual fields. 

    I would suggest adding the fields to your MailChimp form. The fields such as the Facility, etc. in your last screenshot. That way, you can map it in the form. 

  • Profile Image
    Answered on May 17, 2018 at 11:33 PM

    OK - so the answer is to ignore the GDPR capability they have added to mailchimp and just ask the questions with standard fields.
    Seems a shmae but i guess if they haven't opened up those fields for you to write to there's nothing you can do!

  • Profile Image
    Answered on May 18, 2018 at 03:48 PM

    I'm sorry, I've seen my colleague has marked this thread as answered. 

    Anyways, it's not to ignore, but to follow the steps to be compliant. We are compliant too with GDPR, so that is the starting point. You're going to follow the steps as shown in the MailChimp guide that I've given you yesterday. Once you do that, your submitters will get a Consent Email from MailChimp telling them about GDPR. Here's a screenshot of that:

    Here's the guide again: Just please follow the steps, and you should be compliant with GDPR after.