-
Notifications
You must be signed in to change notification settings - Fork 23
Google Analytics
-
Create Analytics account:
- Your first step is to set up an Analytics account.
-
Create a new Google Analytics 4 property.
- In Admin, look at the Account column to make sure that you've selected the right account. Then, in the Property column, click Create Property then populate information of project
If you are developing in a dev environment, you must populate "www.localhost:4000" for the first field - Website Url and "https://localhost:4000" for the second field - Stream name.
Click Measurement Protocol API secrets to create API Secret Key.
In file clarin-dspace.cfg we need config 5 properties:
- rest.properties.exposed
- google.analytics.key
- google.analytics.buffer.limit
- google.analytics.cron
- google.analytics.api-secret
-
Property rest.properties.exposed
Declare property with value "google.analytics.key" so that Front end can get value of property from Back end. Example: rest.properties.exposed= google.analytics.key
-
Property google.analytics.key
We can get value of property from field MEASUREMENT ID Example: google.analytics.key=redacted
-
Property google.analytics.cron
Define cron for how frequently events tracked in the DSpace backend will be sent to Google Analytics. Keep in mind, changing the schedule requires rebooting your servlet container, e.g. Tomcat. Example: The below example will run this task daily, every 1 minutes google.analytics.cron = 0 0/1 * * * ?
-
Property google.analytics.buffer.limit
The max number of events held in the GA buffer (default: 256) Example: google.analytics.buffer.limit=256
-
Property google.analytics.api-secret
Defines a Measurement Protocol API Secret to be used to track interactions which occur outside of the user's browser. We can get value of property from Secret value Example: google.analytics.api-secret redacted
Getting Started
Features
- All Features — full categorised list
- CLARIN Licenses
- PIDs & Handles
- Featured Services / Refbox
- Field-Level Permissions
- File Previews
- Sharing a Submission
- Personal Access Tokens
- DOI Configuration per Community
- ROR Authority
Operations
- Kubernetes Deployment
- Samples (.env, Nginx)
- Nginx + Shibboleth
- Handle Server · Setup (v7)
- Shibboleth · DiscoJuice
- Shibboleth Accounts
- S3 Storage · CESNET S3
- Google Analytics
- Matomo
- Solr
- Logging
- Custom Namespace
- Health Report
For Users
Development
Reference
- Authorizations
- Metadata Info
- Citations (proposal)
- Repository Checklist
- Search, Browse & Filters
- Localization
- Importing Items (CLI)
- NFA Import - Steps
- OpenAIRE
- DOI Registration
- Inclusion in OLAC
- Unit Testing
- Deploy Checks
- Troubleshooting
- Versioning Theory
- Dynamic Resource Versioning
- Metashare Import · Schema
- Web Server Overview
- LINDAT Common Theme
- Workshop 2016 Results
- WebLicht Integration
- Google Dataset Search
Archive (v5 / stale)
- Old Home (v5)
- Installation (v5)
- Prerequisites (v5)
- Connecting Tomcat with Apache
- Using Apache
- Building Shibboleth FastCGI
- Shibboleth Install (v5)
- EUDAT Replication
- Backup (v5)
- Spring Social / Google Drive (v5)
- Clarin (→ Repository Checklist)
- Control Panel (v5)
- Overlays (v5)
- Configuration (v5)
- Speeding Up Downloads
- Debugging (v5)
- Selenium (v5)
- Code Contributions (v5)
- Best Practices (v5)
- Testing Hudson
- Working on Windows
- Prerequisites Checklist (v5)
- Migration to DSpace 7.2.1
- Upgrade From Lindat
- Piwik (→ Matomo) · Piwik Cleaning