search

veda-consulting-company / uk.co.vedaconsulting.mailchimp

Other
22 stars 43 forks source link

Removed from smart group when Mailchimp sync runs #165

Closed natsukipope closed 7 years ago

natsukipope commented 8 years ago

Hi, one of our clients have the issue that a contact in smart group is removed when Mailchimp sync runs.

  1. A contact is added to a smart group. "Sync membership of this group with membership of a Mailchimp List" is set up for an appropriate list in Mailchimp.
  2. Run "Mailchimp Sync" in scheduled jobs. Confirm that the contact is added into the mailing list in Mailchimp side. Then go back to check the contact's info in Civi. This person is removed from the smart group.
  3. Run "Mailchimp Sync" again. Since the contact is removed from the smart list, the person is also removed from Mailchimp list, and it is marked as "Reason: N/A (Unsubscribed by an admin)". Screenshot attached. screen shot 2015-10-27 at 15 32 53

Originally this issue was found in Mailchimp 1.7. We've just updated CiviCRM to 4.6.9 and Mailchimp extension to 1.8.2 but it didn't solve the issue.

Appreciate your help in advance. Natsuki

veda-consulting commented 8 years ago

@natsukipope please check the Webhook settings on the Mailchimp side. The one which sends information back to CiviCRM should NOT be set to execute on API calls. We think this is the issue. Also the latest version 1.8.3 has a failsafe built into it to highlight this configuration

natsukipope commented 8 years ago

Hi, thank you for your reply. So when I went to mailchimp.com/lists/tools/webhooks ... page, for the test site there was no Webhook created. And for the actual client site, Only send updates when a change is made … via the API was unchecked.

screen shot 2015-10-28 at 10 42 09

The issue happens in both sites. Anything else I could check?

veda-consulting commented 8 years ago

@natsukipope is this still an issue for you? Could you update to the latest version and let us know if its still happening?

deepak-srivastava commented 7 years ago

We think latest v2.x has fixed this. Please re-open if the issue still exist. Thanks.