Perhaps. You will want to qualify (enter) in the activity on one mbox call and then convert (success) on another so that you are not double counting the entry. Adobe Target will take care of the (visitor, visit, impression) on the initial (entry) call. After that first call, Adobe has all the data it needs to populate the first column. Now, in order for the second column to get data, it needs to see traffic for your conversion metric. It will only count those if it knows that someone is already in the activity in order to keep the numbers clean. That is where the session comes in. Sessions have no expiry time for AB activities and 20-30 minutes for AP activities. It keeps a record of everyone who is in the activity so it knows how to convert. For example:
An activity with 3 offers (A, B, C) that has an entry mbox of mbox-entry and a success of mbox-success.
Call with mbox-entry and session 1234 => returns offer b
Adobe Target will remember the combination of that session and which offer it brought back (b). It will now increment visitor, visit, and impression.
Call with mbox-success and session 1234
Adobe Target knows the session and gives credit to offer b.
Call with mbox-success and session 1234asdakdfadlkfj
Nothing will happen in Adobe Target. It does not recognize the session.
thirdPartyId and tntId come into play when you start talking about the profile for the user and qualifying for certain activities/offers.
Hi Eric,
Thank for the detailed explanation. Do I need call the 'OrderConfirmationPage' mbox in order confirm page?
Thanks,
Hariharan S