The analytics page is really interesting. Mostly because I am a nerd and I like instrumentation. But I have no experience using traffic analytics.
What are some action items that could derive from looking at the analytics page?
Right now, not much other than some general ideas on simple things, such as how oneās metrics such as veiws, downloads, and prints go up or down in general in a specified period, and which models provided the most reward points, etc.
When conversion rates are coming, they will provide more insights, particularly if some sort of benchmarks are also provided.
To my understanding, three conversion rates are coming, along with a new metric: # of impressions.
view rate: # of views / # of impressions
download rate: # of downloads / # of views
print rate: # of prints / # of views.
I have requested MW to provide the average of the above rates for each model subcategory so designers have context to understand their own rates. MW only said they would consider it. So donāt hold the breath for this benchmark yet 
1 Like
Excellent, thank you for the detailed reply! I spent a little bit more time poking around the Analytics page. It would indeed be great to have graphs for the rates you mention. It seems now we can only kind-of-nearly eyeball those metrics from the āUser Conversionā graph for each model and squinting hehe.
Speaking of which, I guess I canāt feel too bad about some of my models having little to no downloads. The number of views on new models is abysmal LOL.
That is one situation that the vew rate will provide more insight. Is the low veiw count the result of low impressions, meaning the model has been shown up on peopleās screen only a few times, or the result of low conversion, meaning the model has been shown many times, but it failed to attract enough people to click open the model page to take a look?
Another key piece of info is a benchmark. Letās say a designerās view rate is 5%. Is 5% a good rate? The designer has no way to know unless s/he knows whatās the average view rate for the subcategory the model is in. If the average is 2%, then having a 5% rate is not bad. But if the average is 9% then the model is not doing well in attracting people to click.
So with a benchmark number such as an average, the view rate becomes āactionableā, i.e. the info can be used to guide oneās actions to improve it.
The same goes to download rate and print rate, if the average rate is known, they will also becme actionable.
I hope MW considers the request to provide the average or some other benchmark number to help the analytics become actionable (useful).
1 Like