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. 

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

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 BCC'd 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.

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.

BCC feature for emails

You can set BCC recipients in the trigger settings and send a copy of the email to a set of specified email addresses whenever an email is sent to a customer.

If you need to archive every email sent out of the Blueshift platform, Blueshift allows you an automated way of doing so via the BCC settings on the email adapter config screen.

You can choose to BCC your message either natively or as a separate message

  • If you choose to BCC the email as a separate message:
    • It will be counted as an additional message and will double your send cost
    • Any campaign engagement stats associated with these BCC sends would be distinct from the actual campaign engagement stats. 
  • If you choose the native BCC option:
    • You will be paying for just one message. 
    • Any engagement with the BCC message would be indistinguishable from any engagement with your original message and will be included in your original campaign stats. 

Contact support@blueshift.com to determine the right BCC option for your account.

email_bcc.png

 

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

Comments

0 comments

Please sign in to leave a comment.