So what you can do, is use the mappings on the Adobe Target (Async) tag, and that will allow dynamic paramters to be sent, just like the static parameters are.
Here is a community article that explains nicely how to add a mapping:
The example they use is the DoubleClick Tag, but this can be applied to Target tag as well.
Above is an example of the mapping.
This is used in combination with the "Test and Target Content Modification" extension.
May I know what does Destination mean on above screen?
In my case, if custID is in Data Source e.g. a UDO then what would be the Destination? How to apply it as mbox parameter?
Destination is the name that you want to send across.
So in the example Page Name (js) is taken from the UDO (page_name) and sent across as u1.
For what you would like to achieve you would need source to be custId (js) (As in your data source) and the destination would also be custId.
That should be it. I would however recommend the following reading:
09-01-2016 07:33 AM - edited 09-01-2016 07:57 AM
Thanks! I've got my answer.
Btw, I have another message asking how to create / define mbox on event like mouse click, mouse over, document.ready() etc? Or run script like mboxcreate / mboxdefine when visitors trigger some event on my page?
Let me provide more background info related to the above questions. Actually, I have 30+ menu items on a page and each of them associate with a promotion box with a banner. I would like to trigger a mbox over there on every visitor's mouse over on each menu item. Because if I create 30+ mboxes at once on page load, the page loading speed would be very low. That's why I would like trying mouse over event handling to trigger each mbox creation.
Hope you could give me advise.