by Fanatical Labs

Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so that you can work in your preferred application. Segment and Group your MailChimp subscribers based on SugarCRM data so you can market to the right people at the right time. Fully compatible with all versions and editions of Sugar and SuiteCRM.

Cancel at any time!
Free Trial

#3433 - Dealing with internal subscribers & sync

Closed General Question created by nicolas a year ago

Hi All

After the first sync, SugarChimp runs pretty smoothly and the recent support here was great! But as usual with on-boarding, most questions are coming through daily usage:

We have a lot of distribution partners as well as our whole team on our mailing lists. Now, what obviously happens is that they're going to be synced as leads or contacts to SugarCRM. When I'm deleting the records in Sugar, MailChimp will recognize them as unsubscribers. Same happens if I unlink and delete them afterward, they obviously disappear in the mailing list.

So here's my question, is there any workaround for this? Or do I just have to leave them in SugarCRM…
Thank you in advance!

Best regards
Nicolas

  1. fanatical_jon member avatar

    Jon S Provider

    a year ago

    Hello Nicolas,

    Great question. So, we have some configuration options that can turn off the "Create new records in CRM" for you if that is what you'd like to do. Take a look at the Advanced Configuration Settings, in particular the webhook_add_to_list setting. By changing this value to 2, you will not create new records in the CRM from MailChimp.

    If you are wanting something something else, please explain in more detail and I will see if we can handle your use case.

    Thanks,
    Jon

  2. nicolasathanasopoulos member avatar

    nicolas

    a year ago

    Hi Jon

    Thanks for the quick response!
    My original ambition was to ensure that we create every potentially new subscriber as a lead/contact in SugarCRM first and, only then, we sync him over to MailChimp. So, my assumption is that disabling the creation of new records through MailChimp could work pretty well because according to this plan it wasn't intended anyway.

    Just a minor question concerning the execution of the console. If I'm going to change the 'webhook_add_to_list' to value '2', is my command line correct?

    SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/webhook_add_to_list/2'),{},{});

    Hopefully, I interpreted the given code sample the right way!

    Best regards
    Nicolas

  3. nicolasathanasopoulos member avatar

    nicolas

    a year ago

    Hi Jon

    Seems like the workaround is doing a proper job!
    That was my routine, maybe it helps others as well:

    1 Firstly, execute command within SugarCRM

    SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/webhook_add_to_list/2'),{},{});
    

    2 Delete all contacts/leads that have been transferred to SugarCRM unintendedly

    3 Wait for SugarChimp's sync; these leads/contacts should appear as "unsubscribed" in MailChimp now

    4 Resubscribe them manually; thanks to the changed webhook none of them will be synced back to Sugar again!

    The case can be closed!

    Best regards
    Nicolas

  4. fanatical_jon member avatar

    Jon S Provider

    a year ago

    Hello Nicolas,

    I apologize for the slow responses here, I definitely typed up a confirmation to your response from 4 days ago but apparently did not ever send it. A lot of good that did!

    I'm glad to see that you were able to get that fixed as expected. My only note to others who might follow this thread, is that we could've deleted the queue after step 2 by running this console command:

    SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/empty_table/sugarchimp'),{},{});

    That command would replace the need to do your steps 3 and 4, as the sync would not send the 'unsubscribe' calls back to MailChimp. Thanks so much for your detailed responses here, they should definitely help anyone in the community that runs into this issue.

    I'll close the case out.

    Cheers!
    Jon

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
Rating
Rating
  • "Nice product and nice team behind it. They helped us with everything we needed in order to get our system working as we wanted to."

    Read More Reviews

Keep up to date on the latest additions

We'll send you an email every month with handpicked add-ons, reviews, tricks and tips. Don't worry, we hate spam as much as you do.