Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

As we're quickly taking off into 2023, our Adobe Target Product teams want to hear your top interest areas for learning opportunities and value realization with Adobe Target ~ to fill out the survey with your suggestions, experience, and feedback, follow the link to the right.

How to Implement "orderConfirmPage" mbox for Revenue Tracking with Web SDK Library


Level 3


We currently use at.js 2.x for our Target implementation. We are considering migrating to the Web SDK. As part of our current implementation, we have some fairly basic revenue/order confirmation tracking logic implemented using at.js (for Target reporting):{
"mbox": "orderConfirmPage",
"orderTotal": digitalData.itemArray.price,
"productPurchasedId": digitalData.itemArray.productId


How can this be implemented using Web SDK? I assume this is a fairly common use case, but I could not find anything in the documentation. I saw the "trackEvent" comparison here, but did not see any use case really comparable to the above.





Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies


Level 3


Is there a particular field in the XDM Schema you would have to map values to in order for the data to get properly forwarded to Target for reporting?


Level 3

Thanks, but unfortunately, I don't see the answer to my question there. I could be missing it, but I have read the documentation relating to at.js to Web SDK migration and understand the implementation overall. However, what I do not see is how specifically to replicate the example noted above.


The closest I saw to my issue is here:


However, that does not describe how to use replicate "trackEvent" when params (i.e. orderTotal) are required. Under the recommend "alloy.js" "sendEvent" approach, I do not see where one would pass such params in order for them to be properly ingested for Target reporting. I did not see anything relevant in the available field mappings here: