Skip to content
English
Still Need Help? Contact Support
  • There are no suggestions because the search field is empty.

What question is your article answering?

The business logic here is that if we already have a record of someone unsubscribed (at any point) and an integration brings in that same person but "subscribed" we wont set that member to subscribed.An example of this is:
  1. We import a list from Mail Chimp,  comes in as subscribed
  2. We send an email to  and she unsubscribes
  3. We have another import from mail chimp as final clean up but  is still marked as subscribed
  4. We dont override the unsub with sub because we have a record of an opt-out.
The client impact is that they really need to make sure that when importing say from a Mail Chimp its a one and done to make sure we are capturing the opt-in/outs without trying to go back and update.

A few weeks go by, she subscribes via our delightable join pages. That does then override what was previously there from an integration pull?

Yep! It only applies to integrations