Events
Events are used to tell Command AI when the user experiences things in your product. The more events Command AI is aware of, the better targeting rules you can create to ensure your experiences are timely and helpful, and not annoying.
What kinds of events should I provide to Command AI?
It’s easy to send any event you want to Command AI, but what events should you send?
As a starting point, you should send Command AI any events caused by user interactions where you want a nudge to trigger. For example, if you want to trigger a nudge on a button press, you should send Command AI an event on that interaction. This also applies to checklist completion conditions.
For interactions in your app where something changes already (for example, a button that triggers a pop-up or a button that triggers a path change), you don’t have to send events — Command AI can automatically use those as triggers without having to explicitly send an event.
Connecting events via integration
Our integrations with various analytics providers, including Segment and Heap. This means that any events being captured by these tools are automatically provided to Command AI when they happen.
Note that our server-side integrations do not currently support event streaming. Only integrations that connect on the client-side (like our Segment client-side integration) allow event streaming. Server-side integrations support the setting of user properties only.
Creating events manually
If you don’t use an analytics provider and/or want to provide extra events not currently captured by those tools, you can use the Command AI SDK to trigger events manually. This approach is easy. (usually a 5-minute exercise involving one line of code) but requires a developer.