CRT Visibility and Outbound Bridge Sharing

Overview

When using Amperity Bridge to share data with external data warehouses like Snowflake, users may notice that certain tables—specifically the Customer Resolution Table (CRT)—appear in the external catalog but contain zero records. This article explains why the CRT is restricted from outbound sharing and provides the recommended workaround.


Symptoms

  • An outbound bridge for Snowflake is successfully configured and synced.

  • The CRT (Customer Resolution Table) is visible in the Snowflake UI.

  • Executing a SELECT query against the CRT in Snowflake returns a successful execution but with 0 rows, even though the table is fully populated within the Amperity tenant.


Cause

The CRT is classified as a specialized internal system table rather than a standard data table.

Amperity Bridge architecture is optimized for sharing domain tables and unified output tables. Because the CRT is part of the internal identity resolution metadata layer, it does not materialize data within the Bridge interface during the synchronization process. Consequently, while the schema/metadata is shared, the physical records are not projected to the outbound destination.


Workaround: Using a Custom Domain Table (CDT)

To successfully share CRT data via Amperity Bridge, you must mirror the data into a standard table format that the Bridge can materialize.

Step 1: Create a Custom Domain Table (CDT)

Create a new CDT that selects the required fields from the CRT. This "promotes" the system data into a standard domain table format.

Example SQL:

SQL

 
SELECT
  amperity_id,
  given_name,
  surname,
  email,
  -- Add other required fields from CRT
  _pk
FROM
  Customer_Resolution_Table

Step 2: Update the Outbound Bridge

  1. Navigate to the Destinations page in Amperity.

  2. Edit your Outbound Share configuration.

  3. Add the newly created CDT to the share.

  4. Save and Sync the bridge.

Step 3: Verify in Snowflake

Once the sync is complete, the new CDT will be visible in Snowflake and will contain the records previously missing from the direct CRT share.


Summary Table

FeatureSupported for CRT?Supported for CDT?
Outbound Bridge SharingNo (Schema only, 0 records)Yes (Full data visibility)
Standard Data ExportYesYes
Visual Query AccessYesYes