Expand my Community achievements bar.

Join us for an upcoming in-person Adobe Target Skill Builders event ~~> We're hosting these live learning opportunities to equip you with the knowledge and skills to leverage Target successfully. Learn more to see if we'll be coming to a city near you!
SOLVED

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

Avatar

Level 4

Hello,

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):

 

 

adobe.target.trackEvent({
"mbox": "orderConfirmPage",
"params":{
"orderId": digitalData.itemArray.id,
"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.

 

Thanks.

 

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Level 4

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: https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/adobe-target/web-sd...

 

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: https://experienceleague.adobe.com/docs/experience-platform/sources/connectors/adobe-applications/ma...

View solution in original post

4 Replies

Avatar

Level 4

Thanks.

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?

Avatar

Correct answer by
Level 4

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: https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/adobe-target/web-sd...

 

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: https://experienceleague.adobe.com/docs/experience-platform/sources/connectors/adobe-applications/ma...