Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This document presents a brief description of the different datasets Worklytics is able to export to its customers.
Each file will hold a week worth of data. We consider weeks in ISO format, so weeks start on Monday.
From the Data Export Connections section in the Worklytics Web App, you can export any of the available datasets to the Cloud Provider of your choice. For detailed instructions specific to each provider, refer to the corresponding documentation.
Depending on your Worklytics subscription and enabled features, you may not have access to all of these data sets; or additional charges may apply. Please contact sales@worklytics.co.
Worklytics assumes no responsibility for Customer use or management of exported data. In particular, such data is no longer subject to our Privacy Policy, Terms of Service, or any applicable agreements between Worklytics and the Customer Organization.
By initiating or requesting a data export, Customer agrees to ensure that all subsequent usage, management, and retention of exported data by the Customer is consistent with all applicable laws, data protection regulations, and labor/employee/contractor agreements. Customer acknowledges that data exports may include Personally Identifiable Information (PII), which may impose particular data protection requirements on the data.
Additionally, data exports may include information that could be considered sensitive, confidential, or private. Please take care in your usage of the data to avoid inadvertent disclosures of such information. The simplest way to do this is to avoid exposing any non-aggregated data from the Items/Events dataset to end users (ie, humans), and in particular any text fields. Should you choose to expose data from that set to end users, we recommend that you endeavor to respect the privacy models of the underlying data sources.
This is how an output folder with all types might look depending on the format and compression options selected.
bucket/folder/
aggregates/
acmeorg_ANONYMIZED_AGGREGATES_20230327Z.parquet
collaboration-graph/
acmeorg_ANONYMIZED_COLLABORATION_GRAPH_SPLIT_20230327Z000000000000.avro
acmeorg_ANONYMIZED_COLLABORATION_GRAPH_SPLIT_20230327Z000000000001.avro
collaboration-graph-split/
acmeorg_ANONYMIZED_COLLABORATION_GRAPH_SPLIT_20230327Z00000000000N.avro
acmeorg_ANONYMIZED_COLLABORATION_GRAPH_SPLIT_20230327Z00000000000N.avro
events/
acmeorg_ANONYMIZED_EMPLOYEE_EVENTS_20230327Z.json.gz
acmeorg_ANONYMIZED_EMPLOYEE_EVENTS_20230327Z.json.gz
items/
acmeorg_ANONYMIZED_ITEMS_20230327Z000000000000.avro
acmeorg_ANONYMIZED_ITEMS_20230327Z000000000001.avro
Each export will contain a week's worth of data and a week column. Given that we occasionally need to reprocess and re-send data, the simplest way to ensure that all the data is up-to-date is to automate the following steps via your internal systems:
Look in the bucket for new files to import since the last successful import.
Load the files in a temporary table.
Delete all the data in the main table for the weeks found in the temp table.
Copy all the contents of the temp table into the main table.
Filename
organizationName_ANONYMIZED_AGGREGATES_YYYYMMDDZ.extension
Variables:
organizationName: the slugified name of the organization
YYYYMMDD, the week this file contains data from. Week is in ISO format, meaning that Monday is considered the first day of the week.
extension, depending on the format and compression, see below:
Available formats
| Format | Compression | Extension |
|---|---|---|
This file contains data that Worklytics has preprocessed and aggregated at the week level. Depending on the metric in question, data is either inferred from connected customer data sources or calculated by Worklytics.
NDJSON example (note examples are pretty printed for documentation purposes otherwise will be presented in one row each)
Note that not all metrics in the table below will necessarily appear in your company’s export, as some require specific data connectors (e.g., if your company has not connected GitHub, you will not see any of the github: metrics). The list of metrics may change as aggregates are added over time.
Filename
collaboration-graph/organizationName_ANONYMIZED_COLLABORATION_GRAPH_YYYYMMDDZ00000000000N.extension
Variables:
default prefix: collaboration-graph/
organizationName: the slugified name of the organization
YYYYMMDD, week this file contains data from. Week is in ISO format, being Monday first day of the week.
due to size file might be split into N consecutive chunks using the suffix 0000000000N.
extension, depending on the format and compression, see below:
Available formats
| Format | Compression | Extension |
|---|---|---|
Provides a flattened version of the collaboration graph for the company on a given week. Each row has a source employee id, meaning is the person that initiated the collaboration work and a target employee id, the person with whom collaborated. Also the total amount of time of that collaboration during the week, in seconds and in minutes.
NDJSON example (note examples are pretty printed for documentation purposes otherwise will be presented in one row each)
Filename
collaboration-graph-split/organizationName_ANONYMIZED_COLLABORATION_GRAPH_SPLIT_YYYYMMDDZ00000000000N.extension
Variables:
default prefix: collaboration-graph-split/
organizationName: the slugified name of the organization
YYYYMMDD, week this file contains data from. Week is in ISO format, being Monday first day of the week.
due to size file might be split into N consecutive chunks using the suffix 0000000000N.
extension, depending on the format and compression, see below:
Available formats
Provides a flattened version of the collaboration graph for between individuals in the company on a given week. Each row has a source employee id, meaning is the person that initiated the collaboration work and a target employee id, the person with whom collaborated, the tool they used to collaborate and the total amount of time of that collaboration during the week, in seconds and in minutes (rounded) For a pair of employee source and employee target there will be as many rows as different tools they used to collaborate on a given week.
NDJSON example (note examples are pretty printed for documentation purposes otherwise will be presented in one row each) of two rows for the same pair of collaborators, but different tools
Note: Work Events datasets are only available in Datastream Enterprise tiers. Please contact sales@worklytics.co for more information
Filename
events/organizationName_ANONYMIZED_EMPLOYEE_EVENTS_YYYYMMDDZ.extension
Variables:
default prefix: events/
organizationName: the slugified name of the organization
YYYYMMDD, week this file contains data from. Week is in ISO format, being Monday first day of the week.
extension, depending on the format and compression, see below:
Available formats
| Format | Compression | Extension |
|---|---|---|
Note: CSV is not supported for this file because is not able to represent nested objects.
Source: the tools the organization has connected through Worklytics. Examples:
GDrive, Slack, Zoom, GCalendar, GMail, Google Directory, MSFT Office...
Objects: model pieces of work. Examples of objects:
Document or a file in GDrive
Slack channel
Zoom meeting
Calendar event
Event: actions that happened to an object, performed by employees. Examples of events:
Comment, upload or edit a document
Message sent in a Slack channel
Zoom meeting occurrence (the actual action of attend a meeting)
Calendar event attendance
Work Item: either an object or an event
Time Spent: Worklytics' estimation of the amount of time a person worked on the event
This file represents an unnested version of the Items file, showing all events per employee and their estimated time spent on each within a given week.
Each row is a Json object with nested objects. The structure is intended to hold heterogeneous work sources so contents of certain fields may vary depending on the item type. Properties and metrics fields are a good example of this, for example Calendar meetings may have location, Slack message's' may have a message length or Zoom meetings may encode whether they are recurring or not. An entry may be an object and/or an event. Events have the boolean field "event" value set to true.
NDJSON example (note examples are pretty printed for documentation purposes otherwise will be presented in one row each)
Here is an example of how a meeting looks like:
List of possible values for items and relations. List may grow over time.
Note: Work Items datasets are only available in Datastream Enterprise tiers. Please contact sales@worklytics.co for more information
Filename
items/organizationName_ANONYMIZED_ITEMS_YYYYMMDDZ00000000000N.extension
Variables:
default prefix: items/
organizationName: the slugified name of the organization
YYYYMMDD, week this file contains data from. Week is in ISO format, being Monday first day of the week.
due to size file might be split into N consecutive chunks using the suffix 0000000000N.
extension, depending on the format and compression, see below:
Available formats
| Format | Compression | Extension |
|---|---|---|
Note: CSV is not supported for this file because is not able to represent nested objects.
Source: the tools the organization has connected through Worklytics. Examples:
GDrive, Slack, Zoom, GCalendar, GMail, Google Directory, MSFT Office...
Objects: model pieces of work. Examples of objects:
Document or a file in GDrive
Slack channel
Zoom meeting
Calendar event
Event: actions that happened to an object, performed by employees. Examples of events:
Comment, upload or edit a document
Message sent in a Slack channel
Zoom meeting occurrence (the actual action of attend a meeting)
Calendar event attendance
Work Item: either an object or an event
Time Spent:Worklytics' estimation of the amount of time a person worked on the event
This file shows a combination of items and events associated to them for a given week. Each row is a Json object with nested objects. The structure is intended to hold heterogeneous work sources so contents of certain fields may vary depending on the item type. Properties and metrics fields are a good example of this, for example Calendar meetings may have location, Slack message's' may have a message length or Zoom meetings may encode whether they are recurring or not. An entry may be an object and/or an event. Events have the boolean field "event" value set to true.
NDJSON example (note examples are pretty printed for documentation purposes otherwise will be presented in one row each)
Here is an example of how a meeting looks like:
This is what an event attendance looks like:
List of possible values for items and relations. List may grow over time.
You can export the data to any of the supported Cloud Storage Providers. All providers work in a similar way: your organization, as tenant of the Worklytics platform, is assigned with a Google Cloud Platform (GCP) service account (SA) that will be used to export the data to the Cloud Storage Provider of your choice via Workload Identity Federation.
All providers need a series of prerequisites to be met before you can set up the connection in the Worklytics Web App: create some storage resources (such as the bucket/container where the data will be exported) to and give access to them to your Worklytics' tenant account.
Once those prerequisites are met, you can create a in the Worklytics Web App by choosing the desired dataset, configuring its settings (file format, compression, etc.), and providing the necessary information about your storage resources (e.g. bucket/container name).
The user that creates the Data Export needs to have the DataExportAdmin role. Check the documentation for more information.
Whatever the provider you choose, we recommend creating a dedicated bucket/container for the data export and use the Terraform modules we provide to automatically provision the necessary resources, instead of creating them manually. See the detailed instructions for each provider:
(beta)
To export data from Worklytics to Google Cloud Storage (GCS) buckets, you can set up a in the Worklytics Web App selecting Google Cloud Storage as Data Destination.
Your organization, as tenant of the Worklytics platform, is assigned with a Google Cloud Platform (GCP) service account (SA) that will be used to export the data to your GCS bucket via Workload Identity Federation.
Your tenant SA must be granted with the necessary permissions to access your GCS bucket where data will be exported.
Take note of your Worklytics' tenant Service Account email address: you can find this in the page of the Worklytics Web App, and also on the UI to create the data export itself.
Go to the and create a new bucket (o choose an existing one).
Grant Worklytics' tenant SA with the GCP IAM role of Storage Object Admin (roles/storage.objectAdmin) or a similarly restrictive role that permits object creation and listing within the bucket.
We provide a that will automatically provision these resources for you.
Go to the section in the Worklytics Web App.
Select the dataset you want to export, and its frequency.
Select Google Cloud Storage as Data Destination, and enter the Bucket Name.
Select the format and compression options, and click on "Create Export".
To export data from Worklytics to Azure (Blob Storage) containers, you can set up a in the Worklytics Web App selecting Google Cloud Storage as Data Destination.
Your organization, as tenant of the Worklytics platform, is assigned with a Google Cloud Platform (GCP) service account (SA) that will be used to export the data to your GCS bucket via Workload Identity Federation.
Your tenant SA must be granted with the necessary permissions to access your Azure Blob Storage container where data will be exported.
Take note of your Worklytics' tenant SA Unique ID: you can find this value in the page of the Worklytics Web App, and also on the UI to create the data export itself.
Go to the and select a Storage Account (or create a new one).
Inside the Storage Account, create a new container (or choose an existing one).
Go to the Entra ID section of the portal and create a new application registration. Note the application's cliend ID (this is the "Application ID" value in the properties section of the application).
Setup Federated Identity Credentials for the application: go to the "Certificates & secrets" section of the application and create a new Credential with the following values:
Federated credential scenario: choose "Other issuer"
Issuer: https://accounts.google.com
Subject identifier: your Worklytics' tenant SA Unique ID
Audience: api://AzureADTokenExchange
Now, go to the "Access control (IAM)" section of the Storage Account and add a new role assignment using:
Role assignment: Storage Blob Delegator
Member granted with the role: The Service Principal that represents the application.
Repeat the same step, this time inside the container you've created:
Role assignment: Storage Blob Data Contributor
Member granted with the role: The Service Principal that represents the application.
Note: role assignment changes may take a few minutes to take effect.
Finally, take note of the values you'll need to provide when configuring the Data Export in the Worklytics Web App:
Storage Account Name
Container Name
Application ID (Client ID)
Tenant ID: in the Azure portal, find this under "Home > Microsoft Entra ID > Overview > Tenant ID".
Select the dataset you want to export, and its frequency.
Select Azure as Data Destination, and enter all the values from the step number 7 of the pre-requisites.
Select the format and compression options, and click on "Create Export".
To export data from Worklytics to Amazon Web Services (AWS) S3 buckets, you can set up a in the Worklytics Web App selecting Amazon S3 as Data Destination.
Your organization, as tenant of the Worklytics platform, is assigned with a Google Cloud Platform (GCP) service account (SA) that will be used to export the data to your AWS S3 bucket via Workload Identity Federation.
Your tenant SA must be granted with the necessary permissions to access your AWS S3 bucket where the data will be exported.
Take note of your Worklytics' tenant Service Account Unique ID: you can find this value in the page of the Worklytics Web App, and also on the UI to create the data export itself.
Go to the and create a new bucket (or choose an existing one).
Create an AWS IAM role and allow your Worklytics' tenant SA to assume it, but configuring the role assumption policy.
Grant the role s3:PutObject, s3:GetObject, and s3:ListBucket permissions on the chosen bucket.
We also provide a that will automatically provision these resources for you.
Go to the section in the Worklytics Web App.
Select the dataset you want to export, and its frequency.
Select Amazon S3 as Data Destination, and provide the following values:
Enter the Bucket Name.
Enter the Role ARN: created in the pre-requisites. It's the role that your Worklytics' tenant SA will assume to access the bucket.
Enter the Region where the bucket is located.
Select the format and compression options, and click on "Create Export".
Worklytics assumes no responsibility for Customer use or management of exported data. In particular, such data is no longer subject to our , , or any applicable agreements between Worklytics and the Customer Organization.
By initiating or requesting a data export, Customer agrees to ensure that all subsequent usage, management, and retention of exported data by the Customer is consistent with all applicable laws, data protection regulations, and labor/employee/contractor agreements. Customer acknowledges that data exports may include Personally Identifiable Information (PII), which may impose particular data protection requirements on the data.
Additionally, data exports may include information that could be considered sensitive, confidential, or private. Please take care in your usage of the data to avoid inadvertent disclosures of such information. The simplest way to do this is to avoid exposing any non-aggregated data from the Items/Events dataset to end users (ie, humans), and in particular any text fields. Should you choose to expose data from that set to end users, we recommend that you endeavor to respect the privacy models of the underlying data sources.
| NAME | TYPE | DESCRIPTION |
|---|
This schema is generated dynamically based on the groups provided by the customer. Fixed columns are:
employeeId
week
active
The following table shows all possible columns, final customer export might differ.
| Field | Type | Description |
|---|---|---|
| Field | Type | Description and examples |
|---|---|---|
| Format | Compression | Extension |
|---|---|---|
| Field | Type | Description and examples |
|---|---|---|
| Field | Type | Description and examples |
|---|---|---|
| Source (integrationId) | Item type | Relation type |
|---|---|---|
| Field | Type | Description and examples |
|---|---|---|
| Source (integrationId) | Item type | Relation type |
|---|---|---|
Go to the section in the Worklytics Web App.
| NAME | TYPE | DESCRIPTION |
|---|
| NAME | TYPE | DESCRIPTION |
|---|
| NAME | TYPE | DESCRIPTION |
|---|
NONE,GZIP
.csv[.gz]
NONE,GZIP
.json[.gz]
NONE,DEFLATE,SNAPPY
.avro
NONE,SNAPPY,GZIP,ZSTD
.parquet[.gz]
employeeId
STRING
Pseudonymized ID of the employee whose work is summarized in the aggregate (ID may be un-pseudonymized for non-proxy users)
week
DATE
ISOWEEK when that work occurred
key
STRING
Metric name (see "Weekly aggregate definitions" below for details)
value
FLOAT
Metric value
NONE,GZIP
.csv[.gz]
NONE,GZIP
.json[.gz]
NONE,DEFLATE,SNAPPY
.avro
NONE,SNAPPY,GZIP,ZSTD
.parquet[.gz]
week
DATE
Week when collaboration happened
employeeIdSource
STRING
Employee that initiated the collaboration
employeeIdTarget
STRING
Employee affected by employeeSourceId events
weeklyCollaborationTimeSeconds
INTEGER
Time of collaboration in the week expressed in seconds. Collaboration is the sum of the estimated time employeeIdSource spent on all events that were related with employeeIdTarget.
weeklyCollaborationTimeMinutes
FLOAT
weeklyCollaborationTimeSeconds but expressed in minutes
NONE,GZIP
.csv[.gz]
NONE,GZIP
.json[.gz]
NONE,DEFLATE,SNAPPY
.avro
NONE,SNAPPY,GZIP,ZSTD
.parquet[.gz]
week
DATE
Week when collaboration happened
employeeIdSource
STRING
Employee that initiated the collaboration
employeeIdTarget
STRING
Employee affected by employeeSourceId events
sourceType
STRING
The type of events (gcal, gdrive, outlook-cal, zoom, slack, jira...)
weeklyCollaborationTimeSeconds
INTEGER
Time of collaboration in the week expressed in seconds. Collaboration is the sum of the estimated time employeeIdSource spent on all events of the particular sourceType that were related with employeeIdTarget.
weeklyCollaborationTimeMinutes
FLOAT
weeklyCollaborationTimeSeconds but expressed in minutes
NONE,GZIP
.json[.gz]
NONE,DEFLATE,SNAPPY
.avro
NONE,SNAPPY,GZIP,ZSTD
.parquet[.gz]
employeeId
STRING
Employee ID
sourceKindId
STRING
Source of event
id
STRING
The id of the event
eventType
STRING
Type of event: meeting, email, message, document
relationType
STRING
Type of action the employee did (meeting attendance, email sent, message sent, document edited)
eventTime
DATETIME
When the event took place in employee's timezone
eventTimeUTC
TIMESTAMP
When the event took place in Universal Time Coordinated
timeZone
STRING
Employee's time zone
relationProperties
RECORD
Properties associated with the action (example: RSVP status on meeting, lenght of comment,...)
├─ name
STRING
Name
├─ value
STRING
Value
eventProperties
RECORD
Properties of the event, vary across sources (meeting is recurrent, email thread-id, ...)
├─ name
STRING
Name
├─ value
STRING
Value
metrics
RECORD
Metrics for the event. Can be collected from source or derived. Value can either be numeric or a date
├─ name
STRING
Metric name
├─ value
FLOAT
Numeric value (examples: meeting duration, file size)
├─ dateValue
TIMESTAMP
Timestamp (example: meeting start)
estimatedTimeSec
FLOAT
Time spent working exclusively on this event given their concurrent work (in seconds). Equivalent to item's exclusiveTimeSpent
estimatedEventDurationSec
FLOAT
Estimated event duration (in seconds). Equivalent to item's directTimeSpent
parentId
STRING
Parent id of the work item if any
gapps_groups
manager
gapps_groups
member
gapps_groups
owner
gcal
attendance
attendee
gcal
attendance
creator
gcal
attendance
organizer
gcal
attendance
resource
gcal
event
attendee
gcal
event
creator
gcal
event
organizer
gdrive
file
owner
gdrive
file
reader
gdrive
file
writer
gdrive
revision
author
github
actor
github
commit
author
github
issue
creator
github
issue_comment
author
github
issue_comment_created
subject
github
issue_comment_edited
subject
github
issue_opened
subject
github
pull
contributor
github
pull
reviewer
github
pull_request
contributor
github
pull_request_assigned
subject
github
pull_request_closed
subject
github
pull_request_comment
author
github
pull_request_create
creator
github
pull_request_edited
subject
github
pull_request_labeled
subject
github
pull_request_merge
merger
github
pull_request_opened
subject
github
pull_request_reopened
subject
github
pull_request_review_comment
author
github
pull_request_review_comment_created
subject
github
pull_request_review_comment_deleted
subject
github
pull_request_review_comment_edited
subject
github
pull_request_review_request_removed
subject
github
pull_request_review_requested
subject
github
pull_request_unassigned
subject
github
pull_request_unlabeled
subject
github
push
sender
gmail
chat
From
gmail
chat
To
gmail
chat_sent
From
gmail
message
BCC
gmail
message
CC
gmail
message
From
gmail
message
To
gmail
message_sent
From
jira
comment
author
jira
comment_created
author
jira
issue
assignee
jira
issue
attachmentAuthor
jira
issue
creator
jira
issue_created
actor
jira
issue_deleted
actor
jira
issue_resolved
actor
jira
issue_updated
actor
slack
channel
channel_creator
slack
channel
channel_member
slack
message
author
slack
message
mentioned
slack
message
reactor
NONE,GZIP
.json[.gz]
NONE,SNAPPY,DEFLATE
.avro
NONE,SNAPPY,GZIP,ZSTD
.parquet[.gz]
week
DATE
The ISOWEEK this work item happened
id
STRING
The id of the work item
type
STRING
Type of work item: file, meeting, slack channel...
relatedItems
RECORD
Other work items related to this one, if any
├─ itemId
RECORD
Structure that holds the related item identifier
├─── orgId
STRING
Organization this item belongs to
├─── integrationId
STRING
DEPRECATED
├─── sourceKindId
STRING
Source
├─── itemId
STRING
Id
├─ type
STRING
Type of relation (parent, in-reply-to emails...)
metrics
RECORD
Metrics for work item. Can be collected from source or derived. Value can either be numeric or a date
├─ name
STRING
Metric name
├─ value
FLOAT
Numeric value (examples: meeting duration, file size)
├─ dateValue
TIMESTAMP
Timestamp (example: meeting start)
url
STRING
The url associated with the work item if any
contentType
STRING
Content type. Usually present in items related to files (ex: application/vnd.google-apps.spreadsheet)
creationTime
TIMESTAMP
When the item was created
lastActiveTime
TIMESTAMP
When the item was last actioned (created and active are same in events)
firstSyncTime
TIMESTAMP
DEPRECATED.
lastSyncTime
TIMESTAMP
DEPRECATED.
lastUpdateTime
TIMESTAMP
When the item was seen by Worklytics
integrationId
STRING
DEPRECATED
sourceKindId
STRING
Source of item
orgId
STRING
Organization this item belongs to
sourceConnectionId
INTEGER
Worklytics identifier for customer connector
detailVisibilitySetting
STRING
DEPRECATED.
event
BOOLEAN
True if the work item is an event
parentId
RECORD
Parent id of the work item if any
├─ orgId
STRING
Organization this item belongs to
├─ integrationId
STRING
DEPRECATED
├─ sourceKindId
STRING
Source
├─ itemId
STRING
Id
title
STRING
Title of the item if available (email subject, file name, pull request name...)
relations
RECORD
People related to this item
├─ type
STRING
Type of relation (attendee, creator, organizer, editor...)
├─ employeeId
STRING
Employee ID, if action taken by employee in Worklytics records, or,
├─ externalId
STRING
Anonymized external identifier of the person that did the action
├─ properties
RECORD
Properties associated with the action (example: RSVP status on meeting, lenght of comment,...)
├─── name
STRING
Name
├─── value
STRING
Value
├─ directTimeSpent
INTEGER
Time spent working on an event (in milliseconds)
├─ exclusiveTimeSpent
INTEGER
Time spent working exclusively on this event given their concurrent work (in milliseconds)
├─ exclusiveMeetingTimeSpent
INTEGER
Meetings only. Time spent working exclusively on the meeting considering other concurrent meetings (in milliseconds)
properties
RECORD
Properties of the item, vary across sources
├─ name
STRING
Name
├─ value
STRING
Value
gapps_groups
manager
gapps_groups
member
gapps_groups
owner
gcal
attendance
attendee
gcal
attendance
creator
gcal
attendance
organizer
gcal
attendance
resource
gcal
event
attendee
gcal
event
creator
gcal
event
organizer
gdrive
file
owner
gdrive
file
reader
gdrive
file
writer
gdrive
revision
author
github
actor
github
commit
author
github
issue
creator
github
issue_comment
author
github
issue_comment_created
subject
github
issue_comment_edited
subject
github
issue_opened
subject
github
pull
contributor
github
pull
reviewer
github
pull_request
contributor
github
pull_request_assigned
subject
github
pull_request_closed
subject
github
pull_request_comment
author
github
pull_request_create
creator
github
pull_request_edited
subject
github
pull_request_labeled
subject
github
pull_request_merge
merger
github
pull_request_opened
subject
github
pull_request_reopened
subject
github
pull_request_review_comment
author
github
pull_request_review_comment_created
subject
github
pull_request_review_comment_deleted
subject
github
pull_request_review_comment_edited
subject
github
pull_request_review_request_removed
subject
github
pull_request_review_requested
subject
github
pull_request_unassigned
subject
github
pull_request_unlabeled
subject
github
push
sender
gmail
chat
From
gmail
chat
To
gmail
chat_sent
From
gmail
message
BCC
gmail
message
CC
gmail
message
From
gmail
message
To
gmail
message_sent
From
jira
comment
author
jira
comment_created
author
jira
issue
assignee
jira
issue
attachmentAuthor
jira
issue
creator
jira
issue_created
actor
jira
issue_deleted
actor
jira
issue_resolved
actor
jira
issue_updated
actor
slack
channel
channel_creator
slack
channel
channel_member
slack
message
author
slack
message
mentioned
slack
message
reactor
GROUP_TYPE_individual_collaboration_interteam_hours
Total time a person has spent collaborating with people belonging to a different group in the specified GROUP_TYPE. A GROUP_TYPE is any of: cost center, business unit, department, level, region, etc. or company-specific custom groups. For example, an employee in the Marketing department that spends 1 hour in a meeting with Engineering employees in a given week would have 1 hour of department_individual_collaboration_interteam_hours.
GROUP_TYPE_individual_collaboration_interteam_percent
Time a person has spent collaborating with people belonging to a different group in the specified GROUP_TYPE as percent of total collaboration time (`GROUP_TYPE_individual_collaboration_total_hours`)
GROUP_TYPE_individual_collaboration_interteam_people_count
Count of a person's collaborators belonging to a different group in the specified GROUP_TYPE
GROUP_TYPE_individual_collaboration_intrateam_hours
Total time a person has spent collaborating with people belonging to their same group in the specified GROUP_TYPE. A meeting with 1+ person in a different group would not be counted.
GROUP_TYPE_individual_collaboration_intrateam_percent
Time a person has spent collaborating with people belonging to their same group in the specified GROUP_TYPE as percent of total collaboration time (`GROUP_TYPE_individual_collaboration_total_hours`)
GROUP_TYPE_individual_collaboration_intrateam_people_count
Count of a person's collaborators belonging to their same group in the specified GROUP_TYPE
GROUP_TYPE_individual_collaboration_not_classified_hours
Total time a person has spent collaborating with people for whom Worklytics doesn't have a GROUP_TYPE affiliation. Typically due to delays in HRIS updates after a new hire is made.
GROUP_TYPE_individual_collaboration_not_classified_percent
Time a person has spent collaborating with people for whom Worklytics doesn't have a GROUP_TYPE affiliation, as percent of total collaboration time (`GROUP_TYPE_individual_collaboration_total_hours`). Typically due to delays in HRIS updates after a new hire is made.
GROUP_TYPE_individual_collaboration_not_classified_people_count
Count of a person's collaborators for whom Worklytics doesn't have a GROUP_TYPE affiliation. Typically due to delays in HRIS updates after a new hire is made.
GROUP_TYPE_individual_collaboration_total_hours
Total time a person has collaborated with all people in a given week
GROUP_TYPE_individual_collaboration_external_hours
DEPRECATED. Total time a person has collaborated with people outside the organization on a given week.
GROUP_TYPE_individual_collaboration_external_percent
DEPRECATED. Time collaborating with people outside of the organization as percent of total collaboration time (`GROUP_TYPE_individual_collaboration_total_hours`)
TOOL_NAME:minutes:week
Total time in minutes spent working with a specific tool or platform (based on exclusive time). E.g., ‘zoom:minutes:week’ would be total minutes in Zoom Meetings.
TOOL_NAME:events:hours:spent:meetings:unscheduled
Total time in hours spent in unscheduled meetings
asana:tasks:completed
Number of Asana tasks completed during week
asana:v1:total:actions
Number of Asana actions an a person did during week
asana:v1:tasks:acted-on:count
Number of tasks actions (created and updated) a person did during the week
asana:v1:tasks:completed
Number of Asana tasks completed during week
asana:v1:tasks:reopened
Number of Asana tasks were completed but they were marked as incomplete during the week
asana:v1:tasks:assigned:to:others
Number of tasks this person has assigned to other people during the week
asana:v1:tasks:assigned:self
Number of tasks this person has assigned to them self during the week
asana:v1:tasks:assigned:by:others
Number of tasks assigned by peers to this person during the week
asana:v1:tasks:assigned:total
Number of tasks this person has been assigned during the week (self assigned + assigned by others)
asana:v1:tasks:unassigned
Number tasks that the person has unassigned someone from it during the week
asana:v1:tasks:created
Number tasks created during the week
asana:v1:tasks:marked_duplicate
Number of tasks marked as duplicated during the week
asana:v1:tasks:liked
Number of tasks liked during the week
asana:v1:tasks:subtasks:added
Number of subtasks added to a parent task during the week
asana:v1:tasks:subtasks:removed
Number of subtasks removed from parent task during the week
asana:v1:tasks:comments:added
Number of comments added during the week
asana:v1:tasks:comments:liked
Number of comments an individual liked during the week
asana:v1:tasks:followers:added
Number of followers added to tasks during the week
asana:v1:tasks:tagged
Number of tags did the person add to tasks during the week
asana:v1:tasks:completed:on-time
Number of tasks on time during the week
asana:v1:tasks:past-due-date
Number of tasks late in the given week
asana:v1:tasks:completed:past-due-date
Number of tasks completed past due date in the given week
asana:v1:tasks:status:approved
Number of tasks marked as approved during the week
asana:v1:tasks:status:rejected
Number of tasks rejected during the week
asana:v1:tasks:status:changes_requested
Number of tasks with changes requested during the week
asana:v1:tasks:milestone
Number of tasks marked as milestone during the week
asana:v1:project:tasks:added
Number of tasks assigned to a project during the week
asana:v1:project:tasks:removed
Number of tasks removed from a project during the week
asana:v1:project:tasks:section:changed
Number of tasks moved from a section within a project during the week
asana:v1:projects:acted-on:count
Number of projects the person did of the given the week
badge:v1:swipes:monday:count
Number of badge swipes logged on the Monday of the given week
badge:v1:swipes:tuesday:count
Number of badge swipes logged on the Tuesday of the given week
badge:v1:swipes:wednesday:count
Number of badge swipes logged on the Wednesday of the given week
badge:v1:swipes:thursday:count
Number of badge swipes logged on the Thursday of the given week
badge:v1:swipes:friday:count
Number of badge swipes logged on the Friday of the given week
badge:v1:swipes:weekend:count
Number of badge swipes logged on Saturday or Sunday of the given week
badge:v1:weekdays_in_office:count
Number of weekdays (Mon-Fri) the employee swiped in in the given week.
calendar:events:attended
Number of meetings attended. By default, a person is considered to have attended as long as they did not decline the invite.
calendar:v1:events:attended:external
Number of meetings attended where at least one attendee is from outside of the company
calendar:v1:events:attended:internal
Number of meetings attended where all attendees are internal to the company
calendar:events:created:attendees
Average number of people invited on meetings created
calendar:events:created:avg:length
Average length in hours of meetings created. Multiply by 60 to get minutes
calendar:events:created:total:attendees
Total number of people invited to meetings in a given week
calendar:events:created:total:length
Total length (in hours) of meetings created. Multiply by 60 to get minutes
calendar:events:created
Number of meetings created during week
calendar:events:focus
% of time in meetings doing other work, e.g., a value of 95% means that 5% of time in meetings was spent in email, messaging, documents etc.
calendar:events:hours:internal:meetings:invited
Total duration of internal meetings (only people from your organization invited) the entity was invited to. Value in hours. Multiply by 60 to get minutes.
calendar:events:hours:internal:meetings
Hours spent in meetings where all attendees are internal to the company. Multiply by 60 to get minutes
calendar:v1:events:hours:meetings:external
Hours spent in meetings where at least one attendee is from outside of the company. Multiply by 60 to get minutes
calendar:events:hours:meetings
Total hours spent in meetings. Multiply by 60 to get minutes
calendar:manager1on1:count
Number of 1:1 meetings with manager in week
calendar:v1:manager1on1:hours
Hours spent in 1:1 meetings with managers in week (based on exclusive meeting time)
calendar:v1:manager1on1:count_4wk
Number of 1:1 meetings with manager in the last 4 weeks; this metric calculation is the same as that of calendar:manager1on1:count, except the count includes 1:1s from the current week + the prior 3 weeks
calendar:v1:manager1on1:count_2wk
Number of 1:1 meetings with manager in the last 2 weeks; this metric calculation is the same as that of calendar:manager1on1:count, except the count includes 1:1s from the current week + the prior 1 week
calendar:v1:manager-co-attendance:hours
hours spent in meetings during which an individual's manager is also an attendee
calendar:v1:manager-co-attendance:pct
Percent of total meeting hours with an individual's direct manager co-attending
calendar:v1:manager1on1:weeks-since-last-1on1
Number of weeks since an individual's last scheduled 1:1 with their manager
calendar:v1:meetings:attendees:2:count
Number of meetings with 2 people in week
calendar:v1:meetings:attendees:3-or-more:count
Number of meetings with 3 or more people in week
calendar:v1:meetings:attendees:5-or-more:count
Number of meetings with 5 or more people in week
calendar:v1:meetings:attendees:8-or-more:count
Number of meetings with 8 or more people in week
calendar:v1:meetings:attendees:10-or-more:count
Number of meetings with 10 or more people in week
calendar:v1:meetings:attendees:15-or-more:count
Number of meetings with 15 or more people in week
calendar:v1:meetings:attendees:20-or-more:count
Number of meetings with 20 or more people in week
calendar:v1:meetings:attendees:2:hours
Hours spent in meetings with 2 people in week (based on exclusive meeting time)
calendar:v1:meetings:attendees:3-or-more:hours
Hours spent in meetings with 3 or more people in week (based on exclusive meeting time)
calendar:v1:meetings:attendees:5-or-more:hours
Hours spent in meetings with 5 or more people in week (based on exclusive meeting time)
calendar:v1:meetings:attendees:8-or-more:hours
Hours spent in meetings with 8 or more people in week (based on exclusive meeting time)
calendar:v1:meetings:attendees:10-or-more:hours
Hours spent in meetings with 10 or more people in week (based on exclusive meeting time)
calendar:v1:meetings:attendees:15-or-more:hours
Hours spent in meetings with 15 or more people in week (based on exclusive meeting time)
calendar:v1:meetings:attendees:20-or-more:hours
Hours spent in meetings with 20 or more people in week (based on exclusive meeting time)
calendar:v1:recurring:meetings:count
Number of recurring meetings in week
calendar:v1:recurring:meetings:hours
Hours spent in recurrent meetings in week (based on exclusive meeting time)
calendar:uninterrupted:focus:hours
Average number of hours per day in blocks of at least 2 hours without an interruption from meetings for active people (worklytics:active:employees is marked as 1) on workdays (Mon-Fri).
calendar:uninterrupted:focus:v2:hours
Average number of hours per day in blocks of at least 2 hours without an interruption from meetings, mail, chat or videoconferencing for active people (worklytics:active:employees is marked as 1) on workdays (Mon-Fri).
cisco-jabber:message:sent
Number of Cisco Jabber messages sent
chat:v1:incoming:manager:after-hours
Number of slack, gchat, etc. messages received from one's manager outside of one's work hours
chat:v1:incoming:after-hours
Number of slack, gchat, etc. messages received outside of one's work hours
chat:v1:outgoing:after-hours
Number of slack, gchat, etc. messages sent outside of one's work hours
collaboration:highest-total-with-any-direct-manager
In the case of multiple managers, the highest time spent collaborating in seconds. Mostly for ML purposes.
collaboration:manager-to-employee:ratio
Percent of total collaboration time between manager and direct report initiated by manager. [0..1]. 0.5 means collaboration is equally started. 0.8 means manager initiates collaboration 80% of the time
collaborative_work_time_hours
How much of the total time working is considered collaborative
collaborative_work_time_percent
How much of the total time working is considered collaborative as percent of total (collaborative_work_time_hours + individual_work_time_hours)
individual_work_time_hours
How much of the total time working is considered individual work
individual_work_time_percent
How much of the total time working is considered individual work as percent of total (collaborative_work_time_hours + individual_work_time_hours)
collaborator_turnover_26wk_ratio
Ratio of recent collaborators that left in the last 26 weeks
collaborators:count_distinct_12wk
Total number of distinct collaborators in the past 12 weeks
collaborators:count_distinct_4wk
Total number of distinct collaborators in the past 4 weeks
collaborators:count_distinct
Total number of collaborators this week. This value may be large as it could include anyone attending the same large meeting or on the same large email thread. For a more realistic value of collaborators see the ‘collaborators:strong’ value
collaborators:strong_count_distinct
Total number of collaborators considered strong this week.
collaborators:strong_count_distinct_4wk
Total number of collaborators considered strong in the last 4 weeks.
collaborators:strong_count_distinct_mean_4wk
4 week rolling average number of collaborators considered strong (at least 2 hours of weekly collaboration). This metric is useful for determining the number of frequent collaborators.
confluence:pages:created
The number of pages that a person created during the week.
confluence:pages:updated
The number of pages that a person updated during the week.
document_download_hours_spent
Dropbox Business hours spent downloading documents
document_download_total_actions
Dropbox Business total download actions on week
document_download_unique_items
Dropbox Business number of distinct documents downloaded on week
document_editing_hours_spent
Dropbox Business hours spent editing documents
document_editing_total_actions
Dropbox Business total edit actions on week
document_editing_unique_items
Dropbox Business number of distinct documents edited
document_sharing_hours_spent
Dropbox Business hours spent sharing documents
document_sharing_total_actions
Dropbox Business total sharing actions on week
document_sharing_unique_items
Dropbox Business number of distinct documents shared on week
document_discussion_hours_spent
Estimate of total time spent commenting on documents
document_discussion_total_actions
Count of total comments made on documents
document_discussion_unique_items
Count of total unique documents commented on
document_management_hours_spent
Estimate of total time spent managing documents and files. Includes a broad range of actions on taken such as creation, deletion, moving, rename, publishing etc
document_management_total_actions
Count of total actions taken to manage documents and files. Includes a broad range of actions taken such as creation, deletion, moving, rename, publishing etc
document_management_unique_items
Count of unique documents and files on which management actions have been taken. Includes a broad range of actions such as creation, deletion, moving, sharing, publishing etc
document_others_hours_spent
Estimate of total time spent on range of other admin type actions. Including permission changes, group/team creation and management, password management etc
document_others_total_actions
Total number of other administrative actions taken. Including permission changes, group/team creation and management, password management etc
document_others_unique_items
Total number of documents, folder, users and groups upon which administrative actions were taken
email:avg:checks:per:day
Estimated number of times a person checks and responds to their email per day
email:incoming:internal
Count of emails received from other employees
email:incoming:out-of-office
Count of emails received outside of working hours. Working hours value is configurable at an org level. Default is 9:00-17:00.
email:outgoing:external
Count of emails sent to people outside the org
email:outgoing:internal
Count of emails sent to other employees
email:outgoing:total
Total number of emails sent regardless of destination (aggregate of all email sources - GMail, Outlook)
gcal:events:attended:active
# Google Calendar events attended by a person who was considered ‘active’ in the given week. This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gcal:events:attended
# Google Calendar events the person was invited to. This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gcal:events:avg:attendees
Average number of people invited on meetings created in Google Calendar. This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gcal:events:avg:hours:created:meetings
Total length (in hours) of meetings created in Google Calendar. This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gcal:events:created
Number of meetings created during week in Google Calendar. This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gcal:events:hours:spent:meetings:active
Hours spent in meetings by a person who had activity that week (usually same as below value). This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gcal:events:hours:spent:meetings
Total hours spent in meetings in Google Calendar. This metric is generated based the total raw number of calendar events observed. It does not deduplicate concurrent meetings nor remove all day meetings and individual reminders. Usage intended for ML models. For more precise calendar meetings metrics use the ones prefixed with `calendar:`
gdrive:file:created
Number of of files created
gdrive:file:edits
Number of files edited
github:issues:created
Number of issues created
github:pr:avg:num:comments
Average number of comments per pull requests
github:pr:opened
Total pull requests opened
github:pr:closed
Total pull requests closed
github:pr:contributed:merged
Count of pull requests contributed by employee that were merged
github:pr:created
Count of pull requests created
github:pr:loc:added
Number of lines of code added that week
github:pr:loc:deleted
Number of lines of code deleted that week
github:issues:opened
Number of issues opened that week
github:pr:merged
Number of pull requests merged
github:pr:total:commits
Total commits done in pull requests on that week
github:v2:issues:opened
Number of issues opened that week
github:v2:issues:closed
Number of issues closed that week
github:v2:issues:reopened
Number of issues reopened that week
github:v2:issues:commented
Number of comments written on an issue (discussions, etc) that week
github:v2:issues:contributed
Number of issues contributed that week
github:v2:issues:assigned:to:others
Number of issues assigned to other people that week
github:v2:issues:assigned:self
Number of issues self assigned that week
github:v2:issues:assigned:by:others
Number of issues assigned from other people that week
github:v2:issues:assigned:total
Number of total issues assigned that week
github:v2:pulls:opened
Number of pulls opened that week
github:v2:pulls:opened:change_requested
Number of pulls opened that week that someone has requested changes
github:v2:pulls:closed
Number of pulls closed that week
github:v2:pulls:merged
Number of pulls merged that week
github:v2:pulls:reopened
Number of pulls reopened that week
github:v2:pulls:reviewed
Number of pull reviews done that week
github:v2:pulls:reviewed:commented
Number of pull reviews done as commented that week
github:v2:pulls:reviewed:changes_requested
Number of pull reviews with requested changes done that week
github:v2:pulls:reviewed:approved
Number of pull reviews with approval done that week
github:v2:pulls:reviewed:dismissed
Number of dismissed pull reviews done that week
github:v2:pulls:review:comment
Number of comments done as part of a pull reviews on that week
github:v2:pulls:comments
Number of comments (discussions, etc) done in a pull that week
github:v2:pulls:totals:commits
Number of commits done for pulls that week
github:v2:pulls:contributed
Number of pulls contributed that week
github:v2:pulls:contributed:merged
Number of pulls contributed that have been merged that week
github:v2:pulls:assigned:to:others
Number of pulls assigned to other people that week
github:v2:pulls:assigned:self
Number of pulls self assigned that week
github:v2:pulls:assigned:by:others
Number of pulls assigned from other people that week
github:v2:pulls:assigned:total
Number of total pulls assigned that week
github:v2:totals:commits
Number of commits done that week
github:v2:commits:loc:added
Number lines added from commits that week
github:v2:commits:loc:deleted
Number lines deleted from commits that week
github:v2:repository:contributed
Number repositories contributed (commits, issues, pulls) that week
gitlab:issues:opened
Number of issues opened on that week
gitlab:mr:accepted
Number of merge requests accepted on that week
gitlab:total:pushes
Number of code pushes on that week
gmail:chats:sent
Number of Google Chat messages sent
gmail:email:sent:avg:recipients
Average number of recipients in emails sent
gmail:emails:sent
Number of emails sent using GMail
google-chat:message:sent
Number of Google Chat messages sent
google-meet:v1:unscheduled:meetings
Count of unscheduled Google Meet meetings held with 7 or less hours of duration
google-meet:v1:hours:spent:meetings:unscheduled
Total time in hours spent in unscheduled Google Meet meetings held with 7 or less hours of duration
graph:betweenness:centrality:score
Value for Betweenness Centrality algorithm (measure of how much information flows through an individual)
graph:eigenvector:centrality:score
Value for Eigenvector Centrality algorithm (common metric used to indicate how influential a given individual is in the flow of information within a network)
graph:in-degree:count
Average in-degree connections (collaboration to person)
graph:out-degree:count
Average out-degree connections (collaboration from person)
jabber:events:avg:recipients:sent:messages
Average sent message recipients count
jabber:events:avg:recipients:sent:group:messages
Average sent group message recipients count
jira:assigned:tickets
Number of assigned tickets to that person
jira:issues:completed
Number of issues completed that week
jira:issues:created
Number of issues created that week
jira:issues:updated
Number of issues updated that week
jira:comments:created
Number of comments created that week
jira:comments:updated
Number of comments updated that week
jira:comments:deleted
(Not available in Jira Proxy connector) Number of comments deleted that week
jira:worklogs:created
Number of worklogs created that week
jira:worklogs:updated
Number of worklogs updated that week
jira:worklogs:deleted
(Not available in Jira Proxy connector) Number of worklogs deleted that week
jira:boards:created
(Not available in Jira Proxy connector) Number of boards created that week
jira:boards:updated
(Not available in Jira Proxy connector) Number of boards updated that week
jira:boards:deleted
(Not available in Jira Proxy connector) Number of boards deleted that week
manager:changed
Boolean value. 1 means a manager change happened that week
msft-teams:v1:unscheduled:meetings
Count of unscheduled Microsoft Teams meetings held with 7 or less hours of duration
msft-teams:v1:hours:spent:meetings:unscheduled
Total time in hours spent in unscheduled Microsoft Teams meetings held with 7 or less hours of duration
org:hierarchy:depth
Depth in org, number of steps in hierarchy from CEO
org:hierarchy:direct-ic-reports
Number of direct reports that are individual contributors (not managers)
org:hierarchy:direct-manager-reports
Number of direct reports that are managers themselves
org:hierarchy:direct-reports
Total direct reports (contributors + managers)
org:hierarchy:height
Height in org, number of steps from the bottom of the hierarchy
org:hierarchy:managers-direct-reports
Number of direct reports this person's manager has
org:hierarchy:total-reports
Total count of direct reports this person has (direct + indirect)
outlook-cal:events:attended:active
Number Outlook Calendar events attended with person considered active
outlook-cal:events:attended
Number Outlook Calendar events attended
outlook-cal:events:hours:spent:meetings:active
Hours spent in meetings by a person who had activity that week (usually same as below value)
outlook-cal:events:hours:spent:meetings
Same as 'calendar:events:hours:meetings' but specific to Outlook Calendar source
outlook-mail:emails:sent
Number of emails sent using Outlook Mail
salesforce:email:outgoing:total
Number of emails sent that week
salesforce:task:created
Number of tasks created that week
salesforce:task:edited
Number of tasks edited that week
salesforce:task:completed:total
Number of tasks completed that week
salesforce:task:completed:high_priority
Number of tasks marked with as high priority completed that week
salesforce:phone_call:total
Number of phone calls made that week
salesforce:phone_call:inbound
Number of phone calls received that week
salesforce:phone_call:internal
Number of internal phone calls made that week
salesforce:phone_call:outbound
Number of external phone calls made that week
salesforce:events:created
Number of events created that week
salesforce:events:attended
Number of hosted events attended that week
salesforce:phone_call:minutes:week
Number of minutes spent on calls during that week
salesforce:events:hours:meetings
Number of hours spent in meetings during that week
salesforce:accounts:created
Number of accounts created that week
salesforce:accounts:edited
Number of accounts edited that week
slack:message:sent
Number of Slack messages sent
slack:message:sent:channel:count
Number of Slack messages sent by channel type
slack:message:sent:public:count
Number of Slack messages sent in public channels
slack:message:sent:private:count
Number of Slack messages sent in private channels
slack:v1:message:sent:count
Number of Slack messages sent
slack:v1:dm:channels:sent:count
Number of Slack direct messages sent
slack:v1:group:channels:sent:count
Number of Slack group messages sent. This covers groups and mpim conversations
slack:v1:public:channels:sent:count
Number of Slack channel messages sent
slack:v1:message:dm:sent:people:count
Number of unique individuals direct messaged for Slack
slack:v1:message:group:sent:active:people:reached
Number of unique individuals reached in conversations in private groups. Count of all active senders in private groups this person has sent during the week.
slack:v1:total:channels:sent:count
Number of unique Slack channels messages sent in
slack:v1:message:mentions:received
Number of mentions by others in a Slack message
slack:v1:message:dm:response:time:seconds
Average time taken to respond to direct messages within a conversation window. A conversation window is all messages with less than 12h hours response before the previous one.
slack:v1:message:dm:response:percent
Percentage of new conversations started with an individual where they do respond within the 12 hour window
slack:v1:reaction:received
Number of reactions received on messages
slack:v1:reaction:sent
Number of reactions on other people's messages
slack:v1:huddles:attended
Count of Slack Huddles attended. For Psoxy, requires minimum of v0.4.58
slack:v1:huddles:hours:spent:meetings
Number of hours spent on Slack Huddles. For Psoxy, requires minimum of v0.4.58
tenure:months
Tenure in months
weekly:peer_turnover
Number of collaborators that left the company on that week
work_schedule:median_workdayTimeEnd_hour
Median weekly start time for a person, 0-24 range. F.e. 8.50 means 08:30 AM
work_schedule:median_workdayTimeStart_hour
Median weekly end time for a person, 0-24 range. F.e. 17.25 means 17:15 PM
work_schedule:median_workdayTimespan_hours
Median weekly time span for a person, 0-24 range. F.e. 12.50 means 12:30 hours. Time span is the time between the first and last action of the day. It is an estimate of the work day length.
worklytics:active:employees
Boolean. 1 means that person is considered active that week based on the data we have
worklytics:active:weeks_out_of_last_12
Count number of weeks out of last 12 that has some activity
worklytics:active:weeks_out_of_last_4
Count number of weeks out of last 4 that has some activity
worklytics:days:with:activity
Range 1-7. Count of days this week in which the person has some activity
worklytics:hours:in:focus:blocks
Average hours of at least 2h blocks working uninterrupted by meetings on workdays (Mon-Fri)
worklytics:hours:in:focus:blocks:v2
Average hours of at least 2h blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri)
worklytics:hours:in:focus:blocks:v3:prep
Average hours of at least 30m blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:in:focus:blocks:v3:focus
Average hours of at least 1h blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:in:focus:blocks:v3:flow
Average hours of at least 2h blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:fragmented:v3:prep
Average hours of 0-30m blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:fragmented:v3:focus
Average hours of 0-1h blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:fragmented:v3:flow
Average hours of 0-2h blocks working uninterrupted by mail, chat or videoconferencing on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:interrupted:v3:prep
Average hours spent on mail, chat, and videoconferencing, plus hours spent in uninterrupted blocks that are too short to be focus time (less than 30m) on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:interrupted:v3:focus
Average hours spent on mail, chat, and videoconferencing, plus hours spent in uninterrupted blocks that are too short to be focus time (less than 1h) on workdays (Mon-Fri). No lunch time accounted for.
worklytics:hours:interrupted:v3:flow
Average hours spent on mail, chat, and videoconferencing, plus hours spent in uninterrupted blocks that are too short to be focus time (less than 2h) on workdays (Mon-Fri). No lunch time accounted for.
worklytics:total:time:worked:hours
Total hours worked, estimated by adding up workday span for all weekdays + the number of hours of logged activity in digitial tools on the weekend
worklytics:v1:total:time:event:hours
Total hours worked, estimated by adding up the number of hours of logged activity in digitial tools on weekdays + the number of hours of logged activity in digitial tools on the weekend
worklytics:v1:weekdays:avg:intensity:pct
Estimated % of the typical day that includes logged activity in digital tools. The numerator is the number of hours of logged activity in digital tools, and the denominator is workday span (the time difference between first and last action of the day)
worklytics:v1:weekdays:avg:time:event:hours
Average hours of logged activity in digital tools on weekdays
worklytics:v1:weekdays:total:time:event:hours
Total hours of logged activity in digital tools on weekdays
worklytics:weekdays:avg:timespan:hours:outside:workday
Total hours worked during the workdays outside of the established working hours
worklytics:weekdays:avg:timeend:hours
Average weekly end time for a person, 0-24 range. F.e. 17.25 means 17:15 PM. End time is the time of the last action of the day. It is an estimate of when the day ends.
worklytics:weekdays:avg:timespan:hours
Average weekly time span for a person, 0-24 range. F.e. 12.50 means 12:30 hours. Time span is the time between the first and last action of the day. It is an estimate of the work day length.
worklytics:weekdays:avg:timespan:more9h:hours
Number of days (Mon-Fri) where the individual worked more than 9h
worklytics:weekdays:avg:timestart:hours
Average weekly start time for a person, 0-24 range. F.e. 8.50 means 08:30 AM. Start time is the time of the first action of the day. It is an estimate of when the day begins.
worklytics:weekdays:total:time:worked:hours
Total hours worked during regular work week (mon-fri)
worklytics:weekend:worked
Boolean, 1 means that employee worked on the weekend
worklytics:weekends:total:time:worked:hours
Total hours worked on the weekend
zendesk:ticket:assigned
Count of tickets assigned in the given week
zendesk:ticket:commented
Count of tickets submitted in the given week
zendesk:ticket:submitted
Count of tickets submitted in the given week
zoom:created:meetings
Count of Zoom meetings created
zoom:events:hours:spent:meetings
Sum of total hours spent in Zoom meetings, including both scheduled and unscheduled meetings (deprecated, use v2)
zoom:v2:events:hours:spent:meetings
Sum of total hours spent in Zoom meetings, including both scheduled and unscheduled meetings with 7 or less hours of duration
zoom:events:avg:hours:created:meetings
Average length of Zoom meetings created
zoom:events:avg:participants:created:meetings
Average number of participants in Zoom meetings created
zoom:late:meetings
Count of meetings that started after the scheduled start time plus a 5 minute grace period. A meeting is considered to have started when at least 2 participants have joined.
zoom:brief:meetings
Number of scheduled meetings that finish earlier than the scheduled duration
zoom:scheduled:meetings
Count of scheduled Zoom meetings attended
zoom:ontime:meetings
Count of meetings that started before the scheduled start time plus a 5 minute grace period. A meeting is considered to have started when at least 2 participants have joined.
zoom:unscheduled:meetings
Count of unscheduled Zoom meetings attended
zoom:v1:unscheduled:meetings
Count of unscheduled Zoom meetings attended with 7 or less hours of duration
zoom:v1:hours:spent:meetings:unscheduled
Sum of total hours spent in unscheduled Zoom meetings with 7 or less hours of duration
zoom:overtime:meetings
Count of Zoom meetings that ended after the scheduled end time
zoom:late:meetings:avg:minutes
Average number of minutes that Zoom meetings start after the scheduled start time
zoom:brief:meetings:avg:minutes
Average number of minutes that Zoom meetings end before the scheduled end time
zoom:overtime:meetings:avg:minutes
Average number of minutes that Zoom meetings end after the scheduled end time
zoom:external:meetings
Weekly count of external meetings. A meeting is considered external when at least one participant is not from the organization
zoom:internal:meetings
Weekly count of internal meetings. A meeting is considered internal when all participants belong to the organization
zoom:org:external:meetings
Weekly count of total external meetings. A meeting is considered external when at least one participant is not from the organization
zoom:org:internal:meetings
Weekly count of total internal meetings. A meeting is considered internal when all participants belong to the organization
zoom:minutes:week
Total time in minutes spent working with Zoom.
zoom:v2:created:meetings
Count of Zoom meetings created
zoom:v2:events:avg:hours:created:meetings
Average length of Zoom meetings created
zoom:v2:events:avg:participants:created:meetings
Average number of participants in Zoom meetings created
zoom:v2:late:meetings
Count of meetings that started after the scheduled start time plus a 5 minute grace period. A meeting is considered to have started when at least 2 participants have joined.
zoom:v2:scheduled:meetings
Count of Zoom meetings scheduled
zoom:v2:ontime:meetings
Count of meetings that started before the scheduled start time plus a 5 minute grace period. A meeting is considered to have started when at least 2 participants have joined.
zoom:v2:unscheduled:meetings
Count of unscheduled Zoom meetings held with 7 or less hours of duration
zoom:v2:hours:spent:meetings:unscheduled
Total time in hours spent in unscheduled Zoom meetings held with 7 or less hours of duration
zoom:v2:hours:spent:meetings:scheduled
Total time in hours spent in scheduled Zoom meetings
zoom:v2:overtime:meetings
Count of Zoom meetings that ended after the scheduled end time
zoom:v2:late:meetings:avg:minutes
Average number of minutes that Zoom meetings start after the scheduled start time
zoom:v2:overtime:meetings:avg:minutes
Average number of minutes that Zoom meetings end after the scheduled end time
zoom:v2:external:meetings
Weekly count of external meetings. A meeting is considered external when at least one participant is not from the organization
zoom:v2:internal:meetings
Weekly count of internal meetings. A meeting is considered internal when all participants belong to the organization
zoom:v2:org:external:meetings
Weekly count of total external meetings. A meeting is considered external when at least one participant is not from the organization
zoom:v2:org:internal:meetings
Weekly count of total internal meetings. A meeting is considered internal when all participants belong to the organization
zoom:v3:created:meetings
Count of Zoom meetings created (replaces v1/v2, rolling out end of March 2024)
zoom:v3:events:avg:hours:created:meetings
Average length of Zoom meetings created (replaces v1/v2, rolling out end of March 2024)
zoom:v3:events:avg:participants:created:meetings
Average number of participants in Zoom meetings created (replaces v1/v2, rolling out end of March 2024)
zoom:v3:events:attended
Count of all Zoom meetings attended
zoom:v3:events:hours:spent:meetings
Sum of total hours spent in Zoom meetings, including both scheduled and unscheduled meetings with 7 or less hours of duration (replaces v1/v2, rolling out end of March 2024)
zoom:v3:unscheduled:meetings
Count of unscheduled Zoom meetings attended (replaces v1/v2, rolling out end of March 2024)
zoom:v3:events:hours:spent:meetings:unscheduled
Sum of total hours spent in unscheduled Zoom meetings with 7 or less hours of duration (replaces v1/v2, rolling out end of March 2024)
zoom:v3:scheduled:meetings
Count of scheduled Zoom meetings attended (replaces v1/v2, rolling out end of March 2024)
zoom:v3:events:hours:spent:meetings:scheduled
Sum of total hours spent in scheduled Zoom meetings (replaces v1/v2, rolling out end of March 2024)
zoom:v3:late:meetings
Count of meetings that started after the scheduled start time plus a 5 minute grace period. A meeting is considered to have started when at least 2 participants have joined. (replaces v1/v2, rolling out end of March 2024)
zoom:v3:ontime:meetings
Count of meetings that started before the scheduled start time plus a 5 minute grace period. A meeting is considered to have started when at least 2 participants have joined. (replaces v1/v2, rolling out end of March 2024)
zoom:v3:overtime:meetings
Count of Zoom meetings that ended after the scheduled end time (replaces v1/v2, rolling out end of March 2024)
zoom:v3:earlyend:meetings
Number of scheduled meetings that finish earlier than the scheduled duration (replaces v1/v2, rolling out end of March 2024)
zoom:v3:late:meetings:avg:minutes
Average number of minutes that Zoom meetings start after the scheduled start time (replaces v1/v2, rolling out end of March 2024)
zoom:v3:overtime:meetings:avg:minutes
Average number of minutes that Zoom meetings end after the scheduled end time (replaces v1/v2, rolling out end of March 2024)
zoom:v3:earlyend:meetings:avg:minutes
Average number of minutes that Zoom meetings end before the scheduled end time (replaces v1/v2, rolling out end of March 2024)
zoom:v3:internal:meetings
Weekly count of internal meetings. A meeting is considered internal when all participants belong to the organization (replaces v1/v2, rolling out end of March 2024)
zoom:v3:external:meetings
Weekly count of external meetings. A meeting is considered external when at least one participant is not from the organization (replaces v1/v2, rolling out end of March 2024)
msft:teams:v1:message:sent:count
Number of Teams messages sent
msft:teams:v1:public:channels:sent:count
Number of Teams messages sent to a public channel
msft:teams:v1:private:channels:sent:count
Number of Teams messages sent to a private channel
msft:teams:v1:external:channels:sent:count
Number of Teams messages sent to an external channel
msft:teams:v1:dm:chats:sent:count
Number of Teams chat direct messages sent to someone
msft:teams:v1:group:chats:sent:count
Number of Teams chat messages sent to a private group
msft:teams:v1:message:dm:sent:people:count
Number of unique individuals direct messaged for Teams
msft:teams:v1:message:group:sent:active:people:reached
Number of unique individuals reached in conversations in private groups or channels. Count of all active senders in private groups this person has sent during the week.
msft:teams:v1:total:channels:sent:count
Number of unique Teams channels messages sent in
msft:teams:v1:message:mentions:received
Number of mentiones received on messages
msft:teams:v1:message:dm:response:time:seconds
Average time taken to respond to direct messages within a conversation window. A conversation window is all messages with less than 12h hours response before the previous one.
msft:teams:v1:message:dm:response:percent
Percentage of new conversations started with an individual where they do respond within the 12 hour window
msft:teams:v1:reaction:received
Number of reactions received on messages
msft:teams:v1:reaction:sent
Number of reactions on other people's messages
msft:teams:v1:calls:created:count
Number of unique calls created on Teams
msft:teams:v1:calls:scheduled:created:count
Number of scheduled calls created on Teams
msft:teams:v1:calls:unscheduled:created:count
Number of unscheduled calls created on Teams
msft:teams:v1:calls:attended:scheduled:count
Number of people attended on scheduled meetings created
msft:teams:v1:calls:attended:unscheduled:count
Number of people attended on unscheduled meetings created
msft:teams:v1:calls:sum:hours:spent:meetings
Number of hours spent in meetings during that week
msft:teams:v1:calls:scheduled:sum:hours:spent:meetings
Number of hours spent in scheduld meetings during that week
msft:teams:v1:calls:unscheduled:sum:hours:spent:meetings
Number of hours spent in unscheduld meetings during that week
msft:teams:v1:calls:scheduled:sum:participants
Number of unique participants in meetings scheduled meetings created
msft:teams:v1:calls:unscheduled:sum:participants
Number of unique participants in meetings unscheduled meetings created
employeeId | STRING | employee id as provided by customer |
questionId | STRING | question id |
questionLabel | STRING | question text |
surveyDate | DATE | response date |
surveyName | STRING | survey name for identification |
value | INTEGER | question response value |
employeeId | STRING | employee id as provided by customer |
week | DATE | isoweek, starts on Monday |
key | STRING | metric key |
value | FLOAT | metric value |
employeeId | STRING | employee id as provided by customer |
week | DATE | isoweek, starts on Monday |
BUSINESS_UNIT | STRING | BUSINESS_UNIT group this person belonged to during the week, NULL if none |
BUSINESS_SEGMENT | STRING | BUSINESS_SEGMENT group this person belonged to during the week, NULL if none |
COST_CENTRE | STRING | COST_CENTRE group this person belonged to during the week, NULL if none |
DEPARTMENT | STRING | DEPARTMENT group this person belonged to during the week, NULL if none |
LEVEL | STRING | LEVEL group this person belonged to during the week, NULL if none |
LINE_OF_BUSINESS | STRING | LINE_OF_BUSINESS group this person belonged to during the week, NULL if none |
OFFICE | STRING | OFFICE group this person belonged to during the week, NULL if none |
ROLE | STRING | ROLE group this person belonged to during the week, NULL if none |
TEAM | STRING | TEAM group this person belonged to during the week, NULL if none |
TERRITORY | STRING | TERRITORY group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_1 | STRING | CUSTOM_GROUP_1 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_2 | STRING | CUSTOM_GROUP_2 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_3 | STRING | CUSTOM_GROUP_3 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_4 | STRING | CUSTOM_GROUP_4 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_5 | STRING | CUSTOM_GROUP_5 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_6 | STRING | CUSTOM_GROUP_6 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_7 | STRING | CUSTOM_GROUP_7 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_8 | STRING | CUSTOM_GROUP_8 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_9 | STRING | CUSTOM_GROUP_9 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_10 | STRING | CUSTOM_GROUP_10 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_11 | STRING | CUSTOM_GROUP_11 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_12 | STRING | CUSTOM_GROUP_12 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_13 | STRING | CUSTOM_GROUP_13 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_14 | STRING | CUSTOM_GROUP_14 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_15 | STRING | CUSTOM_GROUP_15 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_16 | STRING | CUSTOM_GROUP_16 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_17 | STRING | CUSTOM_GROUP_17 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_18 | STRING | CUSTOM_GROUP_18 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_19 | STRING | CUSTOM_GROUP_19 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_20 | STRING | CUSTOM_GROUP_20 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_21 | STRING | CUSTOM_GROUP_21 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_22 | STRING | CUSTOM_GROUP_22 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_23 | STRING | CUSTOM_GROUP_23 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_24 | STRING | CUSTOM_GROUP_24 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_25 | STRING | CUSTOM_GROUP_25 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_26 | STRING | CUSTOM_GROUP_26 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_27 | STRING | CUSTOM_GROUP_27 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_28 | STRING | CUSTOM_GROUP_28 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_29 | STRING | CUSTOM_GROUP_29 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_30 | STRING | CUSTOM_GROUP_30 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_31 | STRING | CUSTOM_GROUP_31 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_32 | STRING | CUSTOM_GROUP_32 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_33 | STRING | CUSTOM_GROUP_33 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_34 | STRING | CUSTOM_GROUP_34 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_35 | STRING | CUSTOM_GROUP_35 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_36 | STRING | CUSTOM_GROUP_36 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_37 | STRING | CUSTOM_GROUP_37 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_38 | STRING | CUSTOM_GROUP_38 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_39 | STRING | CUSTOM_GROUP_39 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_40 | STRING | CUSTOM_GROUP_40 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_41 | STRING | CUSTOM_GROUP_41 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_42 | STRING | CUSTOM_GROUP_42 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_43 | STRING | CUSTOM_GROUP_43 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_44 | STRING | CUSTOM_GROUP_44 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_45 | STRING | CUSTOM_GROUP_45 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_46 | STRING | CUSTOM_GROUP_46 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_47 | STRING | CUSTOM_GROUP_47 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_48 | STRING | CUSTOM_GROUP_48 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_49 | STRING | CUSTOM_GROUP_49 group this person belonged to during the week, NULL if none |
CUSTOM_GROUP_50 | STRING | CUSTOM_GROUP_50 group this person belonged to during the week, NULL if none |
<any HRIS custom group defined 1> | STRING | Only if present in Employee Snapshot HRIS file, the first custom group defined there. |
<any HRIS custom group defined ...> | STRING | Only if present in Employee Snapshot HRIS file, rest of custom groups defined there (one column per group) |
STRING | Only if present in Employee Snapshot HRIS file, the last custom group defined there. |
ETHNICITY | STRING | ETHNICITY group this person belonged to during the week, NULL if none |
GENDER | STRING | GENDER group this person belonged to during the week, NULL if none |
GENERATION | STRING | GENERATION group this person belonged to during the week, NULL if none |
MILITARY_STATUS | STRING | MILITARY_STATUS group this person belonged to during the week, NULL if none |
active | BOOLEAN | if employee was considered active on the week |
week | DATE | isoweek, starts on Monday |
idType | STRING | type of group (ORG or GROUP) |
groupType | STRING | group sub type |
groupName | STRING | group name |
aggType | STRING | AVG/ SUM/ COUNT |
key | STRING | metric key |
value | FLOAT | metric value |
sumValue | FLOAT | sum of all (precalculated value, usefulness depends on the aggregate) |
avgByActiveEmployees | FLOAT | avg per active employee (precalculated, usefulness depends on the aggregate) |
activeEmployees | INTEGER | active members on the week |
totalMembers | INTEGER | total members on the week |
worklyticsId | STRING | worklytics unique for the group id |