-
Notifications
You must be signed in to change notification settings - Fork 302
How we measure
Digital.gov is a community of people in government that share the methods, practices, policies, and tools needed to deliver smart, effective digital services in the government.
Our focus is the craft of applying of digital technology in government, to solve problems and enable new possibilities.
Here is how we intend to measure what we're doing
We intend to measure the effectiveness of our brand on our community. When we speak, how many people listen?
- number of newsletters opened
- Visits via a tweet we sent
- Visits via a facebook post
- emails sent to a community
- direct visits Unique visitors
We would like to measure the effectiveness of our presence on the open web. How are we doing at being an available resource for people searching for information?
- indirect visits via Google etc...
- direct visits to digital.gov
Once on digital.gov, how many people took an additional action?
- searches on digital.gov
- pages printed
- pages shared (via share tools)
- pages emailed (via email-this button... coming soon)
- pages referenced in Slack
- pages referenced in a community
- asked a question about a page (to digital.gov inbox)
- submitted an edit/change/pull-request
- provided feedback via email
- discussed content of a page in a community
- total unique visitors
- total pages viewed
We are making changes to digital.gov to ensure that every blog post, resource page, event, video, and promo to other services and tools is properly tagged with our new "topics" taxonomy.
We provide a lot of information across a lot of different content types. In our research, we heard that people would like the information they need packaged as resources and guides and less in blog posts. However, we have a great deal of content in our blog posts. Having the content type available to us in the analytics would help us to make smarter decisions about which type of content we write, edit, and promote on digital.gov.
🎉Questions? Email [email protected]