UKG Pro Data Coverage and Performance

Understand the data gaps, limitations, and performance expectations of the UKG Pro data connector.

Overview

Visier provides an integration that covers the key metrics and dimensions needed to jump-start a people analytics strategy. We have identified the critical attributes that most organizations will need to retrieve from their UKG system. The UKG API does not expose all of the data required to build a people analytics solution. Because of the UKG limitations, the connector is not a one-size-fits-all strategy. If there are topics and fields that are not covered by the UKG connector, you can load this data via flat file.

Data coverage

This section details the data coverage the connector provides for subjects in Visier’s analytic model. Use the following table to determine if the connector can be used to retrieve the data you want to analyze.

If the connector provides:

• Full coverage: The connector can be used to load this data. You will have a good set of data to fill out Visier’s Blueprint.
• Limited coverage: The connector can be used to load this data. However, there will be gaps. For example, supplementary data may be absent or some source system properties may not be supported by Visier’s analytic model. You will need to load additional data to fill out Visier’s Blueprint.
• No coverage: The connector cannot be used to load this data.

Subject	Data Coverage	Notes
Organization Core (Employee, Starts, Exits, Hierarchies)	Limited	Historical data is only available for the Job History table. You will need to load data via flat file for custom fields.
Compensation Payout (Actual Compensation)	Full	You will need to load data via flat file for custom fields.

Ways to achieve full data coverage

The UKG API does not provide 100% coverage for all the data needed for a people analytics implementation. You will need to load supplementary flat files to achieve full data coverage.

Organization Core

History is only tracked for data contained in the Job History table. The remaining tables only return current snapshots. You will need to supplement historical data for any field that is not contained within the Job History table via flat file.

For more information about the fields returned as part of the Job History table, see Get all employee job history details.

Custom Fields

The UKG API only exposes the custom fields for certain objects in the UKG system, and doesn’t track historical values for these fields. Due to these limitations, we recommended that you load all custom fields via flat file.