Blueshift Source
Good to know: Event Cloud source
The Blueshift Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
This source is supported in US data processing regions.
The Blueshift source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.
Blueshift is an AI powered customer engagement platform for growth marketers. With Blueshift, you can set up programmatic cross-channel marketing campaigns across Email, Mobile, Website and other channels.
Take your company’s email analysis to the next level by adding Blueshift as a Source to Segment. Segment automatically collects email events like Email Delivered and Email Opened, forward them to your destinations, and load them into your data warehouse.
In your favorite BI or analytics tool, you’ll be able to analyze your email campaigns in SQL or through drag-and-drop reports. And, you’ll be able to join your Blueshift data with the event data you’re already sending through Segment to analyze the down-funnel effects of your emails.
Getting Started
- From your workspace’s segment.com/
/sources page, click Add source. - Choose Blueshift.
- Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like Blueshift for nickname and Blueshift for the schema name.
- The next page (“Overview”) will surface your Segment write key for Blueshift. Copy this write key.
- To finish the setup, you’ll have to go into your Blueshift account and enter this Segment write key in their destinations settings. Find the right place in Blueshift by clicking Account > Webhooks:
- Click Save.
- Now when you go back to Segment, click into your Blueshift Source and you’ll be able to add other downstream Destinations where you want to see email events.
That’s it! As you send emails, events will now be sent to your destinations and automatically loaded into any warehouses you have enabled.
Blueshift Events
Below is a table of events that Blueshift sends to Segment. These are the events that will appear in your warehouse or your destinations, depending on what connections you enable in Segment:
| Event Name | Description |
| Email Delivered | Message has been successfully delivered to the receiving server |
| Email Opened | Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event |
| Email Link Clicked | Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event |
| Email Bounced | Receiving server could not or would not accept message |
| Email Marked as Spam | Recipient marked message as spam |
| Unsubscribe | Recipient clicked on message’s subscription management link |
Blueshift Event Properties
Below is a table of properties that are sent for the events above:
| Propert Name | Description |
account_uuid |
UUID of the account |
campaign_uuid |
UUID of the campaign |
bucket_uuid |
UUID of the bucket |
trigger_uuid |
UUID of the trigger |
experiment_uuid |
UUID of the experiment |
creative_uuid |
UUID of the creative (template) |
message_uuid |
Blueshift internal unique uuid associated with the corresponding message send event |
trgger_timestamp |
The timestamp at which this event was generated |
trgger_type |
The type of the trigger. Values can be one of “PushTrigger”, “EmailTrigger”, “SmsTrigger”, “DisplayAdTrigger”, “OnsiteTrigger” depending on the channel of the message |
action |
Blueshift identifiers for the event - “open”, “click”, “delivered”, “bounce”, “spam_report” or “unsubscribed” |
campaign_name |
Name of the campaign |
campaign_exec_term |
Nature of the campaign |
creative_name |
Name of the creative |
utm_* |
All of the utm_campaign, utm_content, utm_medium, utm_source, utm_term on the campaign are sent back on the event |
sg_message_id |
Message id on Sendgrid if the event was triggered by a Sendgrid event |
| Other | All trigger level custom URL tracking parameters added on the campaign are sent back on the event |
UserId
Blueshift sends their customer_id associated with the message recipient as the top level userId field. Additionally, we will also send “email” and “blueshift_user_uuid” under context.traits.
Send Data to Blueshift
The Blueshift Source works better when you also connect Blueshift as a downstream destination within Segment. With the Blueshift Destination, you can send Blueshift user and event data, which you can use to trigger email campaigns. Want to start sending website or mobile to Blueshift? Head on over to our Blueshift destination docs.
This page was last modified: 21 Apr 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!