Websites/Snippets/Impressions/Meetings/2012-01-11: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 24: Line 24:


=== Team Members ===
=== Team Members ===
* IT - cory shields
* WebDev: mkelly
* IT: cory shields
* Security: michael coates
* Security: michael coates
* QA: steven donner
* QA: steven donner
* Metrics: einspanger
* Metrics: einspanger


== Decisions  ==
* Ben will wait till mkelly is approaching having availability to schedule kick off meeting.
* Ben will contact IT/Sec/Qa/Metrics and let them know this is coming
* Ben will contact laura forrest along with anyone else relevant in engagement to discuss reporting wish-list
* Ben will find a firefox contact to sanity check this change to the about:home page


 
== Items To Become Requirements ==
 
* Because we are talking a sample size we must ensure that if the sample size changes historical data will be accurate
=== Chris More ''(Laura sent responses to questions via email pre-meeting)''<br> ===
* If server is down this must fail silently
 
*What have we done with snippets historically?
 
Here's a good [https://intranet.mozilla.org/Marketing/StartPageSnippets#Snippet_Program_Overview overview].
 
*What was successful and what wasn't?
 
Snippets are amazingly successful at upgrading users that are on old browser versions, telling people about new features, and providing qualified traffic to our engagement campaigns. Areas to improve: make them more compelling and interactive to better show users what Firefox can do, better tracking to understand CTR, rapid iteration. &nbsp;
 
*Where do we want to go?
 
In the immediate future see two projects above. Beyond that, keep developing the quality of content we show and get smarter about what we show, where, when, etc.
 
*How can we ensure clicks are tracked so we can measure the success of a campaign? (webtrends query strings)
 
Continue use of Webtrends query strings.
 
*Are there l10n considerations?
 
The strongest results often come from l10n-ized content. We should continue to translate and make it easy to batch load/import this content into the snippet service. More info [https://wiki.mozilla.org/L10n:Web_parts:Snippets here].
 
*Why are Google Analytic UTM tracking variable on the "About Mozilla" link when we use Webtrends?
 
Legacy - should be changed.
 
<br>


== Action Items ==
== Action Items ==


* Mike/Chris: Talk to WebDev and see who would be interested in being involved with the project.
* Fred will inform Ben of approximate date when mkelly will be available
* Laura: Create a more formal requirements document (managing snippets, HTML5 features to promote, analytic reporting, etc.)
* Ben will start meeting with relevant folks

Revision as of 00:25, 12 January 2012

This was an informal meeting to get Ben up to speed on this project.

Attendees

  • Fred Wenzel - Web Dev
  • Benjamin Sternthal - TPM
  • Chris More - Just Advising

Agenda

Review Scope

  • implement about:home js (webdev)
  • implement interface deciding which snippet to track (webdev)
  • implement tracking hardware (IT)
  • implement reports

Review Work Done Thus Far

https://bugzilla.mozilla.org/show_bug.cgi?id=690881 Other than some sample code, head scratching by mkelly nothing substantial

Project Size Estimate

  • webdev 2 (1-5)
  • IT 2 (1-5) however they have less time available

Team Members

  • WebDev: mkelly
  • IT: cory shields
  • Security: michael coates
  • QA: steven donner
  • Metrics: einspanger

Decisions

  • Ben will wait till mkelly is approaching having availability to schedule kick off meeting.
  • Ben will contact IT/Sec/Qa/Metrics and let them know this is coming
  • Ben will contact laura forrest along with anyone else relevant in engagement to discuss reporting wish-list
  • Ben will find a firefox contact to sanity check this change to the about:home page

Items To Become Requirements

  • Because we are talking a sample size we must ensure that if the sample size changes historical data will be accurate
  • If server is down this must fail silently

Action Items

  • Fred will inform Ben of approximate date when mkelly will be available
  • Ben will start meeting with relevant folks