Crossing Minds Destination

Destination Info

Crossing Minds is a recommendation platform for businesses using next-gen AI that instantly anticipates customers’ wants and needs using only anonymized user data.

Crossing Minds maintains this destination. For any issues with the destination, contact the Crossing Minds Support team.

This document is about a destination which is in beta

This means that the Crossing Minds Destination is in active development, and some functionality may change before it becomes generally available.

Getting Started

  1. Contact your Crossing Minds Account Manager and request your integration API Key, API Password, and Database ID.
  2. From the Destinations catalog page in the Segment App, click Add Destination.
  3. In the Destinations Catalog, search for “Crossing Minds” and select the “Crossing Minds” destination.
  4. Choose which source should send data to the Crossing Minds destination.
  5. In the Crossing Minds destination settings in Segment, enter the Service Account Name as the API Key, Service Account Password as the API Password, and the Database ID.

Supported methods

Crossing Minds supports the following methods, as specified in the Segment Spec.


Send Identify calls to create or update a Crossing Minds User for any identified user on your site.

For example:

analytics.identify('userId123', {
  email: ''

Segment sends Identify calls to Crossing Minds as an identify event.


Send Track calls to record User Interactions as:

For example:

analytics.track('Login Button Clicked')

Segment sends Track calls to Crossing Minds as a track event. Any events that are not listed in the mentioned categories will be rejected.


You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule 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, Engage 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), Engage sets that value to false.

When you first create an audience, Engage 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.

Real-time to batch destination sync frequency

Real-time audience syncs to Crossing Minds may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


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

Setting Description
API Database ID
string. The Crossing Minds Database ID
string. The Crossing Minds API Service Account Name
API Password
string. The Crossing Minds API password

This page was last modified: 25 Apr 2022

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account