Get analytics directly into your Segment workspace
After adding Cord to your website, you may be interested in running some analytics. We use Segment in order to log our events. The team at Segment is working on a solution that will allow us to offer partners relevant time.
In the meantime, please contact your Cord contact for a secure way to provide us your Segment write key. Here's how you can locate your write key.
{
"event": "cord-[event-name]",
"userId": "USER_ID",
"properties": {
"location": "http://...",
"organization_id": "ORGANIZATION_ID"
// other, event-specific properties
}
}
All our Segment events start with cord-
. This will enable you to use an existing source if you to choose to do so, without the event schemas conflicting. However, we recommend creating a new Segment source for these purposes.
All events include the user ID you have provided us, as well as two permanent properties:
location
organization_id
select-profile
create-new-profile
click-upgrade-plan
update-profile
navigate-to
cord_location
property will contain the tab to which they navigated.render-sidebar-open
connect-service-started
service
property will contain the service the user is connecting; one ofslack
, jira
, asana
, linear
.connect-service-successful
service
property.connect-service-failed
service
property, as well as a reason
property will contain the reason for the failure; one of error
or cancelled
.disconnect-service
service
property.hover-for-presence
insert-mention
insert-assignee
message-send
message-updated
message-deleted
message-delete-undone
create-task
remove-task
thread-resolved
thread-unresolved
subscribed-to-thread
unsubscribed-from-thread
toggle-sidebar-visibility
to = false
if closed, or to = true
if openedlogout
Some events may contain some additional information which would appear in the properties
field of the event:
method
composer-text
, on-it-reaction
.task_provider
cord
, jira
,asana
, linear
.mentions
attachments
annotations
new_thread
cord_location
inbox
,chat
.thread_id