identity

Name: identity
Availability: InStock
Author: Treasure Data

Query id_changes logs to track identity stitching events and reconstruct profile histories.

21|24|Updated Oct 21, 2025

Search Tags:#queries #real-time #identity #stitching #id_changes

Ready to run

npx skills add https://github.com/treasure-data/td-skills --skill identity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: identity
Source: https://github.com/treasure-data/td-skills/tree/main/realtime-skills/identity
Command: npx skills add https://github.com/treasure-data/td-skills --skill identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Query identity changes logs to understand profile creation, updates, and merging in real-time within a streaming real-time context.

Core Features & Use Cases

Inspect the id_changes table to follow stitching events
Understand new, updated, and merged identity flows
Time range tips and extraction of key-value attributes

Quick Start

Query the id_changes log for the last 24 hours with a sample query.

Frequently Asked Questions about identity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I query identity change logs to track profile stitching events in real-time?▼

Query the id_changes log using a numeric parent segment ID to retrieve stitching events like profile_added, profile_updated_by_stitching, and profile_deleted_by_stitching. Access requires tdx-skill or Treasure Data mcp-server, an API key with privileges to the cdp_audience_<segment>_rt table, and time-bounded queries using TD_INTERVAL and TD_TIME_FORMAT.

What information can I extract from identity stitching logs?▼

Identity stitching logs record profile creation, merging, and deletion events. You can reconstruct profile histories, understand identity flows across updates, extract key-value attributes, and investigate segment-specific changes within configurable time ranges to track how profiles are created and consolidated.

What are the prerequisites for querying identity change logs?▼

You need a properly configured tdx-skill or Treasure Data mcp-server access, an API key with sufficient privileges to the parent-segment id_changes table formatted as cdp_audience_<segment>_rt, and the numeric parent segment ID. Time-bounded queries require support for TD_INTERVAL and TD_TIME_FORMAT.

Can I use identity stitching logs for real-time segment investigations?▼

Yes. Identity stitching logs support real-time workflows for segment-specific investigations. Query profile changes within specific time ranges to understand stitching behavior, track merging events, and analyze identity flows as they occur in your streaming context.

How do I set up time-bounded queries on identity change logs?▼

Use TD_INTERVAL and TD_TIME_FORMAT parameters to bound your queries by time range. These enable you to query the id_changes table for specific periods, such as the last 24 hours, to isolate profile events and reconstruct histories within your investigation window.