1. One option is to include both of the classification in the values: so “Leggings” => “Trousers, tights”, “Jeggings” => “Jeans, Trousers, tights”, Tights => “tights”, “Pop Socks” => “socks, tights”, etc. Then when you run your report, you’ll need to do a search for all the different values of “tights” and then add them together (with the caveat that there may be some overlap in visits that you are basically ignoring).
3. If you ran the above classification you could create a segment where any value of “tights” in the classification causes that to be included in the segment. This solves the problem of deduplicating visits, but means you may end up with a large number of segments, which will be difficult to manage (but if you use Discover/Ad Hoc then it might make the reporting ok)
4. In the SEO world we want to ensure that there is only one version of every page, so we assign each object a primary classification for things like the url. So for example Leggings would only be trousers and not tights. A real world example of this was a retailer I worked with who had ‘womenswear’ and ‘lingerie’ as two different primary classifications and there were constant arguments over what counted in each section (are bikinis ‘womenswear’ or ‘lingerie’ for example). This means your classifications are easier, but you won’t get that nuance.
There are two other options I didn’t mention earlier:
5. Use a list evar to start with. These need to be enabled on your account – but if you wanted to you could pass through the comma separated values as part of the tag (this may have a cost associated with it). These work in the same way as normal evars, but pass through several values at once (so you would say list1=”leggings, tights”). There are limitation on what you can do with list evars though, so unless you are using them stand alone I wouldn’t recommend
6. Send each value you’d have as a separate server calls to an existing evar (you can send a secondary server call to Omniture on a page easily so that it doesn’t count as another page view – a bit like link tracking). You’d then tell Omniture that evar1=Leggings, evar2=trousers in one server call and evar1=Leggings, evar2=tights in another, so that you have both values of evar2 in your report.
I am trying to pull multiple tag values for 1 tag category into a single column in the SAINT export classification.
In your example above, ‘Leggings’ is the tag category and ‘Tights’ and ‘Trousers’ are the tag values. The classification doesn’t accept Tights, Trousers (comma-separated) in the Leggings column.
I have gone with #2 in your list above. But as you mentioned, this is inflexible, hard to keep updating when more tag values are added and will miss tag values if the classification is not updated.
Can you please suggest/explain some of the options?
The problems of the dashboards! They never quite do what you want them to do.
If I were you the first step I’d go for would be double checking whether it is a space issue or not by recreating one of the pages that doesn’t currently work in a new dashboard. If it still doesn’t work, it is probably a space issue and you may need to rethink back down to two columns (or put the unique’s in a different widget).
I’d also question a 30 page report – too many metrics mean people forget about what is important (think frameworks and KPIs!).
I’m assuming you mean you want to make the value in the report equivalent to more than one value in another report (eg leggings could be both trousers and tights, so you might want to classify it against both).
Currently you can’t do this with a standard variable. If you wanted to do this you could do a couple of things:
1. Put them in as comma separated and then you when you want to see “tights” you’ll need to add up “tights”, “tights, trousers” and any other variation
2. Create a “tights” classification (the values of which are ‘yes’ and ‘no’ – this isn’t ideal if there are numerous versions like this – but you can do through autoclassification if you have already put them in as a comma separated list)
3. Use segments for the breakdowns (managing this can be a pain, but at least you aren’t as limited as you are with classifications)
4. Use the primary classification and ignore any secondary ones
Hope that helps!
Everything looks great in SiteCatalyst but when I download the report to have the PDF version — it cuts out the uniques from the pages with 3 columns (the two columns are fine).
It still shows there is blank space for the unique numbers to fit next to Page Views so I don’t think that’s the problem of not having enough space.
I’ve tried this twice and stumped as to how to get the uniques to download on the 3 column pages of the report.
Do you know anything I could possibly do to fix this?
Anyone knows why when I receive visits from utm_campaign and visitors buy, I have zero in revenues from that visits?
Any suggestions would be really appreciated.
1) Online Store > Themes > … > Edit HTML/CSS > theme.liquid > place immediately after the opening tag
2) Settings > Checkout > Additional Content and Scripts > Paste above other scripts (i.e Facebook Pixel and AdWords Conversions Tracking)]]>
It turns out that I worked out a few ways to get the analytics insight either through using GA and the universal tracking (which I learnt from you) or using GTM by embedding the script in the GA ‘extra scripts’. Check out my notes at the bottom of that page.]]>