• Resolved AnnacolaWP2

    (@annacolawp2)


    Dear Support Team,
    I have two questions for you as I did not find on your forum any solution right for my case.

    #1 question: for each new subscribing to my newsletter, I receive a mail notification that they subscribed.

    In the last 3 subscriptions which happened after the GDPR, it seems that these 3 readers did not consent to GDPR. In fact, I checked every new subscriber and I noticed that there is no consent.

    So they finished automatically in a segmented list that doesn’t allow that I send them the newsletter complying to GDPR. This is so strange because if they don’t want to consent to GDPR they actually have not to subscribe!

    I am sorry cannot give you the names of the subscribers for privacy reason

    For doing all the process complying the GDPR I followed Mailchimp’s support instructions here:
    https://mailchimp.com/help/collect-consent-with-gdpr-forms/

    But maybe I did something wrong.

    Could you please check from a technical point of view? Mailchimp’s support team told me to contact you as a third party plug in.

    #2 question: is it possible that the mail with the link to download my present go out to these 3 last subscribers, and then they retired the consent to the GDPR?

    Here you are all the other requested useful information:

    *** Which version of MailChimp for WordPress you’re on: ->>
    Version 4.2.5

    *** WordPress & PHP version: ->>
    WordPress 4.9.8
    PHP Version don’t know, sorry

    *** Messages, errors, etc.: ->>
    [2016-10-11 06:37:46] ERROR: Form 807 > MailChimp API error: 0 cURL error 28: Operation

    timed out after 10000 milliseconds with 0 bytes received.
    [2017-03-30 13:54:17] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    migu*********@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-03-30 14:13:07] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    varn******@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-03-31 08:49:41] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    bron****************@ma**.ru has signed up to a lot of lists very recently; we’re not

    allowing more signups for now
    [2017-04-01 19:19:33] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    exhi**************************@gm***.com has signed up to a lot of lists very

    recently; we’re not allowing more signups for now
    [2017-04-03 01:03:33] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    mame*******@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-04-04 23:47:40] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    adam**********@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-04-05 17:06:27] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    roza***********@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-04-06 11:18:18] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    khri********************@ma**.ru has signed up to a lot of lists very recently; we’re not

    allowing more signups for now
    [2017-04-08 09:38:36] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    levy******@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-04-11 09:16:20] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    luki***********@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-04-12 23:24:38] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    mari**************@ma**.ru has signed up to a lot of lists very recently; we’re not

    allowing more signups for now
    [2017-04-17 11:04:34] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    roks******************@ma**.ru has signed up to a lot of lists very recently; we’re not

    allowing more signups for now
    [2017-07-05 08:46:56] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    khri******************@ma**.ru has signed up to a lot of lists very recently; we’re not

    allowing more signups for now
    [2017-08-13 22:24:41] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    ruza*************@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-08-15 19:49:21] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    leno************@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-08-19 15:59:37] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    chug*************@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-08-19 23:50:06] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    eva.*************@ma**.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-08-23 09:34:08] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    ianv**@az***.ru has signed up to a lot of lists very recently; we’re not allowing more signups

    for now
    [2017-09-10 23:52:04] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    hook*******@ya****.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-09-22 11:32:29] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    leik********@gm***.com has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-10-11 06:18:20] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    lena*********@ya****.ru has signed up to a lot of lists very recently; we’re not allowing

    more signups for now
    [2017-10-18 00:13:26] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    egoi*******@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-10-18 12:38:08] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    egoi*******@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2017-10-21 06:35:52] ERROR: Form 807 > MailChimp API error: 400 Bad Request.

    egoi*******@ma**.ru has signed up to a lot of lists very recently; we’re not allowing more

    signups for now
    [2018-02-14 00:20:27] WARNING: Form 807 > onda*******@gm***.com is already subscribed

    to the selected list(s)
    [2018-04-13 18:55:49] WARNING: Form 807 > cris*************@gm***.com is already

    subscribed to the selected list(s)
    [2018-05-22 19:55:09] ERROR: Form 807 > MailChimp API error: 400 Bad Request. Member

    Exists. anna********@gm***.com is already a list member. Use PUT to insert or update list

    members.
    Request: PUT

    https://us12.api.mailchimp.com/3.0/lists/2c7ada04e6/members/6ef43ec02489012f98c058c57f10

    eff8 – {“email_address”:”anna********@gm***.com”,”interests”:{},”merge_fields”:

    {“FNAME”:”Anna”},”status”:”pending”,”email_type”:”html”,”ip_signup”:”79.17.252.73″}
    Response: 400 Bad Request –

    {“type”:”https://developer.mailchimp.com/documentation/mailchimp/guides/error-

    glossary/”,”title”:”Member Exists”,”status”:400,”detail”:”anna********@gm***.com is already a

    list member. Use PUT to insert or update list members.”,”instance”:”f77c2809-84d8-4e35-a6fc-

    58e309360c56″}
    [2018-09-26 22:02:21] ERROR: Form 807 > MailChimp API error: 400 Bad Request. Invalid

    Resource. Please provide a valid email address.
    Request: PUT

    https://us12.api.mailchimp.com/3.0/lists/2c7ada04e6/members/d6a51d122add233e3edd8e6fb7b

    acfa7 – {“email_address”:”shar***************@gm***.com”,”interests”:{},”merge_fields”:

    {“FNAME”:”ClaraSmutt”},”status”:”pending”,”email_type”:”html”,”ip_signup”:”209.58.144.246″}
    Response: 400 Bad Request –

    {“type”:”https://developer.mailchimp.com/documentation/mailchimp/guides/error-

    glossary/”,”title”:”Invalid Resource”,”status”:400,”detail”:”Please provide a valid email

    address.”,”instance”:”a543ea24-94de-4f8d-8258-bb178455a632″}

    Hope to read your answer soon.

    Thanks again for your support.
    Regards

    Anna

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hello Anna,

    It looks like all the errors are related to a specific email. Please note that the errors are returned from MailChimp.com. We simply log them to show to you for debugging. Based on the errors, the email addresses listed tried to signup too many times and are blocked by MailChimp.com.

    Can you test from a different email address?

    Thread Starter AnnacolaWP2

    (@annacolawp2)

    Hello Harish,

    thanks so much for your reply.

    Of all those multiple-subscribing emails just one is mine because I tested the GDPR campaign a couple of times before sending and it worked everything perfectly.

    The 3 emails that seems to have opted in and out the same day are not in that list of errors.

    So what could be happened with my last 3 subscribers? Maybe could you look deeper at their anonymized emails please?
    la*********@******io.it
    tp**********@*************ni.com
    na**********@***il.com

    Thanks for your help
    Anna

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey Anna,

    Please note that we are not MailChimp.com, so we do not have any control over checking why an email was not added. Can you please check the error log at “MailChimp for WP > Others” and once you find the 3 emails you shared, please share with us the error details listed next to them.

    Thread Starter AnnacolaWP2

    (@annacolawp2)

    Hi Harish,

    thanks for your reply.

    I thought you could check from a coding or other technical point of view on your plug in.
    As I said before, those 3 emails are not listed in the error list of your plug in.

    I will be back to Mailchimp’s support if you cannot do anything else from your side.

    Thanks again for your help.
    Regards
    Anna

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey Anna,

    We do not do anything from our end to treat emails separately. If the email format is correct, we simply share it with MailChimp and then based on whether it’s accepted or rejected we show a success or error message.

    I would suggest contacting MailChimp.com and you could also try the form hosted on MailChimp.com.

    Thread Starter AnnacolaWP2

    (@annacolawp2)

    Hi Harish,

    thanks for your reply.

    After inspecting more deeply the issue with Mailchimp, I send you their answer:
    “…The only data that is coming over to Mailchimp from that form is the email address, the name, the location of signup, and the status (essentially, making it a double opt-in form). There is no data for the GDPR fields. The form needs to send data indicating that someone has opted into those fields. Basically, Mailchimp will reflect whatever data that form sends over. If data is missing from what’s sent to Mailchimp, Mailchimp has no way of knowing what that other data would be.”

    So that means that when the subscribers click the 2 mandatory check boxes on the contact form (one of those contains a link to the GDPR legislation) no data are transferred to Mailchimp and that’s why those 3 emails go into a list not allowed to send them the newsletter.

    Do you have technical instructions to add those data properly in your plug in? For GDPR and other legal aspects I use a provider called Iubenda.

    Thanks in advance.
    Regards
    Anna

    Plugin Author Danny van Kooten

    (@dvankooten)

    Hi Anna,

    Our plugin does not yet allow you to subscribe people using the GDPR information that MailChimp provides. We recommend asking your visitor for their consent before sending anything over to MailChimp, because it doesn’t make much sense to transfer their data over to MailChimp if they don’t consent to receiving emails.

    There is a field in the plugin called “Agree to terms” which you can use for this. If you include this field in your sign-up form, any visitor that does not check the “agree to terms” checkbox will not have their data transferred to MailChimp.

    Hope that clarifies. If not, let us know please.

    Thread Starter AnnacolaWP2

    (@annacolawp2)

    Hi Danny,

    thanks for your reply.

    As said, through that check boxes Mailchimp does not receive any data that the subscribers accept the GDPR. Infact, I used your “Agree to terms” box, adapted the text and inserted the link to privacy policy and GDPR Regulamentation.

    So they suggest to
    “see if they’re able to support “marketing_permissions” in their forms. They can check out our documentation for that found here:
    https://developer.mailchimp.com/documentation/mailchimp/reference/lists/members/

    Hope this helps.

    Thanks again.

    Anna

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey Anna,

    We do understand that. As we mentioned we do not have support for the MailChimp’s GDPR field yet hence we suggest users use our field instead. This field is not connected to the GDPR field in MailChimp, but regardless, it helps receive user consent.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Subscribers opted in and out the same day!’ is closed to new replies.