Introduction
collective.jqganalytics uses the jQuery Google Analytics plugin to load Google Analytics asynchronously by default.
Custom Variables
Google Analytics tracking now provides for setting at most 5 user variables. These can be managed through the control panel in Plone under the ‘Google Analytics settings’ tab. There is no limit on the number of variables that can be set in the control panel since they can be disabled or optionally disabled using an expression. In the end though, the last one that is set for each slot is the one that will end up getting sent to Google for that slot. The name and value for the variables are both TALES expressions with the normal context variables (context,`here`,`request`, etc) available for use. For a complete list, see Products.CMFCore.Expression.createExprContext.
Attribution
Changelog
1.1.1 (2010-04-05)
Added Generic Setup import/export for custom variables
Switched javascript registry entry for the analytics code to safe encoding due to issues with full encoding
1.1 (2010-02-09)
Added site wide custom variables using expressions to fill them with dynamic content
Updated to a newer version of jquery.google-analytics.js plugin
1.0.1 (2010-02-02)
Bugfix for product available but not installed causing viewlet to render but crash
1.0 (2010-02-02)
Included jquery.google-analytics.js plugin
Viewlet for tracking page views
Configuration forms for Plone control panel
Generic setup export/import for account settings
2 maintainers
Metadata
2 maintainers
Release files for collective.jqganalytics 1.1.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 | |
|---|---|---|---|---|
| collective.jqganalytics-1.1.1.tar.gz | 17.6 kB | Without provenance | Details |
Release files / collective.jqganalytics-1.1.1.tar.gz
| Download URL | collective.jqganalytics-1.1.1.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
502d3aa46db628b52ebe9ee5ea4d4e454a34c1caa9cf8abd1fee4839d6391c4e
|
|
BLAKE2b-256 checksum How to use checksums |
91290e8d97946c615e62c6a231cdad1f0a952c448da25fa230aeadc45acf51cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.jqganalytics 1.1.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.
