The following information explains more about how Subscribe and Unsubscribe campaigns work.
Subscribe Campaigns:
- Subscribe campaigns can welcome customers to a conversation and confirm that they want to
receive e-mail in the future for the conversation.
- Subscribe campaigns can automatically subscribe the customer to the conversation when the
message is sent, or set the customer's subscription record to
Opting-in.
- Customers who are set to Opting-in only receive messages if they respond to the welcome
message. If the customer does not reply to the message, their status remains
Opting-out and will NOT receive any future e-mails for that
conversation.
- Opt-in campaigns require the Active Double Permissions Reply Handler to be active for the
message.
- Customers added using the Customer Browser or Connect Conduits are sent a welcome message
associated with a Subscribe campaign when they are added to the
database.
- Only customers added to the database after a welcome message is launched are sent a message. Any
customers already subscribed to the conversation do NOT receive the
message.
- Subscribe campaigns behave like an event-triggered campaign. Adding the subscription record in
the database using Core Conduits for Connect or the Customer Browser creates
an event for the subscribe campaign.
- Instances are NOT created in the instance report for each customer added to the database. A
single instance is created for the Subscribe Campaign for the entire week.
At the end of the week, the instance is replaced with a new instance, and
customers added for that week are included in the new instance.
- Individual instance rows are created for all staged messages.
- New Welcome Message content replaces existing Welcome Message content when it is launched. The
old content is automatically expired when the new content is launched.
- The content of a Welcome Message is treated like all other message content in the system.
Unsubscribe Campaigns:
- Unsubscribe campaigns must be launched to send the message.
- Unsubscribe requests processed by the Unsubscribe reply handler receive the Unsubscribe
message.
- When a customer opts-out, the customer's status code is set to Unsubscribe if an unsubscribe
message is processed by the unsubscribe reply handler.
- The unsubscribe message is an unsubscribe confirmation sent to the customer.