Skip to main content

CDP integrations overview

CommandBar integrates with the most popular Customer Data Platforms (CDPs) — Twilio, Segment and Rudderstack.

What is the purpose of these integrations?​

CDPs are like the carrier pigeons of CommandBar data to the rest of your product stack. While we have integrations that allow you to send data to many popular tools (like product analytics platforms) directly, a CDP integration expands the scope of where you can send CommandBar data.

These integrations are typically the first our customers enable, because they make it simple to send CommandBar events to any other tool that is connected to the CDP.

What can I do if I use a CDP tool you don’t integrate with?​

Answer: Use our SDK and API​

Fear not. Our integrations are a relatively thin layer on top of some pretty basic general-purpose SDK and API methods that you can use to create your own integration with any third-party CDP.

Sending data from CommandBar​

To do this, you can utilize an event subscriber. Simply create an event subscriber and within the body of that subscriber send the event payload to the CDP of your choice.

// The function that handles CommandBar events
const myHandler = (eventName, eventData) => {
  sendToMyCDP({ name: eventName, ...eventData });
};

// Subscribe to CommandBar events
const unsubPromise = window.CommandBar.addEventSubscriber(myHandler);

// Later, call the function returned by the promise
// to unsubscribe your handler from CommandBar events.
unsubPromise.then((unsub) => unsub());

Sending data to CommandBar​

To send data to CommandBar, you can use the strategies described in our User Properties doc.

  1. Provide audience and other user properties via the boot SDK method
  2. Use the /api/{your_org_id}/bulk-identify API endpoint

Your CDP should be able to provide information to your client via the first method.