How do I map a UDO variable to a SiteCatalyst eVar greater than 75.

[steve_sherwood]

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.

[kathleen_jo]

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. 

[steve_sherwood]

These are the instructions that show up when you are mapping variables in the tag for Site Catalyst

[adam_wolfers]

Hi @steve_sherwood,

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.

[steve_sherwood]

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

[steve_sherwood]

I notice that Tealium did set s.eVar79 = utag_data.webpush, but it did not track the eVar.  Seems like the trackVars step was not done.

[kathleen_jo]

Good morning @steve_sherwood. Does this post answer your question:

https://community.tealiumiq.com/t5/DataAccess/Adobe-Analytics-Omniture-eVars-above-75-are-not-popula...

Let me know. I look forward to your reply. 

[kathleen_jo]

Hello again @steve_sherwood. I have asked your account manager @tony_paster for some assistance. He should be in contact with you shortly. 

[bjoern_koth]

Hi @steve_sherwood,

cannot see any instructions. Do you have a working answer for your problem?

[kathleen_jo]

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!

[bjoern_koth]

thanks, @kathleen_jo, will do.

[simon_browning]

Hi @steve_sherwood @bjoern_koth

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.

[bjoern_koth]

Hi @simon_browning,

thanks, do you know is this context data approach a temporary workaround, i.e. will future versions of this tag allow direct mapping to eVars > 75?

Thanks,

Björn