Unified_Changes_Clusters Table

The Unified_Changes_Clusters table contains a history of changes to cluster graphs, relative to the previous Stitch run.

The Unified_Changes_Clusters table is automatically added to the Stitch QA database as a passthrough table when it is generated using the “Stitch QA” database template.


Thirty days of history are stored by defaut for the Unified_Changes_Clusters and Unified_Changes_PKS tables. This number of days is configurable.

Use with Stitch QA

Use the Unified_Changes_Clusters table as part of the Stitch QA process to compare the previous state of clusters to the current state and understand why a primary key was added, deleted, or updated.

Column reference

The Unified_Changes_Clusters table contains the following columns:

Column Name

Data type




The unique identifier that is assigned to clusters of customer records that all represent the same individual. The Amperity ID does not replace primary and foreign keys, but exists alongside them within unified profiles.


The Amperity ID is a universally unique identifier (UUID) that is represented by 36 characters spread across five groups separated by hyphens: 8-4-4-4-12.

For example:




The type of change that occurred within the Stitch job. Possible values include: added, deleted, and updated:

  • The added change type indicates a new cluster was created during this run.

  • The deleted change type indicates a cluster was deleted during this run.

  • The updated change type indicates the cluster existed in the past run, and continues to exist in this run but the set of PKs that comprise it has changed.

Also in: Unified_Changes_PKS



The job ID for database table generation. For example: db-gen-20210202-12345-AbCd67EFgH8.

Also in: Unified_Changes_PKS



The timestamp that is associated with job_id. Each row that shares the same job ID will have the same value for timestamp.

Also in: Unified_Changes_PKS