For example the Conversant Tag (Commission Junction) shows the following in the notes:
"This tag requires the E-Commerce Extension (_corder, _cprod, _cquan, _cprice). Use mapping to override E-Commerce Extension values for ITEM, AMT, QTY, DCNT. Map a value to DISCOUNT for order-level discount and an array to DCNT for product-level discounts
Currency will default to USD if no currency is set on the page."
Does this tell me there is an eCommerce variable already mapped to DISCOUNT? If so, how can I tell which?
Rey, you can see what the defaults are by looking at the e-commerce extension mappings itself. Be careful when making changes as they are globally scoped. If the tag needs a different value than what is mapped in the e-commerce extension you need to override that by mapping the value manually in the tag itself.
In the case of Conversant the DISCOUNT needs to be manually mapped as only AMT,QTY,DCNT are mapped via e-commerce extension.
If you have any questions feel free to reach out to your AM or me.
So, when I look at the mapping toolbox for Conversant the variable DISCOUNT is listed...but how would I know it is not already mapped and needs to be manually mapped? (just by the tag comments?) Sorry if I misunderstand your answer. Thanks Josh!
Unfortunately other than the tips there is not a visual indicator of what variables are populated by the e-commerce extension for a given tag at this time. I use the fire and investigate method myself. Then I map the missing elements.
Just an additional hint: in the mapping toolbox, if something is already set in the ecommerce extension, it usually says "(override _cxxx)" where _cxxx is one of the e-commerce variables e.g. "Product Discount (override _cpdisc)". Anything that does not say "override" usually means you must manually map this value if you wish to send it.
This is not always the case, but it's one way of checking. In this case, the wording tells you that DCNT is coming from the e-commerce extension, and you have the option to override it if you wish, but "DISCOUNT", as Josh said, must be manually mapped ("Map a value to DISCOUNT" infers that the tag does not do it automatically for you).
Check out our new Swift integration library for iOS, macOS, tvOS and watchOS: https://github.com/Tealium/tealium-swift with updated documentation https://community.tealiumiq.com/t5/Swift/tkb-p/swift.