Sending a copy of the email to specified users can be helpful for either testing purposes or for simply saving a copy of the email received by your customers. A sample use case for this feature would be to send a copy of the email to a support inbox, so that your customer support staff can reference it. This feature is similar to the BCC in many email clients.

Set BCC recipients in trigger settings

For email triggers in campaigns, you have the ability to send a copy of the email to a set of specified email addresses whenever a user gets messaged.

Important

This feature sends a copy of EVERY email to EVERY user in the trigger, to the specified recipients. Use this feature very carefully.

This feature is hidden by default. Contact support@blueshift.com to enable it.

To send copies of emails, go to the Channel tab of the trigger in your campaign. In the Send Settings, add the required emails addresses in the BCC Every Email To field. By default, the field is blank, which means no copies will be sent.

  • In the text box, enter a comma separated list of email addresses to message.
  • You can also use a Liquid expression to dynamically specify the recipients. For example, if you are running an event-triggered campaign and the event has an attribute "bcc" that is equal to "support@blueshift.com", you can use the Liquid expression "{{bcc}}" and a copy of every email will be sent to "support@blueshift.com" for each user that is messaged.
  • You can even use a combination of hardcoded emails and Liquid.

Note: Email copies are counted as additional sends for billing purposes.

jb_trigger_copyemails.png 

 

The copy that is sent is almost identical to the original email with a few key differences.

  • The first difference is the seed list name is not included in the subject line. The subject line contains {$original subject line} : ( {$customer email} ).
  • The second difference is that these copies do not generate stats like opens or clicks. You can interact with these email copies without affecting the original user's campaign journey.

You can also send a native BCC email where the the BCC recipient and the customer receive the same email from the same send. If the BCC recipient engages with the email (for example, opens it), it will reflect as a customer engagement in your campaign stats and as such will impact your metrics. To switch to the native BCC option, contact support@blueshift.com.

Set default BCC recipients in adapter settings

In your adapter settings, you can specify a set of email addresses in the BCC field. When you use the adapter in any trigger in a campaign journey, the BCC field in the trigger is populated with these email addresses.

 

Was this article helpful?
2 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.