-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added google analytics tag #185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we put some guidance in the readme with how/where to access the analytics? I have never looked at something like this before.
Thanks @gigikenneth, to view the analytics is it as simple as just going to the analytics link that was emailed to us? |
Hi @manciniedoardo , exactly. After the pull request is merged, the numbers will go to Google Analytics and you can view it using the link you received. Other people can be added to Google Analytics as Viewers/Editors. If we want the numbers to be open and accessible to anyone, then we'd have to make a dashboard, but that's probably overkill since we're about to start. |
Happy to keep it as simple as possible, I don't think everyone needs access. |
Will we need a banner at the bottom informing the users about this, and asking for permission? |
hmmm: |
@StefanThoma , thank you for sharing, and yes, I agree we needed to ask for consent before proceeding. I'm looking at how we can do it in Quarto 👀 |
I just asked GPT again, looks like it's possible: |
- "express" consent so no tracking happens unless the blog visitors accept it. - simple and light banner at the bottom right - anonymizes IP addresses by default
Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the
main
branch until you have checked off each task.CICD.R
line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!tag(s)
or categories from the current list:c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Community", "Conferences", "Submissions", "Technical")
for your blog post. If you cannot find anything that fits your blog post, add your own tag! We occasionally tidy up alltags
for consistency.description
field at the top of the markdown document.This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)