P3
Please write the Locale and the Default Browser to an <evar> instead of to <products>. Contact Lauren Zuravleff for two evar numbers when you're ready to implement this.
So instead of <products> ;jre|1603,;s4|-130;;;event7=1,;s8|-132;;;event7=1,;s200|3082;;;event7=1,;s100|2;;;event7=1</products>
the call to Omniture would look like:
<products;jre|1603,;s4|-130;;;event7=1,;s8|-132;;;event7=1</products>
<evarX>2</evarX>
<evarY>3082</evarY>
where evarX is the Default Broswer and evarY is the Locale.
<products> just include the products, like a JRE installation or a sponsor, not attributes of products or installer's computers. Locale and Default Broswer are attributes of the installer's computer.
We use evars (Custom Conversion Variables) to store attributes so that we can do correlations. For example, how many people from the US with the locale set as English got the latest version of the JRE and the Microsoft toolbar? With Products and locale in the <products> string, it is impossible to complete this query without using the back-end Data Warehouse which will take a while to return.
Not only does it make it more difficult to do a correlation, but it also makes it difficult to use the Products Tag. The Products Tag includes everything that we send in <products></products>. It has a 100 character limit. Here's some examples of Products Tag:
;jre|0,;s8|-132;;;206=1,;s4|0;;;206=1
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1,;s4|-129;
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1,;s4|-1;;;
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1,;s4|0;;;2
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s4|-125;;;206=1,;s10|-125;;;206=1
The 206=1 represents the event7=1 (sponsor complete). If you look at this string, the locale (s200|1033;;;206=1,;) takes 19 characters of the 100 available. And Default Broswer takes 16 characters of the 100 available. (Though these aren't typically both in the string.) This often pushes the Products Tag over the 100 character limit. Several of the Products Tags above are truncated because they're more than 100 characters. So if I want to do a query to see how many times the Microsoft toolbar wasn't offered and the Yahoo toolbar was then offered, I may not get all the data because it will be truncated.
More explanation at:
https://confluence.sfbay.sun.com:8443/confluence/display/dotsun/InstallStatProducts
So instead of <products> ;jre|1603,;s4|-130;;;event7=1,;s8|-132;;;event7=1,;s200|3082;;;event7=1,;s100|2;;;event7=1</products>
the call to Omniture would look like:
<products;jre|1603,;s4|-130;;;event7=1,;s8|-132;;;event7=1</products>
<evarX>2</evarX>
<evarY>3082</evarY>
where evarX is the Default Broswer and evarY is the Locale.
<products> just include the products, like a JRE installation or a sponsor, not attributes of products or installer's computers. Locale and Default Broswer are attributes of the installer's computer.
We use evars (Custom Conversion Variables) to store attributes so that we can do correlations. For example, how many people from the US with the locale set as English got the latest version of the JRE and the Microsoft toolbar? With Products and locale in the <products> string, it is impossible to complete this query without using the back-end Data Warehouse which will take a while to return.
Not only does it make it more difficult to do a correlation, but it also makes it difficult to use the Products Tag. The Products Tag includes everything that we send in <products></products>. It has a 100 character limit. Here's some examples of Products Tag:
;jre|0,;s8|-132;;;206=1,;s4|0;;;206=1
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1,;s4|-129;
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1,;s4|-1;;;
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s10|-125;;;206=1,;s7|-125;;;206=1,;s4|0;;;2
;jre|0,;s8|-132;;;206=1,;s6|-130;;;206=1,;s200|1033;;;206=1,;s4|-125;;;206=1,;s10|-125;;;206=1
The 206=1 represents the event7=1 (sponsor complete). If you look at this string, the locale (s200|1033;;;206=1,;) takes 19 characters of the 100 available. And Default Broswer takes 16 characters of the 100 available. (Though these aren't typically both in the string.) This often pushes the Products Tag over the 100 character limit. Several of the Products Tags above are truncated because they're more than 100 characters. So if I want to do a query to see how many times the Microsoft toolbar wasn't offered and the Yahoo toolbar was then offered, I may not get all the data because it will be truncated.
More explanation at:
https://confluence.sfbay.sun.com:8443/confluence/display/dotsun/InstallStatProducts