You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When someone unsubscribes (or you do it through MC admin interface), MC sends a webhook. CiviCRM then begins removing the contact from the various groups. But hook_civicrm_post realises that someone is being removed from a MC group, and triggers a MCAPI delete operation on that email.
This means that the unsubscribe information is completely deleted from MC; you will not (presumably) then be able to tell how many people unsubscribed as the result of a particular campaign etc.
I would have expected that CiviCRM removed the contact from the MC groups, but did NOT tell MC to actually delete the account.
I think this is a bug because it degrades the MC reporting functionality, which is one of the main reasons for wanting to use Mailchimp instead of CiviCRM for mailings.
The text was updated successfully, but these errors were encountered:
This had me flummoxed!
When someone unsubscribes (or you do it through MC admin interface), MC sends a webhook. CiviCRM then begins removing the contact from the various groups. But hook_civicrm_post realises that someone is being removed from a MC group, and triggers a MCAPI delete operation on that email.
This means that the unsubscribe information is completely deleted from MC; you will not (presumably) then be able to tell how many people unsubscribed as the result of a particular campaign etc.
I would have expected that CiviCRM removed the contact from the MC groups, but did NOT tell MC to actually delete the account.
I think this is a bug because it degrades the MC reporting functionality, which is one of the main reasons for wanting to use Mailchimp instead of CiviCRM for mailings.
The text was updated successfully, but these errors were encountered: