Can I have multiple stitching keys?

Yes, you can define multiple stitching keys to capture all possible identifiers present in your event data, ensuring more comprehensive profile merging.

How do I validate my ID stitching configuration?

This skill provides guidance on using the 'tdx ps rt validate' command to check that your primary keys, stitching keys, and regex patterns are correctly formatted.

How do I exclude test data from my ID stitching configuration?

You can use the 'exclude_regex' property within the stitching_keys configuration to filter out identifiers matching specific test patterns, such as '^test_.*' or '.*@example.com$'.

What is a primary key in this context?

The primary key is the main unique identifier for a profile. It must be stable, unique, and present in the majority of your event data.

What is the purpose of ID stitching in Treasure Data RT 2.0?

ID stitching merges disparate data points from various sources into a single unified profile by linking shared identifiers like email, user_id, or device cookies.

Treasure Data RT ID Stitching

Name: Treasure Data RT ID Stitching
Author: treasure-data

bytreasure-data

•

マーケティングオートメーション

Configures real-time profile merging and identity resolution across multiple identifiers within Treasure Data RT 2.0.

The rt-config-id-stitching skill provides a specialized framework for developers and data engineers to implement sophisticated identity resolution within Treasure Data. It streamlines the process of defining primary keys, managing stitching keys like emails or device IDs, and applying robust regex-based exclusion rules to ensure data hygiene. By automating the configuration of profile merging, this skill helps maintain a consistent 'single customer view' across diverse data streams, enabling high-performance real-time personalization and accurate cross-channel attribution.

主な機能

01Standardized configuration for primary and stitching keys

02Schema validation for Treasure Data RT 2.0 requirements

03Regex-based filtering to exclude test, guest, or invalid identifiers

0416 GitHub stars

05External lookup key configuration for CRM and API integrations

06Monitoring utilities for profile merge activity and change logs

ユースケース

01Unifying mobile device identifiers with CRM data for cross-platform tracking

02Merging anonymous web cookie IDs with authenticated user profiles upon login

03Filtering development and staging data out of production audience segments

主な機能

01Standardized configuration for primary and stitching keys

02Schema validation for Treasure Data RT 2.0 requirements

03Regex-based filtering to exclude test, guest, or invalid identifiers

0416 GitHub stars

05External lookup key configuration for CRM and API integrations

06Monitoring utilities for profile merge activity and change logs

ユースケース

01Unifying mobile device identifiers with CRM data for cross-platform tracking

02Merging anonymous web cookie IDs with authenticated user profiles upon login

03Filtering development and staging data out of production audience segments