Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM. Created by Fanatical Labs, 2023 SugarCRM Partner Award Winner.
#1358 - Syncing problems with MailChimp
Hi
I've updated the criteria for my target list in Sugar CE to remove a set of contacts and re synced to MailChimp but the contacts are still showing in my MailChimp list. I wanted to confirm that they should be removed from the MailChimp list also?
Thanks Louise
-
"The new version does this much better and is actually much more feature rich than the old version 3 plugin. https://www.infosectrain.com/" - Infosec Train
Read More Reviews
- Most Recent Love from Users
melissa- Westcoat
- Mark Westerhoff
- danielolivas
- kgm
- Evolution Marketing
9 years ago
Hi Louise, good question. It depends how the contacts are being removed from the Sugar Target List.
Are you using a third-party tool target list tool that has this feature to add/remove based on criteria in Sugar? If so, which one is it? Or is this a customization that you developed? Or something else maybe?
Whichever the case, the tool that is being used needs to use the "Sugar-way" to remove relationship Contacts from the Target List using the SugarBean so that the logic hooks fire. This way SugarChimp will be notified of the removal and will queue an unsubscribe job. If the tool is using a direct sql query to remove the Contact from the Target List, there is no way for SugarChimp to be notified of the removal and it will not do anything.
Let me know if you have more info on this. Thanks!
9 years ago
Hi
I use KReporter V3.0 to create reports and export them as a target list. So I've updated an existing KReport and then re-exported to the target list.
Then in order to force a re sync, I've removed the target list from SugarChimp "MailChimp List:" option in Sugar saved and then re-selected the target list in the same way. So should the changes now be reflected in MailChimp?
In the same vein I assume changes I make in Sugar will not be replicated and therefore synced to MailChimp unless I re create the target list as target lists are not updated dynamically?
Thanks for your help Louise
9 years ago
That makes sense how you do that, but unfortunately that method will not remove the subscribers on the MailChimp side because it's not hitting the logic hook to notify SugarChimp that people are being removed from the list.
There may be another way to do this though. Can you explain your use case? What criteria are you running your report on to determine if someone should be on the list?
9 years ago
It's complicated and stems from another problem that I had support on yesterday.
I want to segment my MailChimp list to send my campaign to clients only (so not prospects). I can't segment on client or prospect (account type) as I can't map this field to my MailChimp list because the account type field is in the Accounts module and not the Contacts module.
Since we are using Sugar Community Edition, if we want to sync a related Account field for a Contact, we need to create a custom field on the Contact module that pulls in the related data, using logic hooks etc. A colleague of yours yesterday directed me to some resources but as this requires php coding etc I will need to find someone to implement this for me.
In the meantime as a workaround I decided to use two separate mailing lists in MailChimp one for clients and one for others. Hence I wanted to update the existing list in MailChimp to remove clients and also create a new list containing only clients.
Thanks
9 years ago
Got it, that makes sense. That was me helping out yesterday on that issue. What you say is correct. You really need to have the custom calculated field setup to do this the easiest way.
An alternative for now, is it possible to create a report in KReporter that can find 'account type' changes that have changed in the past week? You could create a report like that, and then every week you would run the report to find which clients are no longer customers. Then manually remove them from the Customer Target List in Sugar. It would be the same process for finding those that move from a 'prospect' to a 'customer'. This would be a manual process, but I'm guessing there wouldn't be but a few records each week that need to be added/removed from the list.
Would something like this work for now?
9 years ago
I'm not really sure how this would solve my current problem but not to worry. I'll just get someone to code up the logic hooks as you suggested yesterday but for future reference I'm not sure exactly which changes I make on Sugar will be synced on MailChimp then?
And even if I export a new target list those changes won't be picked up? eg when contacts leave a company or ask to change their mail preferences outside of mailChimp
Or is it just when I remove people from the target list they don't get picked up on MailChimp?
9 years ago
My thought was if you could create a report that would show you who needs to be removed from the customer list, you could then go to your Customer Sugar Target List and manually remove them. By manually remove them it will fire the logic hook and tell SugarChimp to remove the person from the Customer MailChimp List.
Does that make more sense?
9 years ago
OK so you're suggesting we remove our clients from our database to sync the MailChimp mailing list to not include clients. Is there documentation somewhere that explains what actions fires these logic hooks to tell MailChimp to update the list?
Thanks for your help
9 years ago
I'm not suggesting you remove the clients from your Sugar database, just simply remove them (unlink them) from the Sugar Target List. If you go to your Sugar Target List, you should see the Contacts/Targets/Leads/Accounts subpanels at the bottom of the page. If you make a report in KReporter to tell you which people are no longer customers, you could then go to the target list, find the person you need to remove, and remove them from the Target List. This will trigger what's needed to unsubscribe them on the MailChimp side.
The original solution of creating the custom calculated field is still what you need. I thought this other way might be a temporary solution in the meantime.
9 years ago
Hello, I just wanted to follow up here. Were you able to give anything above a try?
I'm going to close this case for now, but definitely let me know if anything else comes up around this issue. I'm hoping at some point in the future we can make the related field syncing easier, but I don't have a timeline on something like that. Thanks!