- Date:
- 2008-03-20
- Revision:
- 60988
Abstract
Add Google Analytics context dependent to your Plone Site
Introduction
Google Analytics can cope with different URLs of a site, e.g. with http://plone.org and http://plone.org/products. So if you have a hierarchical structure of your site and you want to analyze it with Google Analytics, you need different ga-code-snippets per URL. With this package you can handle it.
Usage
There is a formlib form registered on the interface collective.gacontext.interfaces.IGAContextMarker. Each context which is marked with that Interface becomes Google Analytics aware. A new object tab is displayed where you can edit a ga-code-snippet.
A viewlet, registered for PortalFooter, will find the responsible code snippet for it. It calls a utility which walks the acquisition chain up for the next object which provides the IGAContextMarker Interface and returns its code snippet (if there is one set).
Example:
http://plone.org is marked with IGAContextMarker and has the following ga code:
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> <script type="text/javascript"> _uacct = "UA-00000-0"; urchinTracker(); </script>
http://plone.org/events will find the same code snippet:
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> <script type="text/javascript"> _uacct = "UA-00000-0"; urchinTracker(); </script>
If http://plone.org/events/conferences is marked with a IGAContextMarker and has the following ga code:
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> <script type="text/javascript"> _uacct = "UA-99999-9"; urchinTracker(); </script>
Then http://plone.org/events/conferences/2008-location-tbd will find the code snippet from http://plone.org/events/conferences:
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> <script type="text/javascript"> _uacct = "UA-99999-9"; urchinTracker(); </script>
vim: set ft=rst tw=75 nocin nosi ai sw=4 ts=4 expandtab spell spelllang=en:
Metadata
Release files for collective.gacontext 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.gacontext-0.2.1.tar.gz | 11.4 kB | Without provenance | Details for collective.gacontext-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.gacontext-0.2.1-py2.4.egg | Legacy Egg format | - | - | Details for collective.gacontext-0.2.1-py2.4.egg |
Total release size: 29.8 kB
Release files / collective.gacontext-0.2.1.tar.gz
| Download URL | collective.gacontext-0.2.1.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a343f00e93d1fb2b6de258115395769d6194a84877e4b639263b263eb0a16b12
|
|
BLAKE2b-256 checksum How to use checksums |
da9c259ce5331119d7bdd23f0b9caec8887a33830ed30136c9173fa328c93ebf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / collective.gacontext-0.2.1-py2.4.egg
| Download URL | collective.gacontext-0.2.1-py2.4.egg |
|---|---|
| Size | 18.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
11368ee01208dd01c2b4ebbd5d4836b50940d9248dc8187f5d1c41a3fb40d395
|
|
BLAKE2b-256 checksum How to use checksums |
adc736b70fe14d39807c50cf5544de7ee394967621ea758661d10fc3fa99059d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.gacontext 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.