Charlie (charbroiled) wrote in suggestions,

Provide usage statistics to LJ users via email

Provide usage statistics to LJ users via email

Short, concise description of the idea
Would an email that provided statistical information about the popularity of a given journal (or community) be helpful and motivating to LJ users?

Full description of the idea
Here is the format of a statistics email I receive from another community site. Would any of this information be valuable to LJ users? See this example: Hello USER, Here is your weekly statistical report on the journal XXXXX. HITS Your Live Journal page: xxx Average Ryze home page: xxxx* Average Ryze home page w/photo: xxxx* To increase your hits, add a photo on your homepage, at: link here. FRIENDS & GUESTS Friends you link to: xx Get the most VALUE by leveraging your Friends' Networks: Link here Friends linked to you: xx* Guestbook entries: xx Contacts: xx * These stats are only available in this e-mail. Is your time valuable? Enhance your networking efficiency with advanced features. PUBLIC EVENTS near you: MONDAY, June 23, 2003 Women's Career Networking Dinner Pittsburgh, PA Link here. NEWS This e-mail now only includes events near you. You can submit your events use this link NEWEST members with photos Member username - link Member username - link Member username - link Member username - link To become more popular, invite your friends to join: link here. Your page is at http://link Subscription Info If you'd prefer not to receive these Weekly Stats e-mails, please go to this URL:

An ordered list of benefits

  • Keeps users informed about journal usage
  • Reminds users to update their journals
  • Motivates users to contribute something of value
  • Could prompt a positive competitive environment

  • An ordered list of problems/issues involved

  • Requires the ability to mine web logs & database for traffic information.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • First, get approval to pilot this idea.
  • Second, determine the people and resources required to specify the effort that would be required to automate the mining of the usage information.
  • Third, discuss the feasability of implementation.
  • Fourth, survey a user group for feedback.
  • Fifth, develop a prototype and test.
  • Tags: ~ historical
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded