Hey Sebastian. You just manually type in your destination with a prefix of "c." after you select the data source, so if you wanted to create a context data variable called c.purchase you'd just type in:
The rest is done via processing rules.
c.purchase = purchaseType ? purchaseType.substring(0,3) : 'n_a';
What would you recommend doing for the mobile app tag to get the same output?
Hi Sebastian, talking it over with Jared, we're not sure exactly where purchaseType is coming from. Plugins typically are only for standard website use, they aren't really a part of mobile app deployments of the AppMeasurement mobile SDK. You may want to contact your account manager for us to get to the specifics of your use case.
For some reason my SiteCat tag will send eVars and props but, with these instructions, will not send context data variables. Am I correct in thinking that context data variables can be used for non-mobile purposes? What could be going wrong? Writing an extension like s.contextData['foo'] = 'bar' does get the tag to send context data. Please advise.
The 'c._____' naming convention being referred to here by Sebastian and me is using the Mobile App version of the AppMeasurement tag, which does not have an "H" version. You're using the desktop version of the SiteCatalyst tag and the rules for that are slightly different. Are you trying to do context vars for a desktop/mobile website?
Ok. thank you for answering. that is what I suspected. I am trying to do context data variables on a desktop website (for a few reasons) and presume Tealium has a solution for this other than for me to write "s.contextData['foo'] = b.data_layer_element" for each event/eVar. But I could not find anything on how to do this except this post.