For the sake of this post, we will again narrow the scope to
a singular GMI brand (Larabar), and create a measurement plan to gauge the
success of a new line of product known as Larabar Uber.
1.
Define the goal
a.
Our goal with the Larabar Uber website is to
“increase sales of the product by 25% by the end of FY 2013.”
b.
Define Success
i. Here,
success would be defined as an increase in sales of the Uber line of product –
increasing the overall market share of the product in the “health food bar
segment.”
1.
We can measure our drive toward “success” by
utilizing analytics tools, and measuring sales of the product through
larabar.com. Additionally, we could track other offline data like sales at
Wal-Mart or Target. Finally, we could measure metrics like unique visitors to
the Larabar Uber pages, or see if one flavors page is frequented more than
another.
2.
Identify Publics
i. Some of our potential publics for Larabar Uber
might be:
1.
Current Larabar Original buyers.
2.
Health
conscious consumers
3.
Those on a special diet (i.e. Gluten-free,
vegan, etc.)
3.
Define Benchmarks
a.
GMI could establish sales and market share
benchmarks to achieve this goal, such as:
i. Denote
every 5% sales increase
ii. Denote
every new retailer that agrees to carry the product.
iii. Denote
increased unique visitors to the larabar.com store.
4.
Determine KPI’s
a.
There are several KPI’s that GMI might consider
here, including:
i. Tracking
overall sales of Larabar Uber
ii. %
Increase in checkout rate at the larabar.com store.
iii. %
Increase in CV rates.
5.
Select a Tool
a.
I imagine we would use Adobe SiteCatalyst to
analyze these metrics, along with data from both SAP and other tools.
Overall, I think this would help formulate an effective
foundation for increases in both the general public awareness – and subsequently,
the sales – of Larabar Uber. By combining both our online and offline data, we
can develop a complete picture of our target audience(s), and ensure that
Larabar Uber is a major success for GMI.
I didn't realize that Larabar was part of GMI -- they might also consider people looking for a healthy snack or a quick breakfest/lunch. I know I've grabbed this type of protein bar for those purposes before. Nice job.
ReplyDeleteI haven't looked too much into Adobe SiteCatalyst. Is there something in particular that it does that something like Google Analytics doesn't do that you feel is a major advantage for an organization like GMI?
ReplyDeleteMike,
DeleteThere are two major reasons we use SC over Analytics:
1.) Local Control of our Dara -- With SC, we can use the servers in OUR datacenter to manage SC, with Analytics, everything is shipped off to some Google server somewhere in the world. For a company like GMI, this is unacceptable.
2.) Enterprise Scalability -- SC is scalable, and can meet the constant needs of the enterprise. Analytics can also do this, but with a more "cloud-like" infrastructure -- which isn't what most enterprises want.