Blueshift can use your SMTP service to send emails that are a part of the campaign journey. Simply enter your SMTP credentials and connect Blueshift with your sending provider.

Tracked events

With SMTP integration for emails, we can track the following:

  • Sends
  • Impressions
  • Unique impressions
  • Clicks
  • Unique clicks
  • Visits
  • Orders
  • Activations
  • Delivered (sent and not bounced)
  • Revenue
  • Bounces
  • Spam reports
  • Unsubscribes

Note: You must send event data back to Blueshift to enable tracking of events.


Before you can set up integration with Blueshift, you must have your SMTP credentials handy.

Set up integration

To integrate your SMTP service with Blueshift, complete the following steps:

  1. Sign in to the Blueshift app, and click App Hub in the left navigation menu.
  2. Go to All Apps, search for, and select SMTP.
  3. You can also go to Email Apps and select SMTP.
  4. Click Configure to view all the configured adapters.
  5. Click +ADAPTER to add an adapter.
  6. Add a Name for the adapter.  If you have multiple adapters, the adapter name helps you to identify the integration.
  7. Provide the following details for integration:


    Alias Name Specify an alias name of the adapter for identification.  
    SMTP Server Address Provide the fully qualified domain name (FQDN)/IP address of the SMTP server. You can get this from your email service provider or specify the address of the server that hosts the SMTP service.  
    SMTP Port Specify the port on which the SMTP service listens. You can get this setting from your provider or specify the configuration if you are using a hosted service. For example, SMTP port is mostly 587, if your SMTP service is using TLS encryption.  
    Username Specify the SMTP server username for authentication. Your SMTP server uses this credential to identify if the request to send/receive an email comes from an authorized source. 
    Password Specify the SMTP server password for authentication. Your SMTP server uses this credential to identify if the request to send/receive email comes from an authorized source. 
    Authentication Type

    Choose the authentication type. This specifies how the SMTP service authorizes requests to send and receive emails through it. We will use this information to make the appropriate authentication request to the service, so that we are authorized to send and receive emails. 

    Your options for authentication type are: None, Plain, Login, and CRAM MD5.

    Encryption Type

    Choose the encryption type. This specifies how the SMTP service encrypts the emails that it sends.

    Your options for encryption type are: None, STARTTLS, SSL, and TLS.

  8. In addition to the mandatory fields above, you can provide the following optional details:  From Name, From Address, and Reply To Address.
    • API key: If your vendor requires an API key, get the API key from your vendor and specify it here. 
    • From Name: Specify a name that we will use as an alias to send emails. 
    • From Address: Specify an email address that we will use as the sender's address. 
    • Reply To Address: Specify an email address to which a recipient can send an email response. 
    • Whitelable host name (CNAME): Specify the domain name of the server on which you host your SMTP service. 
  9. Click Save to add the adapter.

Next steps

  1. Create an Email template for your messages.
  2. In your campaign journey, add an Email trigger. On the Email tab of the trigger, go to Send Settings and specify SMTP Relay as the App and select the adapter that you just created.
  3. Send events data to Blueshift for analytics and tracking.

Send event data to Blueshift

If you are using an SMTP service to send campaign messages, you can send event data back to Blueshift by using the following URL.

  • If you are in the EU region, use the hostname instead of
  • Ensure that you use the correct field names when you send event data to Blueshift.
  • The event field can have the following values: delivered, soft_bounce, bounce, spam_report, and unsubscribe.
  • The following fields must be sent to Blueshift along with the event field:
    • email
    • experiment_uuid
    • user_uuid
    • message_uuid
    • execution_key
    • journey_uuid

Example for a delivered event:

  "email" : "", 
  "timestamp" : 1513299569, 
  "experiment_uuid" : "5192f38e-7094-4dfd-9138-9579aca8f1e3", 
  "user_uuid" : "ecd0474c-fb76-4e59-a321-c6ce558aac5c", 
  "message_uuid" : "1840a829-a4e9-4044-b1f3-7ce9edf120f4", 
  "execution_key" : "2020-06-18T19:02:40Z", 
  "journey_uuid" : "a977ef6b-945c-4e78-a938-8d8f0726f2a8", 
  "user_transaction_id" : "lists_7fc56270e7a70fa81a5935b72eacbe29", 
  "retailer_customer_id" : "159230", 
  "event" : "delivered" 
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.