Skip to content

fix(rt-personalization): null guards and extLookupKey guidance#123

Open
tdroberto wants to merge 1 commit intotreasure-data:mainfrom
tdroberto:fix/rt-setup-personalization-null-guards
Open

fix(rt-personalization): null guards and extLookupKey guidance#123
tdroberto wants to merge 1 commit intotreasure-data:mainfrom
tdroberto:fix/rt-setup-personalization-null-guards

Conversation

@tdroberto
Copy link
Copy Markdown

Summary

  • Fix entity payload template: stringBuilder: null not [], segmentPayload: null, keyEventFilters: null
  • Add guidance that extLookupKey must match the Parent Segment Profile Key (not a stitching key)
  • Add note to verify stitching key columns exist in event tables before configuring

Root Cause

During PPHG Annex A demo, hit 3 distinct failures:

  1. stringBuilder: [] → API returns misleading "Attribute payload can't be blank"
  2. extLookupKey: "email" when PS profile key was guest_id → batch attributes never resolved
  3. Stitching key referencing column not in event tables → profiles never stitched

Changes

5 targeted edits to realtime-skills/rt-setup-personalization/SKILL.md — no structural changes.

🤖 Generated with Claude Code

…ds and extLookupKey guidance

- stringBuilder/segmentPayload: use null instead of [] to avoid misleading 'Attribute payload can't be blank' error
- extLookupKey: add guidance that it must match PS Profile Key, not a stitching key like email
- keyEventFilters: use null instead of {type:And,conditions:[]}
- Stitching keys: add note to verify columns exist in event tables before configuring
- Add profileCriteria:null and includeSensitive:false to entity payload template

Discovered during PPHG Annex A demo setup.
@tdroberto tdroberto requested review from a team as code owners March 12, 2026 04:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant