Store Transactional event data

Hi @dharsanprakash 
✅ Possible Approaches to Capture Customer ID via Transactional Events in Adobe Campaign Standard
1. Use a Workflow to Map Event Data and Trigger Dispatch
• Ingest your Transactional Event (containing Customer ID) into a workflow.
• Map the Customer ID to a profile or a custom schema within the workflow.
• Trigger a delivery (e.g., email or transactional message). The system will automatically log the interaction in broadLog under the dispatched message.
✅ Benefit: You leverage ACS's default logging mechanism without direct writes.

2. Create a Custom Schema for Event Tracking
• Design a dedicated schema to store your Transactional Event information (e.g., Customer ID, timestamp, event metadata).
• Ingest or enrich this schema via a workflow when the event occurs.
• Use this custom schema for downstream reporting, orchestration, or profile enrichment.
✅ Benefit: Offers full control over the event payload and enhances data visibility outside of broadLog.

3. Use Workflow Enrichment Instead of Direct Mapping
• Capture the event input in your workflow, and enrich the existing profile or identify the target segment.
• Use target mapping to align the enriched profile data for subsequent messaging journeys.
• Once the message is dispatched, ACS logs the event in broadLog automatically, tied back to the Customer ID used during targeting.

✅ Benefit: You still indirectly associate the event with broadLog without needing to write directly to it.

Why Direct Writes via Target Mapping Won’t Work
broadLog is read-only in ACS; writing directly via API or target mapping isn’t supported.

Target mappings are designed for message personalization and dynamic audience resolution — not for logging or persisting event data.Workflows are the only supported mechanism for injecting, enriching, and orchestrating event data while leveraging ACS logging.