DocumentationJourney OptimizerJourney Optimizer Guide

Personalization validation personalization-validation

Last update: Mon Jan 23 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Intermediate
  • Developer

Validation mechanisms validation-mechanisms

In the Expression editor screen, use the Validate button to check your personalization syntax.

NOTE
The validation is automatically executed when you click on the Add button to close the editor window.

IMPORTANT
If the personalization syntax is not valid, you cannot close the expression editor window.

Common errors common-errors

  • Path “XYZ” not found

When trying to reference a field that is not defined in the schema.

In this case firstName1 is not defined as attribute in the profile schema:


{{profile.person.name.firstName1}}
  • Type mismatch for variable “XYZ”. Expected array. Found string.

When trying to iterate over a string instead of array:

In this case product is not an array:

{{each profile.person.name.firstName as |product|}}
 {{product.productName}}
{{/each}}
  • Invalid handlebars syntax. Found ‘[XYZ}}’

When invalid handlebars syntax is used.

Handlebars expressions are surrounded with {{expression}}

   {{[profile.person.name.firstName}}
  • Invalid segment definition
No segment definition found for 988afe9f0-d4ae-42c8-a0be-8d90e66e151

The errors related to offers integration in an Email or Push message have the following pattern :

Offer.<offerType>.[PlacementID].[ActivityID].<offer-attribute>

The validation is performed during personalization content validation in the Expression editor.

Error title
Validation / Resolution
Resource with id placementID and type OfferPlacement not found
Resource with id activityID and type OfferActivity not found
Check if ActivityID and/or PlacementID are available
Resource could not be validated.
The componentType in the Placement should match the offerType offer
The public URL is not present in offer offerId.
The Image Offers (all Personalized and fallback associated with the decision and placement pair) should have public URL populated (deliveryURL should not be empty).
The decision contains non-profile attributes.
Offers Model usage should contain only the profile attributes.
An error occurred while fetching the decision usage.
This error could occur when the API is trying to fetch the offer model.
Offer Attribute offer-attribute is invalid.
Check if the offer-attribute referenced in offer drp is valid. Following are the valid attributes:
Image: deliveryURL, linkURL
Text: content
HTML: content
recommendation-more-help
b22c9c5d-9208-48f4-b874-1cefb8df4d76