title:Sample Queries

-path:/unify/profiles-sync/tables

title:Tables & Materialized Views

-section_title:Linked Profiles

slug:unify/linked-profiles

section:

-section_title:Setup Guides

slug:unify/linked-profiles/setup-guides

section:

-path:/unify/linked-profiles/setup-guides/bigquery-setup

title:BigQuery Setup

-path:/unify/linked-profiles/setup-guides/snowflake-setup

title:Snowflake Setup

-path:/unify/linked-profiles/setup-guides/redshift-setup

title:Redshift Setup

-path:/unify/linked-profiles/linked-events

title:Linked Events

-section_title:Traits

slug:unify/traits

section:

1. In the edit panel, define the[conditions](#conditions) under which the action should run.

2. Test those conditions to make sure that they correctly match an expected event.

This step looks for events that match the criteria in the[debugger queue](/docs/connections/sources/debugger/), so you might need to Trigger some events with the expected criteria to test your conditions. You can skip the test step if needed, and re-try it at any time.

3. Next, set up the data mapping from the Segment format to the destination tool format.

4. Test the mapping with data from a sample event.

3. Select data models to[enrich your events](/docs/unify/linked-profiles/linked-events/) with.

4. Set up the data mapping from the Segment format to the destination tool format.

- You can click the Source field, then select the**Enrichments** tab to view and select Enrichments to use.

5. Test the mapping with data from a sample event.

The edit panel shows you the mapping output in the format for the destination tool. You can change your mapping as needed and re-test.

5. When you're satisfied with the mapping, click**Save**. Segment returns you to the Mappings table.

6. In the Mappings table**Status** column, verify that the**Enabled** toggle is on for the mapping you just customized.

6. When you're satisfied with the mapping, click**Save**. Segment returns you to the Mappings table.

7. In the Mappings table**Status** column, verify that the**Enabled** toggle is on for the mapping you just customized.

* Read-only access warehouse destination and warehouse destination settings.*(For example, Redshift, Postgres, BigQuery)*

***Scope:** Grants access to*all* warehouses.

Full CRUD (create, read, access, and delete) access to all Entities within a workspace. You can also grant or revoke user permissions.

Read-only access to all Entities models and destinations in a workspace.

title:Linked Events

beta:true

plan:unify

Use Linked Events to enrich real-time event streams with entities from your data warehouse to your destinations. Insert additional event context for downstream applications for richer data about each event.

On this page, you'll learn how to get started with Linked Events.

With Linked Events, you can:

-**Add details to events for precise targeting**. Enable targeting by appending product events that only have`product_id` with full product SKU details from your warehouse.

-**Sync enriched data**. Add a loyalty ID to event payloads before sending it downstream to destinations such as Amplitude, Mixpanel, and more.

-**Reduce load times**. Enrich page view events with products and subscriptions connected to that view, and send that to Google Analytics 4 to lighten the front end and reduce page loading time.

Before getting started with Linked Events, you'll need:

1.[BigQuery](/docs/unify/linked-profiles/setup-guides/bigquery-setup/),[Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake-setup/), or[Redshift](/docs/unify/linked-profiles/setup-guides/redshift-setup/) data warehouse credentials with**write** access.

2. Access to Unify in your workspace.

3. Access to the Destination you'll be using with Linked Events so that you can validate your data.

The following Segment access[roles](/docs/segment-app/iam/roles/) apply to Linked Events:

**Entities Admin Access**: Full CRUD (create, read, access, and delete) access to all Entities within a workspace. You can also grant or revoke user permissions.

**Entities Read-only Access**: Read-only access to all Entities models and destinations in a workspace.

For Linked Events, you need the following roles:

To use Connections with Linked Events:

To get started, you'll need to connect a data warehouse. Linked Events supports[BigQuery](/docs/unify/linked-profiles/setup-guides/bigquery/),[Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake/), and[Redshift](/docs/unify/linked-profiles/setup-guides/redshift-setup/).

1. Navigate to**Unify > Data graph** and click**Add warehouse**.

2. Select a warehouse to connect from the[supported data warehouses](#supported-data-warehouses).

3.[Connect your warehouse](#connect-your-warehouse).

3. Click**Test Connection** to be sure your warehouse is connected.

4. After a successful test, click**Save**.

For Linked Events, the sync destination is an internal Segment data store. To track the data you send to Segment, you can view deltas/diffs in tables within a single schema Segment creates called`_segment_reverse_etl`.

You can choose which database within your warehouse this data lives in.

The table below shows the data warehouses Linked Events supports. View the Segment docs for your warehouse, then carry out the corresponding steps.

| Data Warehouse| Steps|

|------------------------|-------------------------|

|[Snowflake](docs/unify/linked-profiles/setup-guides/snowflake-setup/)| 1. Configure your snowflake database. <br> 2. Enter your credentials. <br> 3. Test the Connection. <br> 4. Click**Save**.|

|[BigQuery](/docs/unify/linked-profiles/setup-guides/bigquery-setup/)| 1. Add your credentials to the database that has tables with the entities you want to enrich your event with. <br> 2. Test your connection.|

|[Redshift](/docs/unify/linked-profiles/setup-guides/redshift-setup/)| 1. Select the Redshift cluster you want to connect. <br> 2.[Configure](/docs/connections/storage/catalog/redshift/#networking) the correct network and security settings.|

After you connect your warehouse, use the Data graph overview page (**Unify > Data graph**) to view entities Segment has synced from your data warehouse, add a new entity, and view data warehouse settings.

To add a new entity:

1. Click**Add entity**.

2. Select the table(s) from your warehouse that you'll use as an entity.

3. For each table you select, choose a primary key from the drop-down menu.

- The primary key uniquely identifies rows in your table.

4. Click**Add entities**.

To use Linked Events, you'll need to add a destination to send enriched events to. Navigate to**Connections > Destinations**. Select an existing destination, or click**+ Add destination** to add a new destination.

With Linked Events, you can select entities and properties from your data warehouse, then add enrichments to map properties to your connected destination.

To enrich events with entities:

1. Navigate to**Connections > Destinations > Event streams**

2. Select the destination you'd like to create an enrichment on.

3. From the Destination overview page, click**Mappings**.

4. Click**New Mapping**, and select the type of mapping you'd like to add.

- Click the**...** icon to edit an existing mapping.

5. In the "Select Events to Map and Send", define the[conditions](/docs/connections/destinations/actions/#conditions) under which the action should run.

6. Click**Load Sample Event**, then add your entities.

After you load a sample event, you can add entities from the**Enrich events with entities** section. You’ll select an entity, then an entity match property.

- The entity match property is the property in the event that you want to match to the primary key.

After you’ve added an entity and match property, add your event enrichments.

Use enrichments to select the entity you wish to send to your downstream destination.

In the Mappings tab, locate the**Select Mappings** section where you can enrich source properties from the entities you've selected in the previous step.

1. Select the propery field that you'd like to enrich, then select the**Enrichments** tab.

2. Select the entity you want to send to your destination.

- You’ll have access to all rows/columns in your data warehouse associated with the property you've selected in the previous step.

3. Add the key name on the right side, which is what Segment sends to your destination.

After you’ve added Enrichments, test and save your enrichments.

1. Test the mapping with data from a sample event.

- The edit panel shows you the mapping output in the format for the destination tool. You can change your mapping as needed and re-test.

2. When you're satisfied with the mapping, click**Save**. Segment returns you to the Mappings table.

To use Linked Events, be sure that you have proper permissions for the Data Warehouse you're using. Visit the[BigQuery](/docs/unify/linked-profiles/setup-guides/bigquery-setup/),[Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake-setup/), and[Redshift](/docs/unify/linked-profiles/setup-guides/redshift-setup/) setup guides to learn more about updating permissions.

Segment currently syncs once every hour.

For Linked Events, Segment supports all Actions Destinations.

Test events don't send Linked Events. You'll only see test events that come from the source debugger, which is ahead of the event enrichment.

Linked Events uses the existing Audit Trail in your Segment workspace. To view your Audit Trail, navigate to**Settings > Admin > Audit Trail**.

You can define a schedule for refreshing the linked data from your data warehouse.

title:BigQuery Setup

beta:true

plan:unify

On this page, you'll learn how to connect your BigQuery data warehouse to Segment.

To set up the Segment BigQuery connector:

1. Navigate to**IAM & Admin > Service Accounts** in BigQuery.

2. Click**+ Create Service Account** to create a new service account.

3. Enter your**Service account name** and a description of what the account will do.

4. Click**Create and Continue**.

5. In the**Grant this service account access to project** section, select the[*BigQuery User*](https://cloud.google.com/bigquery/docs/access-control#bigquery.user){:target="_blank"} role to add.

6. Click**+ Add another role** and add the*BigQuery Job User* role.

7. Click**+ Add another role** and add the[*BigQuery Metadata Viewer*](https://cloud.google.com/bigquery/docs/access-control#bigquery.metadataViewer){:target="_blank"} role.

8. Click**Continue**, then click**Done**.

9. Search for the service account you've just created.

11. From your service account, click the three dots under**Actions** and select**Manage keys**.

12. Click**Add Key > Create new key**.

13. In the pop-up window, select**JSON** for the key type, and click**Create**.

14. Copy all the content within the file you've created and downloaded.

15. Navigate to Segment and paste all the credentials you've just copied into the**Enter your credentials** section as you connect your warehouse destination.

Grant access to datasets and tables so that Segment can list datasets, tables, and columns, and create Linked Events.

Grant

-[`BigQuery Data Viewer`](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataViewer){:target="_blank"} role <br>

OR

- Permissions:

These can be scoped to projects or[datasets](https://cloud.google.com/bigquery/docs/control-access-to-resources-iam#grant_access_to_a_dataset){:target="_blank"}.

title:Redshift Setup

beta:true

plan:unify

On this page, you'll learn how to connect your Redshift data warehouse to Segment.

To get started with Redshift:

1. Log in to Redshift and select the Redshift cluster you want to connect.

2. Follow these[networking instructions](/docs/connections/storage/catalog/redshift/#networking) to configure network and security settings.

Run the SQL commands below to create a role (`segment_entities`) and user (`segment_entities_user`).

CREATE ROLE segment_entities;

GRANT CREATEON DATABASE"<enter database name here>" TO ROLE segment_entities;

CREATEUSERsegment_entities_user PASSWORD'<enter password here>';

GRANT ROLE segment_entities TO segment_entities_user;

You'll need to grant access to schemas and tables that you'd like to enrich with. This allows Segment to list schemas, tables, and columns, as well as create entities with data extracted and ingested to Segment.

Grant schema permissions based on customer need. Visit Amazon's docs to view[schema permissions](https://docs.aws.amazon.com/redshift/latest/dg/r_GRANT.html){:target="_blank"} and[example commands](https://docs.aws.amazon.com/redshift/latest/dg/r_GRANT-examples.html){:target="_blank"} that you can use to grant permissions.

GRANTUSAGEONSCHEMA<schema-name>TOROLEsegment_entities;

Grant table permissions based on customer need. Learn more about Amazon's[table permissions](https://docs.aws.amazon.com/redshift/latest/dg/r_GRANT.html){:target="_blank"}.

GRANTSELECTONTABLE<schema-name>.<table-name>TOROLEsegment_entities;

If you used RETL in your database, you'll need to add the following[table permissions](https://docs.aws.amazon.com/redshift/latest/dg/r_GRANT.html){:target="_blank"}:

GRANTUSAGE,CREATEONSCHEMA__segment_reverse_etlTOROLEsegment_entities;

GRANTSELECT,INSERT,UPDATE,DELETEONALLTABLESINSCHEMA__segment_reverse_etlTOROLEsegment_entities;