Personalization U.I. - my custom schema attributes not rendering | Community
Skip to main content
U
user61843
November 2, 2025
Solved

Personalization U.I. - my custom schema attributes not rendering

  • November 2, 2025
  • 3 replies
  • 246 views

I created schema datasets and all enabled for profile - I confirmed my profiles is showing the associated attirubtes in Profile browse.

 

However, when I try to use them in personalization of email template - I see the attributes populating in left rail mycompany (object) and attributes under that object and I can drag and drop them onto the canvas 

 

But when I simulate the content - its not applied.

 

Does anyone have similar experience? if so, how do I fix it?

Best answer by Mayank_Gandhi

@user61843 

Key Points To Check 

Attribute Visibility vs. Population vs. Personalisation Context

  • Visible in left rail means the schema and dataset are configured for profile and AJO is ingesting the schema metadata.
  • Able to drag and drop into the template means they're part of the schema, but this does not guarantee the attribute is populated or correctly resolved at render time.
  • If simulation results in unresolved or blank content, this typically indicates:The profile selected for simulation does not actually have the expected attribute value populated at the data layer. Personalization context (what is available to the templating engine) does not include the attribute.

 Profile Test Data—Always Validate

  • In the simulation/test dialog, ensure you are choosing a test profile that actually has a value for your custom attribute.
  • You can use the right-hand attribute data browser in the simulation dialog to confirm what is available for each test profile (see Experience League documentation).

3 replies

SashankaBi1
SashankaBi1
Level 2
November 2, 2025

Hi @user61843 ,

 

If profile attributes appear in Profile Browse but aren’t showing in email personalization, it’s usually a timing issue. Real-time updates need a few minutes to stitch to the profile before the journey uses them. Try adding a short Wait activity (around 5 minutes) before the email step so the latest attributes are available.

 

Also, please share the source of the data (real-time stream, batch ingestion, FAC or other) so we can better understand why the attributes might not be available for personalization.

 

Please try to add a Wait Activity for 5 mins prior to any conditional or personalization templates, let me know if that helps. It worked for me when sourcing FAC data.

 

Thanks a lot

Sashanka B

 

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
November 3, 2025

@user61843 

Assuming you've enabled the testProfile flag, have you tried the "simulate content variations" option? More details can be found here:

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/test/preview-test/simulate-sample-input

If you're using personalization functions to display values, please verify them in the personalization editor:

https://experienceleague.adobe.com/en/apps/journey-optimizer/ajo-personalization?lang=en

If the issue persists, kindly provide additional details about the personalization attribute and how it's used within the content template.

 

Thanks, Sathees
    Mayank_Gandhi
    Adobe Employee
    Mayank_GandhiAdobe EmployeeAccepted solution
    Adobe Employee
    November 3, 2025

    @user61843 

    Key Points To Check 

    Attribute Visibility vs. Population vs. Personalisation Context

    • Visible in left rail means the schema and dataset are configured for profile and AJO is ingesting the schema metadata.
    • Able to drag and drop into the template means they're part of the schema, but this does not guarantee the attribute is populated or correctly resolved at render time.
    • If simulation results in unresolved or blank content, this typically indicates:The profile selected for simulation does not actually have the expected attribute value populated at the data layer. Personalization context (what is available to the templating engine) does not include the attribute.

     Profile Test Data—Always Validate

    • In the simulation/test dialog, ensure you are choosing a test profile that actually has a value for your custom attribute.
    • You can use the right-hand attribute data browser in the simulation dialog to confirm what is available for each test profile (see Experience League documentation).
      Terms & ConditionsAccessibility statement

      Loading footer...