-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I second this!
Gael Pasgrimaud <[email protected]> writes: > On Fri, Jan 13, 2012 at 6:18 PM, Jonathan Vanasco <[email protected]> > wrote: >> >> I thought about the middleware route, but too much interaction needs >> to take place in the handlers/templates. I couldn't think of a good >> way to support this in the middleware, yet configure per-request. >> >> that library just drops in the standard "track pageview" call for a >> global account id. >> >> i needed to support a lot of the other functionality for two of my >> sites: >> - custom variables for performance analytics >> - event tracking for backend interaction / operations >> - ecommerce tracking >> - rolling up multiple domains into 1 reporting suite >> > > Looks powerful. But not really documented... :) > > You should add a few examples in a sphinx doc > >> >> >> On Jan 13, 9:16 am, Chris Rossi <[email protected]> wrote: >>> Maybe these aren't doing the same thing, but another approach is to write a >>> WSGI middleware ala Tres Seaver's repoze.urchin: >>> >>> http://pypi.python.org/pypi/repoze.urchin >>> >>> Chris >>> >>> On Fri, Jan 13, 2012 at 12:06 AM, Jonathan Vanasco >>> <[email protected]>wrote: >>> >>> >>> >>> >>> >>> >>> >>> > it's on github -- https://github.com/jvanasco/pyramid_gaq >>> >>> > it's fairly simple: >>> > - import it into helpers >>> > - in your base handler's __init__ call : gaq_setup( request, >>> > 'account_id' ) >>> > - set custom vars, events, etc, with commands that mimic the gaq >>> > commands - ie: _setCustomVar -> gaq _setCustomVar >>> > - you can print it out in a template via ${h.gaq_print()|n} >>> >>> > its fairly simple, but i found it necessary for a few reasons: >>> > - GA isn't documented well. there's lots of information, but you need >>> > to cross reference 5 API docs to figure out the 'correct' order to >>> > make the calls. gaq_print() does it automatically. >>> > - i needed to write the library for a site, so i could use >>> > setCustomVar in the handlers and have them print in the right place >>> >>> > i also coded one for pylons, which i tossed on 2 production sites >>> > today, that i'll toss up as well. >>> >>> > -- >>> > You received this message because you are subscribed to the Google Groups >>> > "pylons-discuss" group. >>> > To post to this group, send email to [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> >http://groups.google.com/group/pylons-discuss?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "pylons-discuss" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/pylons-discuss?hl=en. >> - -- Parnell "ixmatus" Springmeyer (http://ixmat.us) -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJPEHVJAAoJEPvtlbpI1POLSiMIAJl/qlKY2bDJ8z8tYoH25Bkl 0zwiAw+kwc8/nI/2AhXJvSQHEfyWCTEPudiWGh3p8cIyqCSCMmLyLc+XS8PKXSkv jSDZAlW0PXgkVN+sF8S1Y8uC8lJSYC7nQO4U+pxYz3AofaaLKjBA3KKZpxcRqUoM /ShEyBDRjqsDYeLa6hxARROc4w3M4wIKS8lta+gMyoIKKiSnIV1ngYQySCSw/G83 uCway3NlhtRRhg/47BE43ykfOzuJyASgRL9Hdagk/Ra0gdNa8Gb66j2KRyqgzLy5 IdMffVRKrTiD2EcXoVit4b3NvbIWfBrGhzhGeiR9nJcTTHHSiLxRj2uP77D1dhE= =wH3a -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
