SugarChimp

Thanks for reaching out. It looks like the screenshot didn't come through. Can you send it to mailchimp@fanaticallabs.com so I can take a closer look?

Additionally, can you update to the latest version of SugarChimp and see if the issue still remains? You can find instructions on updating here:

https://fanaticallabs.zendesk.com/hc/en-us/articles/360004608392-Update-to-the-Latest-Version-of-SugarChimp

Thanks, Heidi

Thanks for sending that along. According to the screenshot, it looks like this record was cleaned from one of the audiences, which may explain why it was marked clean in Sugar.

Can you check a setting for me by following the steps below?

1. From within Sugar Admin, navigate to the Health Status page
2. Right-click anywhere on the page and select Inspect
3. Click the Console tab at the top
4. Copy/paste the following text into the Console and press Enter: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/globaloptout'),{},{})
5. Click the Network tab
6. For the globaloptout name, view the value, as shown here: https://d.pr/i/LBNYPP

Thanks, Heidi

Hi Swetha,

Thanks for sending this along. Unsubscribing in Mailchimp should cause the record to be marked as Invalid within Sugar. I had noticed that the record is marked Cleaned in another audience. Can you confirm the email was valid in Sugar prior to marking it as unsubscribed in Mailchimp?

I haven't been able to replicate this issue on my end- are you able to replicate this issue with another record? If so, it might make sense to grab some debug logs so we can take a closer look.

Here are the steps for that process:

1. From within Sugar Admin, navigate to the Health Status page.
2. Right-click anywhere on the page and select Inspect. Switch to the Console tab, and then paste: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/logger/debug'),{},{});
3. Unsubscribe a record from Mailchimp and let it sync to Sugar.
4. Send over the logs. You can get these by following the steps below:

From Sugar Admin, click System Settings Click View Log at the bottom of the page Click All at the top of the page Copy/paste the text that appears into a .txt file to send to mailchimp@fanaticallabs.com

5. When completed, you can return the logger level to normal by pasting the following into the Console tab: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/logger/normal'),{},{});

Thanks, Heidi

Hello there,

We haven't heard from you regarding the issue in a few days. Is there anything we can help with?

Let me know how I can help.

Thanks, Heidi Fanatical Labs Support

Hi Swetha,

Thanks for this response. My apologies, I intended to say that unsubscribing in Mailchimp should cause the record to be marked as opted out in Sugar. Only when a record is cleaned in Mailchimp would that sync to Sugar as a cleaned record.

According to the screenshot you sent, the globaloptout setting is currently set to 2, which means that currently when someone unsubscribes in Mailchimp, that data is not synced to Sugar. This setting would suggest that perhaps the record was marked as Invalid within Sugar, or was marked cleaned within Mailchimp prior to this setting being updated. (You can see more about this setting and other options you have here: https://fanaticallabs.zendesk.com/hc/en-us/articles/360021151672-Advanced-Configuration-Settings)

It sounds like you may have multiple audiences that share some contacts and when a contact unsubscribes from one type of email, that doesn't necessarily mean you want them to be unsubscribed from all. In this scenario, we usually recommend that you have one Master SugarChimp List within Sugar and Mailchimp. You could then create Mailchimp Groups to determine the types of campaigns a contact should be receiving. Here's an example of how that would look: https://d.pr/i/2A1obQ

With this option, the subscriber could unsubscribe from all emails, or they could simply update their preferences to indicate which types of campaigns they would be interested in receiving. You can see how that option might be displayed within the footer of your campaign here: https://d.pr/i/DGcJN6

Please let me know if you have any questions or if you want to hop on a call to chat this through a bit further.

Best, Heidi

Hi Swetha,

Thanks for sending this scenario along. I wasn't able to replicate this scenario. As you mentioned, we would expect the record to be removed for each Target List they unsubscribed from (without the email being marked as opted out). When I did testing on my end, the expected behavior is what occurred. Can you tell me if you unsubscribed them directly from Mailchimp or from a sent campaign? I'm hoping to identify if there was something unique to help me replicate what you found. I didn't receive the logs- can you confirm they were sent to mailchimp@fanaticallabs.com?

In regards to the emails marked Invalid, we did recently resolve an error (in version 10.1.2) where a capitalization change within a record's email address caused the email to be marked Invalid. We discovered this issue when a customer had another integration that randomly changed the capitalization of an email address when making updates. I can't say with certainty that's what happened in your scenario but you could see if there are any clues for that particular record by looking at the audit log. You can find this by navigating to the record and clicking the arrow next to Edit, as shown here: https://d.pr/i/QVMjWM.

Finally, if a contact unsubscribes from a campaign through the unsubscribe link, they cannot be added back to that audience via Sugar as Mailchimp won't allow the contact to be active again unless they personally re-subscribe.

Thanks, Heidi

Hello there,

We haven't heard from you regarding the issue in a few days. Is there anything we can help with?

Let me know how I can help.

Thanks, Heidi Fanatical Labs Support

Thanks for sending those logs along. Unsubscribes sync to Sugar as Opted Out whether they are unsubscribed in Mailchimp by the admin or unsubscribed by the subscriber within the campaign itself. Both actions should have the same result.

As mentioned in our email, I recommend updating to the latest version and let's monitor to see if you encounter this issue again.

https://fanaticallabs.zendesk.com/hc/en-us/articles/360004608392-Update-to-the-Latest-Version-of-SugarChimp

Please let me know if you have any trouble installing the latest version.

Best, Heidi