Member SinceJanuary 3rd, 2019
Last SeenAugust 29th, 2019
JohnK does not have any add-ons for sale.
Support September 20th, 2019 @ 11:52 am
So just to confirm:
How is an abuse report handled in SugarCRM? Does it opt the contact out of all the target lists connected? Does it also set the email as being opt-out?
How is an "opt me out of everything" report handled in SugarCRM? Does it opt the contact out of all the target lists connected? Does it also set the email as being opt-out?View Comment
Support September 19th, 2019 @ 8:23 am
What about "opt me out of everything!" and abuse reports? Surely they get passed back to the CRM regardless of which list they're from?View Comment
Support September 10th, 2019 @ 3:39 pm
Thanks for the response fanatical labs!
Yes, please can you tell me the following:
- You mention that you use the email address to look up the contact. What happens if there are duplicate contacts with the same email address? How does SugarChimp decide which contact the unsubscribe belongs to? Or does it unsubscribe both?
Support September 3rd, 2019 @ 8:18 am
Hi Fanatical Labs, thanks for the response.
Why only for 30 days after the send date? Is there a way to change this? This strikes me as restrictive - a lot of mass mails have a long "tail".View Comment
Support September 2nd, 2019 @ 11:32 am
The same question applies for "sent". I see the webhook that determines when the campaign was sent, but I don't see one for each individual send. Is this also done by the scheduler? Or does it just create a "sent" record for each person in the target list when the campaign "sent" notification is received?View Comment
Support August 29th, 2019 @ 12:31 pm
Additionally, it's really unclear which information is needed for which webhooks.
The MailChimp webhook support contains the following: https://developer.mailchimp.com/documentation/mailchimp/guides/about-webhooks/
"type": "unsubscribe", "fired_at": "2009-03-26 21:40:57",
"data[action]": "unsub", "data[reason]": "manual", "data[id]": "8a25ff1d98", "data[list_id]": "a6b5da1054", "data[email]": "firstname.lastname@example.org", "data[email_type]": "html", "data[merges][EMAIL]": "email@example.com", "data[merges][FNAME]": "Mailchimp", "data[merges][LNAME]": "API", "data[merges][INTERESTS]": "Group1,Group2", "data[ip_opt]": "10.20.10.30", "data[campaign_id]": "cb398d21d2", "data[reason]": "hard"
But of these fields, which are the ones necessary to process an unsubscribe? E.g., are the merge fields actually used?View Comment
Support July 25th, 2019 @ 10:48 am
Please close this case - we have uncovered the root of the problem.View Comment
Support July 18th, 2019 @ 2:49 pm
Please can you confirm that there is no configuration option needed to set up the webhook (and if there is where it is).
The Audience is being synced to a Sugar Target List. No security settings have changed.
The question is why webhooks were being created on previous audiences and not subsequent ones.
Please also reply to my comment beginning "If that record is on multiple...
Support July 18th, 2019 @ 2:03 pm
I discovered that previous Audiences created and utilised by MailChimp all had webhooks set up, but recently created ones do not. This is possibly since we upgraded a MailChimp version.
Please can you confirm:
A) That upon creating an Audience in MailChimp that SugarChimp is supposed to populate a webhook for it and B) That there is no configuration option to do this, otherwise C) Where that configuration option is.View Comment
Support July 18th, 2019 @ 1:03 pm
The contact did not update when I edited its name.
Do I need to have a web hook set up in MailChimp?View Comment
Support July 18th, 2019 @ 12:53 pm
"If that record is on multiple synced Mailchimp lists, then we may not want to mark them as unsubscribed as they are still subscribed on other lists."
They should be unsubscribed from the list that they unsubscribed from, surely?
"We have config settings to know how this should work."
Please let me know where - I couldn't find them.View Comment
Support July 18th, 2019 @ 12:26 pm
Please don't close this bug - I'm still working on it.View Comment
Support July 8th, 2019 @ 9:50 am
I note that it says anyone not running 9.0.0 must upgrade. Is that only if we are on SugarCRM 8 or 9? But none of the bug fixes reference a bug like ours.View Comment
Support January 13th, 2019 @ 11:46 pm
This case shouldn't be closed! We will update our version and let you know if we still encounter it.View Comment
Support January 3rd, 2019 @ 9:53 pm
Thanks for your quick response Heidi,
Are you aware of any issues resulting from installing 8.2.2 on SugarCRM 7.9.5?
Also, is there any configuration that could cause this?View Comment
JohnK has not rated any add-ons.
JohnK has not verified any add-ons.
JohnK has not created any Wanted Add-ons.