Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

4 tips for agile analytics: Implementation and tagging

Ashley Kibler, AT Internet Copywriter, with participation from Florian Rieupet, AT Internet Product Manager | March 2, 2016
Ashley Kibler and Florian Rieupet of AT Internet talk about how companies can take an agile approach to analytics implementations to make tagging quicker and simpler.

This vendor-written piece has been edited by Executive Networks Media to eliminate product promotion, but readers should note it will likely favour the submitter's approach.

More than just a business buzzword, "Agile" methodology and principles have made their way into many companies' operations, extending beyond the realm of software development and into marketing, sales, and business development activities.

Whether you're a strict practitioner of "Agile" methods, or are simply inspired to incorporate some agility into your processes for greater flexibility and productivity, you can apply agile principles to your digital analytics initiatives.

The implementation and tagging phase of your digital analytics project can benefit particularly well from an agile approach. Why?

Implementing a digital analytics solution is often long and tedious, due to the sheer volume of elements to be tagged. Add to that the fact that this operation must be repeated for your different platforms and properties. (Congratulations, you've tagged your website! But those iOS, Android and Windows apps won't all tag themselves. Get back to work!) And, of course, as your business needs and KPIs evolve, your digital analytics tagging must adapt as well.

In a nutshell, implementing your analytics tagging is crucial yet time-consuming... and never-ending.

The good news? Agile analytics can help you make tagging quicker and simpler, leaving you more time and flexibility to continuously iterate and improve.

Here are 4 tips on incorporating an agile approach to your analytics implementations:

 

1.     Set a restricted tagging scope

Resist the temptation to tag everything. In agile analytics mode, you should reduce your scope and tag only what really matters to your performance goals. Not only will you lighten your load of tagging work now, you'll also avoid being inundated later with masses of data you won't use or need. To know "what really matters", always refer back to your KPIs and use those as a guide. Decide what must be implemented at the very minimum to obtain this information, and focus on that. 

 

2.     Work incrementally

This may sound surprising, but you don't need to wait to have everything tagged before you can work with your data. In agile analytics, it's advisable to break your implementation down into several incremental phases, and start exploiting your data right away. Don't wait until your tagging plan is fully implemented to start analysing your data. If you want to measure page performance, for example, you can start analysing your visit data, even if you haven't yet tagged clicks or social media shares. Or perhaps you'd prefer to work incrementally by page priority, first focusing on your homepage, and moving on to medium- and lower-priority pages in subsequent phases.

 

3.     Work iteratively 

Your tagging is never set in stone. And you wouldn't want it to be! Just like any other agile project, agile analytics means studying your needs, defining your tagging plan, implementing it, testing it, and deploying the next (improved) iteration. Count on adding, deleting, and changing things in your tagging as you go.

 

1  2  Next Page 

Sign up for CIO Asia eNewsletters.