Modify the template to add analytics to all extension docs....

chrome/common/extensions/docs/npapi.html

Index: chrome/common/extensions/docs/npapi.html
===================================================================
--- chrome/common/extensions/docs/npapi.html	(revision 26784)
+++ chrome/common/extensions/docs/npapi.html	(working copy)
@@ -199,7 +199,7 @@
 Leveraging HTML and JavaScript
 makes developing new extensions really easy,
 but what if you have existing legacy or proprietary code
-that you want to reuse in your extension? 
+that you want to reuse in your extension?
 You can bundle an NPAPI plugin with your extension,
 allowing you to call into native binary code from JavaScript.
 </p>
@@ -218,11 +218,11 @@
 </p>
 
 <ol>
-  <li> 
+  <li>
     Add a section to your extension's <code>manifest.json</code>
     that describes where to find the plugin,
     along with other properties about it:
-    
+
 <pre>{
   "name": "My extension",
   ...
@@ -241,7 +241,7 @@
     meaning only your extension can load the plugin.
     </p>
    </li>
-   
+
    <li>
      Create an HTML file that loads your plugin by mime-type.
      Assuming your mime-type is "application/x-my-extension":
@@ -416,6 +416,29 @@
   <p>
   ©2009 Google
   </p>
+
+<!-- begin analytics -->
+<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
+<script src="http://www.google-analytics.com/ga.js" type="text/javascript"></script>
+
+<script type="text/javascript">
+  // chrome doc tracking
+  try {
+    var engdocs = _gat._getTracker("YT-10763712-2");
+    engdocs._trackPageview();
+  } catch(err) {}
+
+  // code.google.com site-wide tracking
+  try {
+    _uacct="UA-18071-1";
+    _uanchor=1;
+    _uff=0;
+    urchinTracker();
+  }
+  catch(e) {/* urchinTracker not available. */}
+</script>
+<!-- end analytics -->
+
     </div> <!-- /pageFooter -->
   </div> <!-- /container -->
 </body></html>