Blueshift offers several ways to trigger messages based on a user action. While some use cases might require the use of Blueshift's API, many transactional emails can be setup in the UI using segment triggered campaigns.

For additional resources visit the Blueshift Developer Portal or API Docs.

Event-based using API endpoint

Typically will be used for credit card declines, password reset or other time sensitive transactional emails that are triggered from one our our systems. For more information visit the Campaign Execution API Reference.

Event-based using “event” data

Some "events" are currently not linked to the transactional data objects that have been moved from Advantage to Blueshift. You can reference those events here. Please see “Segment Based Campaigns” below to send a communication based on Advantage data objects such as list, subscription, and product.

Segment based Campaigns

These types of campaigns are based on users entering a segment. Transactional data from list, subscription, or product can be used to build segments. These are useful for welcome/exit gauntlets, renewal series, or catalog changes such as newly published web content.

For more information visit the Segment Triggered Campaigns section of this wiki. 

Template and Campaign API endpoint

In certain cases you may want to send escaped HTML content to Bsft to create/update a template, with a template defined, you can create/update/execute a campaign using the HTTP POST method. Useful in certain cases where formatting of HTML is handled and defined outside of Blueshift

For more information visit the Template and Campaign API Reference.

Catalog and Recommendation Studio

Used mainly for storing and sharing content or products published to your website . Once catalogs and items are available, recommendations can be created to deliver unique & personalized messages for every user in a marketing campaign. 

For more information visit the catalogs and recommendations documentation.