rt-personalization-validation

RT Personalization Entity Validation

Validates personalization entity payloads and provides error-free templates.

When to Use This Skill

Proactive Validation (REQUIRED)

During rt-setup-personalization workflow at Step 9c:

• MUST be invoked BEFORE making the personalization entity creation API call
• Validates the complete payload JSON with actual values (not placeholders)
• Prevents common API errors by catching issues before submission
• This is a mandatory workflow step, not optional

Reactive Validation (Debugging)

After encountering API errors:

• When seeing "Attribute payload can't be blank" errors
• When personalization creation fails with validation errors
• When reviewing existing personalization configurations
• When troubleshooting payload structure issues

Critical Validation Rules

Rule #1: Empty Arrays Cause Errors

The #1 cause of "Attribute payload can't be blank" errors:

// ❌ FAILS - Empty arrays trigger validation errors
"stringBuilder": []
"attributePayload": []

// ✅ WORKS - Use null instead
"stringBuilder": null
"attributePayload": null

Value	Result
null or omitted	✅ OK - skips validation
[] (empty array)	❌ ERROR - "can't be blank"

Rule #2: At Least One Payload Required

Section definition must include at least ONE of:

• attributePayload (with content)
• stringBuilder (with content)
• catalogPayload (with content, feature-flagged)

All three cannot be null/empty simultaneously.

Rule #3: Misleading Error Messages

The API reports errors incorrectly:

Error: "sections[0].payload.node_id.definition.attribute_payload": ["Attribute payload can't be blank"]

Actual cause: stringBuilder: [] (empty array) Reported cause: attribute_payload (misleading)

Always check stringBuilder first when seeing "can't be blank" errors.

---

Field Validation Rules

attributePayload

Field	Validation
outputName	Required, max 256 chars, unique across all payload types
realtimeAttributeId	Required, must exist in CDP cache
subAttributeIdentifier	Required for ListAttribute/SlidingCounterAttribute only