Blendo Destination

Blendo is an ELT platform that syncs all your sales, marketing, financial or any other data, from your SaaS tools to your data warehouse.

This destination is maintained by Blendo. For any issues with the destination, contact the Blendo Support team.

Getting Started

Before you start, make sure Blendo supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

1. From the Segment web app, click Catalog.
2. Search for “Blendo” in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the “API Key” into your Segment Settings UI that was created when you set up your Segment pipeline. If you don’t have it available, log in to your Blendo account and select the Segment pipeline you want to sent data to. Click on the “Edit” button and copy the “API Key” as shown in the modal window that appears.
4. Blendo will collect any Segment data as soon as they arrive but will sync data to your data warehouse according to your pipeline’s schedule. By default, this is at the start of each hour. You can also manually sync any collected data by selecting your Segment pipeline from your pipelines’ list, and clicking “Sync Now” on the overview section of your pipeline’s syncing status.

Page

If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:

analytics.page()

Page calls will be sent to Blendo as a pageview, which will be copied to your page table

Screen

If you’re not familiar with the Segment Specs, take a look to understand what the Screen method does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Screen calls will be sent to Blendo as a screenview, which will be copied to your screen table

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

Identify calls will be sent to Blendo as an identify event, which will be copied to your identify table

Track

If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button')

Track calls will be sent to Blendo as a track event, which will be copied to your track table

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Key

Select your Segment pipeline and preview its settings for the API Key.