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

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

subAttributeIdentifier rules:

• ListAttribute → must match aggregation identifier
• SlidingCounterAttribute → must match sub_duration identifier
• SingleAttribute/CounterAttribute → must be absent

stringBuilder

segmentPayload

{
  "segmentPayload": {
    "batchSegments": [
      {"id": "segment_id_1"},
      {"id": "segment_id_2"}
    ]
  }
}

• batchSegments required array
• Each id required and unique

catalogPayload (Feature-Flagged)

Unsupported attribute types: ImportedAttribute, CounterAttribute Error: unsupported_attribute_type_for_lookup_catalog

Common Errors & Solutions

Error-Free Templates

Template 1: Minimal Valid Entity

{
  "attributes": {
    "audienceId": "PARENT_SEGMENT_ID",
    "name": "personalization_name",
    "description": "Description of use case",
    "sections": [{
      "name": "section_name",
      "entryCriteria": {
        "name": "trigger_name",
        "keyEventCriteria": {
          "keyEventId": "KEY_EVENT_ID",
          "keyEventFilters": null
        }
      },
      "payload": {
        "UNIQUE_NODE_ID": {
          "type": "ResponseNode",
          "name": "response_name",
          "definition": {
            "attributePayload": [{
              "realtimeAttributeId": "RT_ATTR_ID",
              "outputName": "output_name"
            }],
            "segmentPayload": null,
            "stringBuilder": null
          }
        }
      },
      "includeSensitive": false
    }]
  },
  "relationships": {
    "parentFolder": {
      "data": {
        "id": "FOLDER_ID",
        "type": "folder-segment"
      }
    }
  }
}

Template 2: With String Builder

{
  "attributes": {
    "audienceId": "PARENT_SEGMENT_ID",
    "name": "personalization_with_message",
    "description": "Personalization with welcome message",
    "sections": [{
      "name": "all_visitors",
      "entryCriteria": {
        "name": "pageview",
        "keyEventCriteria": {
          "keyEventId": "KEY_EVENT_ID",
          "keyEventFilters": null
        }
      },
      "payload": {
        "UNIQUE_NODE_ID": {
          "type": "ResponseNode",
          "name": "visitor_data",
          "definition": {
            "attributePayload": [
              {"realtimeAttributeId": "RT_ATTR_1", "outputName": "last_product"},
              {"realtimeAttributeId": "RT_ATTR_2", "outputName": "page_views"}
            ],
            "segmentPayload": null,
            "stringBuilder": [{
              "values": [{"value": "Welcome to our website!", "type": "String"}],
              "outputName": "welcome_message"
            }]
          }
        }
      },
      "includeSensitive": false
    }]
  },
  "relationships": {
    "parentFolder": {
      "data": {"id": "FOLDER_ID", "type": "folder-segment"}
    }
  }
}

Template 3: List Attribute with subAttributeIdentifier

{
  "definition": {
    "attributePayload": [
      {
        "realtimeAttributeId": "LIST_ATTR_ID",
        "subAttributeIdentifier": "items",
        "outputName": "browsed_items"
      },
      {
        "realtimeAttributeId": "SINGLE_ATTR_ID",
        "outputName": "last_item"
      }
    ],
    "segmentPayload": null,
    "stringBuilder": null
  }
}

Bash Validation Function

validate_personalization_payload() {
  local payload_json="$1"

  # Check for empty arrays (common mistake)
  if echo "$payload_json" | grep -q '"stringBuilder":\s*\[\s*\]'; then
    echo "❌ ERROR: stringBuilder is empty array. Change to null."
    return 1
  fi

  if echo "$payload_json" | grep -q '"attributePayload":\s*\[\s*\]'; then
    echo "❌ ERROR: attributePayload is empty array. Change to null."
    return 1
  fi

  # Check for template brackets in stringBuilder values
  if echo "$payload_json" | grep -q '{{.*}}'; then
    echo "❌ ERROR: stringBuilder values cannot contain {{ or }}"
    return 1
  fi

  # Verify at least one payload type has content
  local has_attrs=$(echo "$payload_json" | jq '.attributes.sections[0].payload | .. | .attributePayload? | select(. != null and . != []) | length')
  local has_strings=$(echo "$payload_json" | jq '.attributes.sections[0].payload | .. | .stringBuilder? | select(. != null and . != []) | length')

  if [ -z "$has_attrs" ] && [ -z "$has_strings" ]; then
    echo "❌ ERROR: Must include at least one: attributePayload or stringBuilder with content"
    return 1
  fi

  echo "✅ Payload validation passed"
  return 0
}

# Usage:
# validate_personalization_payload "$PAYLOAD_JSON" || exit 1

Pre-Creation Checklist

Before creating a personalization entity:

• Payload node ID is unique (use uuidgen | tr -d '-' | tr '[:upper:]' '[:lower:]')
• All optional arrays use null not []
• At least one of attributePayload/stringBuilder has content
• All outputName fields are unique across the section
• realtimeAttributeId values exist in CDP
• ListAttributes include correct subAttributeIdentifier
• No {{ or }} in stringBuilder values
• Field names use camelCase (not snake_case)

Quick Fix Guide

If you see: "Attribute payload can't be blank"

1. Check stringBuilder first:

   # Find the problem
   echo "$PAYLOAD" | grep -o '"stringBuilder":\s*\[.*\]'
   
   # If empty [], change to null
   PAYLOAD=$(echo "$PAYLOAD" | sed 's/"stringBuilder":\s*\[\]/"stringBuilder": null/g')
   

2. Check attributePayload:

   # If empty [], change to null
   PAYLOAD=$(echo "$PAYLOAD" | sed 's/"attributePayload":\s*\[\]/"attributePayload": null/g')
   

3. Verify at least one has content:

   • If both are null, add at least one RT attribute OR one string builder value

If you see: "Name has already been taken"

# List existing personalizations
tdx api "/entities/realtime_personalizations?filter[audience_id]=<ps_id>" --type cdp | jq '.data[] | {id, name}'

# Either use a different name or update the existing entity

Production-Tested Examples

These examples successfully created personalization entities in production:

Example 1: EV Ecommerce (Entity ID: 310)

• Parent Segment: 1069935
• Key Event: 806 (pageview)
• Attributes: 7 RT attributes
• stringBuilder: Welcome message
• Success: Created without errors

Example 2: ACME Web Personalization (Entity ID: 312)

• Parent Segment: 1053580
• Key Event: 815 (pageview)
• Attributes: 3 RT attributes
• stringBuilder: Welcome message
• Success: Created without errors

Common pattern: Both include populated stringBuilder (not empty array)

References

• OpenAPI Spec: Payload structure is undefined (object/null only)
• Frontend: Uses crypto.randomUUID() for payload node IDs
• Validation: Server-side validation is strict but error messages are misleading