-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add Visitor Count Feature Using Third-Party Analytics #47
Comments
Can you assign me this task ! |
Sure @melan-variya go ahead. ⭐ the repo and Happy Coding 😄 |
where do i need to show number of visitors , can you please provide me details . |
@melan-variya In the front page, it is up to you just make it according to theme. |
@melan-variya are you working on it ? If you face any difficulty do lemme know we will find solotion togather. |
I created pull request you can check . |
Hi @Ctoic, I am interested to work on this issue if it is still open please assign to me. |
Go ahead @Saiharitha3 |
Thank you @Ctoic will update to you soon! |
Description: We want to add a feature to track the number of visitors to the LisBook app. Since there is no backend or database involved, we will integrate a third-party analytics service, like Google Analytics, to handle visitor tracking. This will allow us to monitor user engagement, the number of visits, and other relevant statistics.
Tasks:
Research and choose a third-party analytics tool (e.g., Google Analytics, Simple Analytics, Plausible Analytics).
Set up an account with the chosen tool and get the tracking code.
Insert the tracking code in the section of the HTML files so it loads on all pages.
Test to ensure that visitor tracking works properly.
Document the changes in the README file, specifying how analytics have been implemented.
Acceptance Criteria:
Analytics tool is integrated successfully.
Visitor tracking data is accessible from the chosen third-party platform.
The code is well-documented, and any additional configuration steps are clearly explained in the README file.
The solution works on both desktop and mobile views.
The text was updated successfully, but these errors were encountered: