Employee Events

Employee Events Data

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

Note: CSV is not supported for this file because is not able to represent nested objects.

Glossary

  • 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

File contents

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.

Events export schema

Sample rows

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:

{
"employeeId": "E00000123",
"sourceKindId": "gcal",
"id": "XXXXXXXXXXXXXXXXX@google.com:20210123T190000:attendance",
"eventType": "attendance",
"relationType": "attendee",
"eventTime": "2021-01-23T12:00:00",
"eventTimeUTC": "2021-01-23 20:00:00 UTC",
"timeZone": "US/Pacific",
"relationProperties": [
  {
    "name": "participationStatus",
    "value": "NEEDS_ACTION"
  },
  {
    "name": "responseStatus",
    "value": "needsAction"
  }
],
"eventProperties": [
  {
    "name": "onlineMeetingUrl",
    "value": "https://zoom.us/whatever"
  },
  {
    "name": "meetingId",
    "value": "123456789"
  },
  {
    "name": "status",
    "value": "confirmed"
  },
  {
    "name": "meetingType",
    "value": "ONE_OFF"
  },
  {
    "name": "startTz",
    "value": "America/Los_Angeles"
  }
],
"metrics": [
  {
    "name": "start",
    "value": null,
    "dateValue": "2021-01-23 19:00:00 UTC"
  },
  {
    "name": "end",
    "value": null,
    "dateValue": "2021-01-23 20:00:00 UTC"
  },
  {
    "name": "durationMillis",
    "value": "3600000.0",
    "dateValue": null
  },
  {
    "name": "attendeesCount",
    "value": "3.0",
    "dateValue": null
  }
],
"estimatedTimeSec": "3600.0",
"estimatedEventDurationSec": "3600.0",
"parentItemId": "YYYYYYYYYYYYYYYYYY@google.com"
}

List of possible values for items and relations. List may grow over time.

Last updated