Overview
Import user group memberships (e.g., household relationships) from your data warehouse using Connectivity. This enables household-level identity resolution and allows you to build User Group Cohorts that target groups of users rather than individuals.Prerequisites:
- Connectivity set up and configured for your data warehouse
- At least one User-level identifier configured in Identity > Identifiers
- At least one User Group-level identifier configured in Identity > Identifiers
- User group membership data available in your data warehouse
Steps
Configure required identifiers
In Identity > Identifiers, ensure you have:
- At least one User-level identifier (e.g.,
email_sha256,appnexus) for identifying individual users - At least one User Group-level identifier (e.g.,
household_id,group_id) for identifying user groups
Prepare data warehouse table
Create or identify a table in your data warehouse with the following columns:
- user_id (required): Contains user identifiers matching your configured User-level identifier
- group_id (required): Contains group identifiers matching your configured User Group-level identifier
- cursor (required): Timestamp column indicating when the user was added to the group (used for incremental processing)
- is_deleted (optional): Boolean column where
TRUEindicates the user should be removed from the group
Create Connectivity connection
In the Permutive dashboard, navigate to Connectivity and create a new connection to your data warehouse if one doesn’t exist.
Create Group Identity Data import
Create a new Connectivity import and select Group Identity Data as the data type. This import type is specifically designed for user group membership data.
Configure import columns
Map your data warehouse columns to the required fields:
- Map the Group ID column to your User Group-level identifier
- Map the User ID column to your User-level identifier
- Map the Timestamp column to your cursor field
- Optionally map the Delete column if you have an is_deleted field
Set import frequency
Configure how often the import should run. Connectivity uses the cursor column to process only new data incrementally, avoiding full table re-imports.
Data Format Requirements
Your data warehouse table should follow this structure:| user_id | group_id | cursor | is_deleted |
|---|---|---|---|
| user123 | household456 | 2025-01-01 10:00:00 | FALSE |
| user124 | household456 | 2025-01-01 10:00:00 | FALSE |
| user125 | household457 | 2025-01-02 14:30:00 | FALSE |
| user123 | household456 | 2025-01-15 09:00:00 | TRUE |
- Each Connectivity import supports only one type of identifier for User and Group data
- You cannot mix multiple identifier types (e.g., both HEM and AppNexus IDs) in the same import
- The user_id can be a Permutive user ID or any configured User-level identifier
- The group_id must match a configured User Group-level identifier