For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Supported Sources and Connection Modes
The first step is to make sure Blueshift supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
To learn more about about Connection Modes and what dictates which we support, see here.
Segment offers an optional Device-based Connection Mode for Mobile data going to Blueshift, so that you can use Blueshift features that collect data directly from the mobile device. To do this, you must package the Segment-Blueshift mobile SDK with the Segment mobile SDK.
Segment lets you change these destination settings from your Segment dashboard without having to touch any code.
Your API key can be found in Account Profile > API Keys
This will retarget page calls on the client-side
This page was last modified: 25 Nov 2019
Questions? Problems? Need more info? Contact us, and we can help!