Request for Edge Network for decision

​@Dex 666 

For server-side Edge Decisioning requests from Contentful, the identityMap is not written to the system dataset ajo_exd_decision_event_dataset. Instead, the request payload lands in the Experience Event dataset mapped to the Datastream (configId / dataStreamId) used by the /interact call.

To debug identities, check the Datastream → attached Event Dataset → query fields like identityMap and _experience.decisioning.propositions. The ajo_exd_decision_event_dataset is mainly populated by Journey/Outbound decisioning flows, not generic server-side Edge fetches. 

HI ​@Dex 666 
For a server-side AJO Code-Based Experience (CBE) fetch, I'd check the Experience Event dataset configured on the exact datastream used by the /interact request—rather than assume the request lands in one universal AJO Decisioning dataset. The request is sent to a datastream, and the datastream's configuration controls where its event data is routed. https://developer.adobe.com/data-collection-apis/docs/endpoints/interact/
 https://experienceleague.adobe.com/en/docs/experience-platform/datastreams/overview

To inspect the identities being sent, use an Assurance session: pass its session ID in the x-adobe-aep-validation-token header, then open Edge Delivery to inspect the request payload and response. The CBE server-side sample places identityMap inside event.xdm https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/code-based-experience/configure-code-based-channel/code-based-implementation-samples https://experienceleague.adobe.com/en/docs/experience-platform/assurance/view/edge-delivery

On eventType: for a fetch-only server-side CBE request, the Adobe sample uses event.xdm.eventType: "decisioning.propositionFetch". So I'd use that value here. The general Edge /interact endpoint accepts events; the AJO CBE sample is the more specific reference for this use case. Use decisioning.propositionDisplay when the returned content is actually displayed, and decisioning.propositionInteract for a user interaction—those are separate tracking events. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/code-based-experience/configure-code-based-channel/code-based-implementation-samples https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/experienceevent

If you still don't see the identity in the dataset, first verify that the request's datastream ID is the one you're inspecting and that its Adobe Experience Platform service is configured with the expected Event Dataset. Then confirm the event is reaching AEP; Assurance helps separate a payload/identity issue from a dataset-routing or ingestion issue.