Transactional Email with Freetext data

[Mert_AliEr]

Hello ACS professionals,

I need to send a transactional email that includes product details. The landing page is hosted outside of Adobe Campaign Standard (ACS), and the information is passed through an external API. When a user fills out a form containing product details such as the product name, code, etc., I need to send a confirmation email that includes the product information. However, I am unable to map the product details into the transactional email because they are not recognized as dynamic fields, even though I have added these fields to the Data Structure section in the Event Configuration.

How can I do this?

Email details are like this:

Your Product Details

Product type:

Product name: 

Model/Product code: 

Date of purchase: 

[SatheeskannaK]

@Mert_AliEr Fields added to the data structure should be available in the email template via personalization.

https://experienceleague.adobe.com/en/docs/campaign-standard/using/communication-channels/transactio...

If the transactional event involves product purchase details such as item, quantity, price, etc., consider setting up collections.

https://experienceleague.adobe.com/en/docs/campaign-standard/using/communication-channels/transactio...

[Mert_AliEr]

Thank you for your response Sathees,

I've used collections and I'm able to see the fields in the transactional email but the values(Product type, Product name, Model/Product code, Date of purchase) are not populated into the email somehow when I test the email. I tried mapping them but it's not working. 

Or I'm not sure how to map them correctly as they are not defined inside ACS.

• Product type: registration_type = -name-
• Product name: registration_product = -name-
• Model/Product code: registration_productcode = xyz
• Date of purchase: registration_date = timestamp dd/mm/yyyy

[Sukrity_Wadhwa]

Hi @SatheeskannaK,

Can you please help @Mert_AliEr further with their query?

Thanks!

[Thanongdach]

@Mert_AliEr 
Step Check and Fix it: 
1. Event Configuration : 
Check that all product-related fields (e.g., productName, productCode, price) are properly added in the Event Configuration → Data Structure.
2. Check JSON Payload for send to Event 
Make sure the JSON payload you send matches the Event Configuration exactly. Field names must match.
"json

{
"email": "user@example.com",
"productName": "Example Product",
"productCode": "ABC123",
"price": "299.00"
}"
3. Test Event
Use the “Test Event” function to simulate sending your payload and confirm if ACS accepts and maps the fields correctly.
4.  Check Dynamic Field in email template 
In your transactional email template, make sure the personalization syntax matches exactly:
"html
<p>Thank you for your order</p>
<p>Product: {{ event.productName }}</p>
<p>Code: {{ event.productCode }}</p>
<p>Price: ${{ event.price }}</p>"
5.  Check already to Publish Event . 
Always publish your Event Configuration after any updates. New fields won’t be recognized unless the configuration is published.
6.  Check Log and Error Messages 
After sending the actual Event, check the logs for errors or warnings to confirm that the event was triggered and processed correctly.