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
BedrockMission!

Learn More

View all

Sign in to view all badges

Order Confirmation Mbox - Add custom parameters??

Avatar

Avatar
Validate 1
Level 2
s_kala
Level 2

Likes

11 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
s_kala
Level 2

Likes

11 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
s_kala
Level 2

18-04-2018

Hi Guys,

I use Adobe Target on an e-commerce website. I am order confirmation mbox to get order details for a test. Currently, I am passing only three parameters (order id, order total & productPurchaseID) in the mbox as suggested in the documentation - Create an Order Confirmation mbox - at.js

I tried passing more than three parameters in the mbox but they do not show in the audit report or the API report.

Is there a way that I can add more than three parameters in this mbox like productName, productCategory and get them in the audit report or using the Target API?

Appreciate your help!

Regards,

Suchindra Kala

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 5
Level 4
russpainter
Level 4

Likes

49 likes

Total Posts

40 posts

Correct Reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile

Avatar
Boost 5
Level 4
russpainter
Level 4

Likes

49 likes

Total Posts

40 posts

Correct Reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile
russpainter
Level 4

18-04-2018

Nope. These are to only 3 fields that you can pass data to the Target DB, audit tables. Here is a couple hacks/work-arounds we used.

1. Pass more than one parameter in orderId and productPurchasedID. We've passed strings like this "12345677|abcsedee|dfdf123uejjs" into the orderId and then parsed them out on the DW end. ProductPurchaseId can be comma delimited and you could do the same thing once you pull them with an API you can parse them out on the backend.

2. Use A4T. If you are using Analytics setup the integration and pass events, variables or whatever data you need into the AA and report on those parameters in the AA UI or pull from the API.

Hope this helps. Adobe always gets a weird look on their face when I tell them I would love more parameters to collect data on a per mbox level. Target is also on Adobe I/O which is better and Adobe Analytics isn't quite there yet.

Russ

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1
Level 2
s_kala
Level 2

Likes

11 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
s_kala
Level 2

Likes

11 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
s_kala
Level 2

18-04-2018

This is really helpful. Thank you very much russpainter