Enriching Event Data via Event Forwarding and External API Calls

[shamir_duran]

Hi,

For a project, we’re exploring whether it’s possible to send an event using the Edge Network Interactive Endpoint and leverage that event data in AJO-D (Adobe Journey Optimizer Decisioning) to create offer items (in JSON format) for server-side content personalization. So far, we’ve confirmed that this is feasible.

Now, based on the event data, we need to make a call to an external API to retrieve additional data that can then be used in the AJO-D offer item. We’re aware that ideally this data should be fetched before the event is sent, so the payload already includes all necessary information. However, we’re exploring the possibility of handling everything in a single request through Event Forwarding.

We understand that Event Forwarding can make GET requests to external APIs and store the response. We’ve successfully fetched the required data, which is available at the following path within Event Forwarding:
arc.ruleStash["adobe-cloud-connector"].responses.apiResponse.

We also have access to the event data through arc.event.xdm.... However, we’re unable to use this combined data directly in AJO-D, and we’re not sure how to send it to an AEP dataset.

Is there a way to use this enriched data and insert it into the event dataset?
Alternatively, is there a way to make the apiResponse data available within AJO-D (Adobe Journey Optimizer Decisioning)?

Thanks in advance for your help.

[KumarRishii · Accepted solution]

You can send the enriched data to an AEP dataset by using the Streaming Ingestion API from Event Forwarding.

- Combine arc.event.xdm and apiResponse into one payload.
- POST to AEP with required headers (x-api-key, x-dataset-id, etc.).
- Ensure payload matches the dataset's schema.

Once in the dataset, AJO-D can access the data for offer decisions.

Alternatives:
Update Profile API: If enrichment is profile-based, patch Real-Time Customer Profile.
Pre-fetch API data before sending the event (if feasible).

[shamir_duran]

Hi Humar,

Thanks for your response.

This was one of my concerns, that the only way would be through an API call, because the event that triggers all of this uses the edge network interact endpoint (realtime). So, when making another call to this endpoint or to the profile one, I'm not sure if there will be enough time for the information to be available so that, in the first request, based on the specified placements, the selected AJO-D offers are returned according to the decision criteria.

I'll give it a try, thanks.

[KumarRishii]

@shamir_duran Let us know if the solution above worked for you! If it helped, marking the response as correct can guide others with the same question. And if you found a different

solution, please share it — your experience could be valuable to the community.