Lookup table usage

After Hightouch runs identity resolution (IDR) on your graph, Hightouch outputs lookup tables into your warehouse. These tables live in the hightouch_planner schema (or the schema override for your source) and can be used across your downstream workflows.

Your marketing team can use these tables for paid campaigns, your sales team for deduplicating outreach efforts, or your data science team for fraud detection.

The output of IDR can also helpful in constructing models or parent models in Hightouch.

Hightouch creates the following output tables:

1. A RESOLVED table (<output_prefix>_resolved) that labels each row from your input tables with a HT_ID representing a profile. This table tells you all the input rows associated with a profile by its HT_ID. The SOURCE is the slug of an input model. The PRIMARY_KEY is the primary key value from the input model. The LATEST_TIMESTAMP is the timestamp of the row from the input model.

2. A RESOLVED_IDENTIFIERS table (<output_prefix>_resolved_identifiers) includes all the unique identifiers associated with each profile. Each row represents a unique identifiers associated with a profile. COUNT represents the number of times the identifier was seen in an input row, including updated rows if the same row gets seen multiple times due to updates. IDENTIFIER is the type of identifier. VALUE is the identifier value for the profile.

3. A UNRESOLVED table (<output_prefix>_unresolved) lists all input rows Hightouch couldn't process because the primary key values weren't unique within the originating model.

4. GOLDEN_RECORD table (<output_prefix>_golden_records):
   (Optional) Only appears if you enable Golden Record in your IDR project's settings. Golden Record flattens all possible values of each identifier into either:

   • A single "best" or "primary" value based on survivorship rules (most recent, most frequent, or source priority)
   • An array of all unique values when using the array survivorship rule

   See our Golden Record doc for more details about survivorship rules and array fields.

   Each row corresponds to a single HT_ID (one identity). For example, a row might look like:

   {
     "ht_id": "ht1",
     "most_recent_email": "user@example.com",                -- using most recent survivorship
     "all_phone_numbers": ["123-456-7890", "098-765-4321"],  -- using array survivorship
     "primary_user_id": "user_123"                           -- using source priority survivorship
   }
   

State tables

Hightouch also uses the same hightouch_planner schema to manage state tables for each identity graph. These tables, typically prefixed with IDR_... or IDR_BACKUP_..., are used internally to support incremental runs and maintain graph consistency.