Ingested JSON Payload Storage for API Triggered Transactional Campaign | Community
Skip to main content
H
HardikJa
Level 2
February 15, 2026
Solved

Ingested JSON Payload Storage for API Triggered Transactional Campaign

  • February 15, 2026
  • 2 replies
  • 4 views

I am in the process of migrating a transactional campaign from Salesforce Marketing Cloud (SFMC) to Adobe Journey Optimizer (AJO) as an API-triggered transactional campaign.

In SFMC, I can easily access all the JSON files used to trigger emails to customers via data extensions. These JSON files allow me to verify which customer received specific communications and cross-check the data in case of discrepancies. Additionally, I can conveniently filter profiles or emails based on order numbers to locate the corresponding JSON file used to trigger the email.

However, in AJO, the data received via an API for a transactional campaign is not stored. How can I verify and identify which customer received specific information in this scenario?

Best answer by Mayank_Gandhi

​@HardikJa 

For API‑triggered campaigns (Interactive Message Execution API):

  • The contextual JSON you send is used to render that one message and is not stored on the profile or in a system dataset. This is by design: fire‑and‑forget transactional/operational use cases.

    possible workarounds: 

  • Use Message Feedback to answer:
    • “Did customer X receive transactional campaign Y?”
    • “What was the status (sent, bounce, etc.) and when?”
  • Introduce an explicit logging layer for anything like orderNumber that you might need later:
    • either an AEP event dataset (Option A/B),
    • or an external archive (Option C),
    • ideally with a key (transactionId / messageExecutionID) that links log rows to AJO sends.

2 replies

Manoj_Kumar
Community Advisor
Manoj_KumarCommunity Advisor
Community Advisor
February 16, 2026

Hello ​@HardikJa AFAIK, the payload information is not store anywhere in AJO. It is used at runtime and discarded after that.

Manoj  | https://themartech.pro
    Mayank_Gandhi
    Adobe Employee
    Mayank_GandhiAdobe EmployeeAccepted solution
    Adobe Employee
    February 16, 2026

    ​@HardikJa 

    For API‑triggered campaigns (Interactive Message Execution API):

    • The contextual JSON you send is used to render that one message and is not stored on the profile or in a system dataset. This is by design: fire‑and‑forget transactional/operational use cases.

      possible workarounds: 

    • Use Message Feedback to answer:
      • “Did customer X receive transactional campaign Y?”
      • “What was the status (sent, bounce, etc.) and when?”
    • Introduce an explicit logging layer for anything like orderNumber that you might need later:
      • either an AEP event dataset (Option A/B),
      • or an external archive (Option C),
      • ideally with a key (transactionId / messageExecutionID) that links log rows to AJO sends.
      Terms & ConditionsAccessibility statement

      Loading footer...