Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

CommandBar Source


Source Info
  • The CommandBar Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
  • This integration is partner owned. Please reach out to the partner's support for any issues.

CommandBar gives your users a searchable index of your app's features and content, as well as customizable in-app components, like onboarding nudges. Better understand user intent and deliver step-change improvements in UX, for new and power users alike. By connecting Segment to CommandBar as a source, you can deliver search and nudge event data directly into Segment in real-time, enabling you to analyze user intent and product usage data in your preferred data tools and enrich user profiles.

This source is maintained by CommandBar. For any issues with the source, contact the CommandBar Support team.


Getting Started

getting-started page anchor
  1. From your workspace's Sources catalog page(link takes you to an external page) search for "CommandBar" and click Add Source.
  2. On the next screen, give the Source a nickname configure any other settings. The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you'll be querying against in your warehouse.
  3. Copy the Write Key from the Segment UI. If you are not sure where to find your write key, visit Segment's help document.
  4. Log in to your CommandBar account(link takes you to an external page), and navigate to the Segment integration page(link takes you to an external page).
  5. Paste your Segment Write Key into the text box.
  6. Click "Connect".
  7. [Optional] Send a test event from the CommandBar Segment integration page(link takes you to an external page), and check your Segment Source Debugger to ensure the integration is properly configured.

Below is a table of events that CommanBar can send to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations. The type name corresponds to the value of the "type" key inside the event's properties.

Event NameType nameDescription
IdentifyN/ACommandBar booted
OpenedopenedCommandBar opened
ClosedclosedCommandBar closed. When the bar is closed with input text, it triggers both a closed event and a dead end event. Executions do not trigger closed events.
Abandoned Searchabandoned_searchA dead end(link takes you to an external page)
Command Suggestioncommand_suggestionCommand suggested
Command Executioncommand_executionCommand executed
No Results For Queryno_results_for_queryUser's search returned no results
Nudge Shownnudge_shownNudge shown
Nudge Clickednudge_clickedNudge clicked
User Changed Shortcutshortcut_editedUser edited a command's shortcut

Each event has its own unique properties. There are also some properties that are shared across events.

All events

all-events page anchor
Property NameDescriptionType
end_userThe user's ID.string
organizationThe CommandBar organization ID.string
searchThe unique ID for the user's search, if relevant.string
sessionThe unique ID for the user's session.string
typeThe name of the event.string
user_typeThe type of user.string
Property NameDescriptionType
formFactorThe form factor for CommandBar, when loaded for the user."modal" , "inline"
userAttributesAttributes that are specific to the user, and which are included in the boot call.object
Property NameDescriptionType
triggerThe entrypoint through which the bar was opened."launcher" , "keyboard" , "programmatic"
Property NameDescriptionType
inputTextThe user's input text when the bar was closed.string
Property NameDescriptionType
inputTextThe text of the dead end.string
triggerThe trigger for the dead end."Backspaced" , "Closed with text" , "Resetting search"
commandThe id of the currently active command, if there is one.number
resourceThe context key of the currently active resource, if there is one.string
resultsInformation about the results being displayed when the dead end happened.object
Property NameDescriptionType
textThe text of the suggestion.string
Property NameDescriptionType
commandThe unique id of the command. For commands defined in the Editor, the value will be a number. For programmatic commands, the name (string) provided will be used.numberstring
commandDetailsThe details of the command.object
commandTextThe text of the command.string
categoryThe category id of the command. Only provided if the command has a category.number
formFactorThe form factor of CommandBar."modal""inline"
placeholderThe text of the placeholder of CommandBar.string
previousCommandsThe IDs of commands executed by the user earlier in the same session.string[]
rankingThe ranking order of the command, if relevant.number
shortcutTrue and only provided if this command was triggered by a shortcut.boolean
sourceSource of the executed command."standard""programmatic"
customShortcutShortcut string if this command has a custom user-set shortcut.anystring
inputTextThe text of the user's query.string
iconThe icon of the command, either a path or an SVG.string
urlThe URL of the command. Only provided if the command is a Link command.string
Property NameDescriptionType
inputTextThe text of the user's query.string
Property NameDescriptionType
idThe ID of the nudge.number
slugThe slug or name of the nudge.string
frequency_limitThe frequency limit of the nudge, for example no_limit.string
on_selectThe command to execute when the nudge is clicked.object
triggerThe trigger for the nudge.object
Property NameDescriptionType
idThe ID of the nudge.number
slugThe slug or name of the nudge.string
frequency_limitThe frequency limit of the nudge, for example,no_limit.string
on_selectThe command to execute when the nudge is clicked.object
triggerThe trigger for the nudge.object
Property NameDescriptionType
commandThe unique id of the command. For commands defined in the Editor, the value will be a number. For programmatic commands, the name (string) provided will be used.number, string
commandTextThe text of the command.string
categoryThe category id of the command. Only provided if the command has a category.number
sourceSource of the executed command."standard", "programmatic"
defaultShortcutThe command's default shortcut. Empty string if the command does not have a default set.string
oldShortcutPreviously set shortcut of the command.string
newShortcutThe new user-set shortcut of the command.string

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.

If you experience any issues with how the events arrive in Segment, contact the CommandBar team.