Highlighted

How do I map 2 UDO variables into the same Adobe Site Catalyst eVar report?

Silver Contributor
Silver Contributor

I have two UDO variables for cart_typemini="mini" and cart_typestd="std". I want to map these into the same Adobe Site Catalyst eVar75 so they will display as two separate rows in the report. With the mapping below will the second UDO over-ride the first. Will this work or do I need to use an extension instead?
cart_typemini-->eVar75
cart_typestd--->eVar75

2 REPLIES 2
Highlighted

How do I map 2 UDO variables into the same Adobe Site Catalyst eVar report?

Tealium Employee

You are correct on the mappings, only one value is accepted. However, Adobe calls only accept one value per eVar/prop on a given network call, so you'll need to do one of two things to get around it:

 

1) Fire a separate utag.link/view event with the second item of data. So you might have the first call look something like so:

utag.link({ cart_typemini="mini" })


Then a second one that you call like so:

utag.link({ cart_typestd="std" })

 

2) Change the variable to be from eVar75 to a list variable. Then, instead of sending 1 value, you can send a list. Example:

 

list1 -> mini,std

 

However, since it appears you are reporting 2 different metrics here, it may be prudent to re-evaluate your actual business requirementsto see if it's possible to put these values into separate eVars.

Highlighted

How do I map 2 UDO variables into the same Adobe Site Catalyst eVar report?

Rookie Contributor

Hi @andre_molnar,

 

Another option to the above, if you're still wanting to use the same eVar would be set up a success event along side setting your eVar.

 

So eVar75 = "mini" and event75

 

When setting up your eVar, tell Adobe in the Admin Panel that it expires on seeing event75. 

Very similar to how the Purchase event works with an eVar set up to capture Order IDs on an ecommerce site.

 

That way when eVar75 is seen, it also sets event 75 and then resets the eVar.

List Vars are very scarce in Adobe SiteCat, so be very wise how and when you use them :-)

 

To be honest, I'd have to agree with the above and potentially re-think a different way of doing this

 

Thanks,

 

Tom