Blueshift enables large-scale consumer marketers to automate hyper-personalized ‘Segment of One’ marketing, combining dynamic segmentation with highly personalized content, across multiple marketing channels.
Note: Blueshift leverages User Identity Change (UIC) events to trigger identity calls within their system. If you do not trigger a UIC event, event data forwarded to Blueshift for that user may not be mapped to a Blueshift user profile. As an alternative, you can ask Blueshift to whitelist other event types to be leveraged for Blueshift identity calls. Please reach out to your Blueshift account manager if you believe this may be required for your account.
mParticle supports both a server-to-server integration and a client-side kit integration. In-app events and events associated with push notifications will be sent client-side to Blueshift via Blueshift’s SDK in conjunction with this kit. All other events will be sent via the server-to-server integration.
You can find Blueshift’s Kit implementations and details on how to configure them below.
Add the Blueshift Kit to your iOS or Android app and the mParticle SDK will automatically route appropriate event data to Blueshift client-side.
//Sample Podfile
target '<Your Target>' do
pod 'Blueshift-mParticle-Kit'
end
//Sample build.gradle
dependencies {
compile 'com.blueshift:android-mparticle-kit:+'
}
Blueshift supports retrieving data for up to 24 hours.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Event API Key | string |
Event API key used to send click-stream data to BlueShift API - You will need an event-stream API key which is accessible from Blueshift dashboard at https://app.getblueshift.com/dashboard#/account_setup. or contact success@getblueshift.com. |
Was this page helpful?