In AJO, do we have any location where the contextual data coming from API triggered Campaign is stored?

​@ap95 

No, AJO doesn't store the contextual payload anywhere, it's used at runtime to render the message, then discarded. Not in Profile, not in any system dataset.

You can try an approach - log the payload yourself when you call the trigger API — stream it to a separate AEP dataset or your own DB, tagged with messageId/journeyId.

Hi ​@ap95 ,

For an AJO API-triggered campaign, contextual attributes passed in the REST API payload can be used for message personalization during execution, for example with:

{{context.attributeName}}

However, Adobe documents that this contextual data is used for the one-off communication and is not stored against the Real-Time Customer Profile. Therefore, you should not expect to find the original contextual payload in the AJO Interactive Messaging Profile Dataset.

If the payload must be retained for auditing, troubleshooting, or reporting, the source application should separately persist it—for example, by writing a copy to an application audit store or ingesting it into a custom AEP dataset. The API-triggered campaign does not automatically act as a payload-audit repository.

One distinction: an API-triggered campaign is different from a journey-triggering event. Journey event storage and dataset configuration should be evaluated separately if the implementation is actually using a journey.