Identity Hub: TransUnion TruAudience Identity

This topic describes how to use the Identity Hub to enhance your data with TransUnion TruAudience Identity. It matches rows in your table with a TransUnion identity, which can be used to match rows in your collaborator’s table.

Keep the following in mind when using the TransUnion integration:

  • Snowflake does not consider the TransUnion score filter when matching identities. All matches are included.

  • When the provider, not the consumer, is running an analysis like the Overlap Audience Analysis, the distinct collaboration IDs are based on the consumer’s count, not the provider’s count.

  • You cannot use the SQL Query template to aggregate on the collaboration ID.

If you are an administrator who needs to configure the TransUnion connector so clean room users can use it in the Identity Hub, see TransUnion TruAudience Identity connector.

Enriching data with TransUnion TruAudience Identity

To enrich your data with TransUnion - TruAudience Identity:

  1. Start the clean room creation or installation process.

  2. When you get to the Specify Join Policies step, expand Identity Hub.

  3. Select TransUnion (TruAudience Identity).

  4. In the Table field, select the table that contains the data you want to enhance with TransUnion collaboration IDs.

  5. In the Unique Record Column field, select the column that uniquely identifies a record in the table, for example, a system-generated user id.

  6. Use the User Identifiers section to associate TransUnion identity types with columns in the table. These columns are used to match TransUnion identities. The values in these columns should conform to the following requirements.

    Identity type

    Format requirements

    Address

    • Address Line — Single input. For addresses with lines 1 and 2, combine the two values into a single value.

    • City — String.

    • State — Two-character abbreviation.

    • Zip — Zipcode or Zipcode+4. Exclude special characters such as spaces or hyphens.

    Date of Birth

    yyyy-mm-dd format.

    Device ID

    Either IDs with hyphens (36 character length raw Device IDs/MAIDs/IFAs) or IDs without hyphens (32 & 40 character long hashed Device IDs/MAIDs/IFAs).

    Email

    Plain text or SHA256-hashed lowercase strings.

    First Name

    Upper or lowercase names, including nicknames. Exclude titles and suffixes.

    IP Address

    IPv4 addresses in dot notation or integer format. You can use the PARSE_IP function to obtain the integer format.

    Last Name

    Upper or lowercase names. Exclude middle initials.

    Phone

    Ten digits without special characters like spaces and hyphens.

Matched TransUnion Identities

When Snowflake matches records in the table with TransUnion identities, the collaborator IDs are added to the table in a new column TCUID. When your collaborator adds the column to one of their own tables, then you can match records based on the TransUnion collaborator ID.

Working with the cache

Snowflake maintains a cache that matches the column of the table that uniquely identifies a record with the TransUnion collaborator ID. The cache is stored in the SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.PUBLIC.SAMOOHA_INTERNAL_TRANSUNION_ID_GENERATION_RECORDS table. This table contains the following columns:

Column

Data type

Description

inputid

VARCHAR

Value from the column selected as the Unique Record Column during the integration.

collaborationid

VARCHAR

TransUnion collaboration ID generated based on the input ID and other integration parameters.

lastprocessed

TIMESTAMP_NTZ

Timestamp when TransUnion generated the collaboration ID.

You can perform the following actions to work with the cache:

Delete the cache
TRUNCATE SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.PUBLIC.SAMOOHA_INTERNAL_TRANSUNION_ID_GENERATION_RECORDS;
Copy
Delete specific records from the cache

You can delete specific records from the cache by specifying them as a comma-separated list of single-quoted values. For example, to delete the records with input IDs of 123456 and abcedf, execute:

DELETE FROM SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.PUBLIC.SAMOOHA_INTERNAL_TRANSUNION_ID_GENERATION_RECORDS
  WHERE inputid IN ('123456', 'abcedf');
Copy
Delete multiple records based on input IDs in a separate dataset

You can delete multiple records from the cache when the input IDs are present in a column of another table. For example, if the input IDs to be deleted are listed in the user_id column of the my_db.my_schema.ref_table table, execute:

DELETE FROM SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.PUBLIC.SAMOOHA_INTERNAL_TRANSUNION_ID_GENERATION_RECORDS
  WHERE INPUTID IN (
    SELECT user_id as INPUTID
    FROM my_db.my_schema.ref_table
  );
Copy
Language: English