Dataset Lookup in AJO Personalization Returning Empty Object | Community
Skip to main content
Level 2
April 30, 2026
Question

Dataset Lookup in AJO Personalization Returning Empty Object

  • April 30, 2026
  • 2 replies
  • 25 views

Summary:

I am using dataset lookup in AJO personalization, but it is returning empty values. My dataset has a primary identity and data is present. I have tried both approaches — with fields nested under the tenant namespace and also without nesting — but still getting empty results. Not sure what is causing the issue or how to fix it.



AEP   configuration:

schema : {

tenant : {

offerID (primary id),

title ,

description

}

}

  • Dataset is enabled for lookup
  • Identity is marked as primary
  • Data exists in dataset (e.g., "IC121")
  • Using hardcoded ID in lookup

Note: Schema and Dataset is not profile enabled

In AJO (Campaign - CBE based), I am trying to access this data using personalization:

Code:

[ {{ datasetLookup datasetId="Dataset" id="ID121" result="offer"}}

 {

“title” : “{{offer.tenant.title}}”,

“description” : “offer.tenant.description”

}]

 

Issue:

The response is:

{

title :””,

description : “”

}

 

It seems like the lookup is not executing. Can anyone help me what i am missing

Thanks in advance

2 replies

Level 3
April 30, 2026

Hey ​@Rahul 

There are few things to check

  1. The schema must be of record-type for lookup to work. Therefore, do let me know if you’re using that type or else you would need to create a new one with new class of record-type. 
  2. And the identifier’s namespace should be of non-person identifier. Kindly check the assigned namespace for your field offerID

  3. It could be that the dataset might not be actually enabled for lookup service. I’d recommend you to check the status of lookup with this API endpoint mentioned here. If you don’t see the status of lookup key being enabled to true, then you could enable it via API

  4. If the above settings are configured & setup correctly and the lookup is still not working, then the data might not be properly ingested and mapped to the fields in your schema. I’d suggest using Data Prep to map data via either API or in UI ingestion workflows

Hope this helps!

 

Regards,

Ganesh Kumar

RahulAuthor
Level 2
May 1, 2026

Hi ​@IamCGK  thanks for the detailed response — really helpful.

The points you mentioned:

  • The dataset is based on a record-type schema

  • The identity field OfferID is configured as non-person identifier and marked as primary

  • The dataset is enabled for lookup (verified from UI)

  • Data is present in the dataset and visible in preview

However, I am still getting an empty object {}  from dataset Lookup. 

 

Is there any way to debug or check the log