Stitch Blocking Keys table¶

The Stitch Blocking Keys table has all blocking keys used during the Stitch process.

Use with Stitch QA¶

Use the Stitch Blocking Keys table to understand why blocking used (or did not use) a foreign key or separation key to block (or unblock) two records.

Add table¶

A passthrough table adds a domain table to your database. Passthrough domain tables often have a field for the Amperity ID, but otherwise are the same as the fields in the source domain table.

To add the Stitch Blocking Keys table

From the Database Editor, click Add Table.
Name the table “Stitch_Blocking_Keys”.
Set the build mode to Passthrough, and then select Stitch Blocking Keys.
Hide the table from the Visual Segment Editor by verifying that Show in VSE? is unselected.
Click Activate to update the customer 360 database with your changes.

Column reference¶

The Stitch Blocking Keys table contains the following columns:

Column name	Data type	Description
BK	String	A blocking key defines a specific combination of characters for a blocking strategy. For example, the first three characters in given-name, the first character in surname, and birthdate represent a blocking key.
Datasource	String	The name of the data source from which this customer profile originated. Tip The combination of PK and Datasource uniquely identifies a row in the Stitch Blocking Keys table, which correlates to a single row in a domain table.
PK	String	The combination of data source and primary key allows Amperity to uniquely identify every row in every data table across the entirety of customer data input to Amperity. Tip The combination of PK and Datasource uniquely identifies a row in the Stitch Blocking Keys table, which correlates to a single row in a domain table.
Strategy	String	A blocking strategy acts like a filter against large datasets. Each blocking strategy applies its filter. All matching records group together into a block. Each record that matches a blocking strategy is a blocking key.