Purchase Event, Serialization and purchaseID in DTM
Something I've found to be a little less than intuitive, and even less documented, is how to properly fire the purchase event in DTM to get proper serialization. The UI in DTM allows you to fire the purchase event, but my question is this: How do I ensure the event is serialized in the same way it would be in a traditional JavaScript call? In other words, in JavaScript, I would fire the s.purchase event and then fire s.purchaseID=orderID.
My assumption is that if I were to serialize the purchase event in the DTM User Interface with %orderID% would not result in s.purchaseID receiving the same value. Is that correct? I know someone out there has done this before, it's just a matter of implementing the proper process.
Thanks in advance!
Jeff
