According to the instructions to map a variable to an eVar greater than eVar75 I'm supposed to map to contextData.myVar replacing myVar with eVar79 So, I mapped the UDO variable to contextData.eVar79, but it doesn't work. Nothing is passed in the beacon.
Good morning @steve_sherwood. Which instructions are you following? Perhaps it's time for an update to that documentation. Thank you and I look forward to your reply.
04-01-2016 10:18 AM - edited 04-01-2016 11:35 AM
You'll want to map to something like contextData.pagename or contextData.productcolor rather than contextData.eVar79. Then in the Processing Rules area of Adobe Analytics UI, you can associate "pagename", "productcolor", or whatever your variable name is with eVar79.
Bringing this up again. I have utag_data.webpush collecting the data. Now I want to map webpush to eVar79, so in the data mapping UI, I selected webpush and added a custom mapping, eVar79. It is not being picked up by SiteCatalyst
Good morning @steve_sherwood. Does this post answer your question:
Let me know. I look forward to your reply.
08-15-2016 09:25 AM - edited 08-15-2016 09:25 AM
Hello @bjoern_koth. You will need to speak to your account manager @Anonymous for further assistance. She should be in contact with you soon regarding your evars above 75 issue. Thank you!
Using the contextData mappings requires the Adobe Analytics tag to use the H.code v27 or to migrate to the new Adobe Analytics AppMeasurement for JS tag. Although you will see the option for contextData in the mappings toolbox you won't be able to make use of this if you are using an older version of H.code.