---
schema_version: "1"
id: 9cf0d884af16fa7504b310b02d7a3f31802d2789dcf9ffd40ea1c00aa0a25581
title: Identity Boost Custom Collaboration Template
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_crc_id_boost_custom_template.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_crc_id_boost_custom_template.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9859f2549709a24e7cb9739d4df36957952771fd6acc3870f5d88ff136e015a9
description: The identity boost custom collaboration template is a JSON configuration that supports identity enrichment use cases in Data 360 Clean Rooms. Use this template to enrich your first-party individual data with third-party identity attributes, such as real IDs from identity resolution providers, in a privacy-safe environment.
products:
  - Data 360
release: "264"
---
# Identity Boost Custom Collaboration Template

The identity boost custom collaboration template is a JSON configuration that supports identity enrichment use cases in Data 360 Clean Rooms. Use this template to enrich your first-party individual data with third-party identity attributes, such as real IDs from identity resolution providers, in a privacy-safe environment.

## Template Overview

The identity boost custom collaboration template includes these fields.

   
| Field Name | Data Type | Requirement | Description |
| --- | --- | --- | --- |
| `name` | string | Required | The name of the collaboration template. For identity boost, the value is MatchBoost. |
| `description` | string | Optional | A short description of the collaboration template. |
| `tables` | object | Required | The input tables used in the collaboration query. Contains the `FirstPartyDataSet` table configuration. |
| `queries` | object | Required | The queries that run in the clean room collaboration to support the use case. |
| `useCaseConfigs` | object | Required | The use case-specific configurations that define supported contact points and output object mappings for identity enrichment. |

## Table Configurations

Each input table used by the query must be defined in the `tables` field. The `tableConfigs` property is an array that can contain multiple table definitions.

- `tableConfigs` (array, required) – A list of table definitions. Each entry represents one table configuration. The identity boost template includes one table configuration, but you can add additional tables as needed.

    
| Field Name | Data Type | Requirement | Accepted Values | Description |
| --- | --- | --- | --- | --- |
| `name` | string | Required | N/A | The name of the table. Value: FirstPartyDataSet. |
| `description` | string | Optional | N/A | A short description of the table. Value: Data set comprising first party information. |
| `role` | string | Required | Provider or Consumer | The role sharing the table in the collaboration. Value: Consumer. |
| `columns` | array | Required | N/A | The schema of the table. Each column object defines a field in the table. |

## Query Configurations

The queries section defines all queries allowed on the combined dataset in the clean room. The identity boost template includes one query through the `queryConfigs` property.

- `queryConfigs` (array, required) – A list of query configurations. The identity boost template includes one query configuration.

    
| Field Name | Data Type | Requirement | Accepted Values | Description |
| --- | --- | --- | --- | --- |
| `name` | string | Required | N/A | The name of the query. Value: MatchBoost. |
| `useCase` | string | Required | MatchBoost | The use case that this query supports. Value: MatchBoost. |
| `description` | string | Optional | N/A | A short description of the query. Value: Enrich first party dataset using third party data. |
| `type` | string | Required | SQL | The type of query. Value: `null` (determined at runtime). |
| `source` | string | Required | N/A | The actual SQL query text. Value: `null` (determined at runtime). |
| `queryParameters` | object | Optional | N/A | The dynamic parameters used in the query. Value: `null`. |
| `referencedTables` | array of strings | Required | N/A | A list of all tables that the query references. Value: \["FirstPartyDataSet"\]. |

## MatchBoost Use Case Configurations

The `useCaseConfigs` section defines the use case-specific settings for identity enrichment, including supported contact points and output object mappings.

   
| Field Name | Data Type | Requirement | Description |
| --- | --- | --- | --- |
| `useCaseType` | string | Required | The type of use case. Value: MatchBoost. |
| `supportedContactPoints` | array of strings | Required | The contact point types used to match and enrich your data. The identity boost template supports Email and PhoneNumber. |
| `outputObjects` | object | Required | Defines where Data 360 writes the enriched data in your org. |

## Output Objects

The `outputObjects` section tells Data 360 where to write the enriched identity data. When the clean room query runs, it creates three types of output:

- A bridge table that connects your original customer IDs to the enriched Real IDs from the identity provider
- Enriched individual records that link the Real IDs to your Data 360 Individual objects
- Enriched contact point records that link the Real IDs to your Data 360 ContactPointEmail objects

The template defines three output objects that work together to store this enriched data.

- `outputObjectConfigs` (array, required) – A list of output object configurations. Each entry defines where Data 360 stores one type of enriched data.

   
| Field Name | Data Type | Requirement | Description |
| --- | --- | --- | --- |
| `objectName` | string | Required | The name of the custom object created in your Data 360 org to store the output. |
| `bridgeTable` | object | Optional | Used for the mapping table that connects your source IDs to Real IDs. Contains the `sourceIdFieldName` property. |
| `relatedTable` | object | Optional | Used for enriched data tables that link to standard Data 360 objects. Contains the `sourceObjectName` (which Data 360 object to link to) and `pathFromBridgeTable` (how to join the tables). |

## SAMPLE\_BRIDGE\_TABLE

This output creates a mapping table between your customer identifiers and the Real IDs from the identity provider.

  
| Field | Value | Description |
| --- | --- | --- |
| `objectName` | `SAMPLE_BRIDGE_TABLE` | The name of the bridge table object in your org. |
| `bridgeTable.sourceIdFieldName` | `SourceId__c` | The field that stores your original customer ID. |
| `relatedTable` | `null` | This is a bridge table, not linked to a Data 360 object. |

## SAMPLE\_INDV\_BOOSTED

This output creates enriched individual records and links them to your Data 360 Individual objects.

  
| Field | Value | Description |
| --- | --- | --- |
| `objectName` | `SAMPLE_INDV_BOOSTED` | The name of the enriched individual object in your org. |
| `bridgeTable` | `null` | Not a bridge table. |
| `relatedTable.sourceObjectName` | `ssot__Individual__dlm` | Links the enriched data to the Individual data model object in Data 360. |
| `relatedTable.pathFromBridgeTable` | Relationship path | Uses the Real ID to connect enriched individual data to your Data 360 individuals. |

## CONTACTEMAIL\_BOOSTED

This output creates enriched contact email records and links them to your Data 360 `ContactPointEmail` objects.

  
| Field | Value | Description |
| --- | --- | --- |
| `objectName` | `CONTACTEMAIL_BOOSTED` | The name of the enriched contact email object in your org. |
| `bridgeTable` | `null` | Not a bridge table. |
| `relatedTable.sourceObjectName` | `ssot__ContactPointEmail__dlm` | Links the enriched data to the `ContactPointEmail` DMO in Data 360. |
| `relatedTable.pathFromBridgeTable` | Relationship path | Uses the Real ID and Party ID to connect enriched email data to your Data 360 `ContactPointEmail` records. |

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note The `pathFromBridgeTable` property defines how to join the enriched data tables with the bridge table and Data 360 objects. It specifies which fields to use as keys when connecting the records.

## Example Scenario

Bridge table mapping: If your customer ID is CUST12345, the bridge table creates a record that connects CUST12345 to the enriched Real ID REAL98765.

Enriched individual records: The enriched individual record for Real ID REAL98765 is linked to your existing Individual record in Data 360.

Enriched contact email records: The enriched email record for Real ID REAL98765 is linked to the corresponding email address in your Data 360 `ContactPointEmail` object.

- **[Identity Boost Custom Template Sample JSON](https://help.salesforce.com/s/articleView?id=data.c360_a_crc_id_boost_custom_template_json.htm&release=264.0.0&type=5)**  
    Copy the template code below or download it directly in Data 360 to begin creating your custom template for the identity boost use case. Fill in the required and optional fields with appropriate values.