Getting Help
We're here to help you get the most out of the Open Source Site Tracking platform. Whether you're just getting started or need advanced assistance, we have multiple ways to get support.
Our vibrant community is one of our greatest assets. Join thousands of users and developers who are passionate about open source analytics.
Community Channels
GitHub Discussions
Perfect for:
- General questions about the platform
- Sharing your experiences and use cases
- Getting feedback on your implementation
- Best practices and tips
Visit GitHub Discussions
Discord Server
Perfect for:
- Real-time help and support
- Technical discussions
- Meeting other users and developers
- Staying updated on new features
Join our Discord
Community Guidelines
Our Community Values
- Inclusive: Welcome to everyone, regardless of experience level
- Helpful: Be patient and supportive of others
- Respectful: Treat everyone with kindness and respect
- Collaborative: Work together to solve problems
- Constructive: Provide helpful, constructive feedback
Documentation
Our comprehensive documentation covers everything from getting started to advanced features:
Key Documentation Resources
Documentation Structure
Getting Started
- Installation and setup
- First project creation
- Adding tracking to your website
- Basic analytics overview
Advanced Features
- Advanced analytics
- Heat maps and user flows
- Form analytics
- Custom event tracking
Administration
- User management
- Team collaboration
- Security and permissions
- Integration options
Reporting Issues
When you encounter problems, we want to help you resolve them quickly. Here's how to report issues effectively:
Before Reporting
Troubleshooting Steps
- Check the FAQ for common solutions
- Search existing GitHub issues
- Check the documentation for relevant information
- Try reproducing the issue in a fresh environment
Creating an Issue
Issue Template
When creating a new issue, please include:
- Clear Title: Descriptive title of the issue
- Description: Detailed description of the problem
- Steps to Reproduce: How to reproduce the issue
- Expected Behavior: What you expected to happen
- Actual Behavior: What actually happened
- Environment: Your environment details
- Screenshots: Screenshots if applicable
Issue Types
- Bug Report: Something isn't working as expected
- Feature Request: Suggestion for new functionality
- Documentation: Issue with documentation
- Performance: Performance-related issues
- Security: Security vulnerabilities (please report privately)
Contributing
We welcome contributions from the community! Whether you're fixing bugs, adding features, or improving documentation, your help is appreciated.
Ways to Contribute
Code Contributions
- Fix bugs and issues
- Add new features
- Improve performance
- Enhance security
Documentation
- Improve existing documentation
- Add new guides and tutorials
- Translate documentation
- Fix typos and errors
Community Support
- Help others in discussions
- Answer questions
- Share your experiences
- Mentor new contributors
Getting Started Contributing
- Read the Contributing Guide
- Fork the repository on GitHub
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
Support Response Times
Our community support team aims to respond within:
- GitHub Discussions: 24-48 hours
- Discord: Real-time during business hours
- GitHub Issues: 48-72 hours
- Security Issues: Within 24 hours
Security Issues
If you discover a security vulnerability, please report it privately to:
Email: security@autobotsolutions.com
Please do not report security issues publicly in GitHub issues or discussions.
Thank You!
We appreciate your interest in the Open Source Site Tracking platform. Your feedback, contributions, and community participation help make this project better for everyone.
Together, we're building the best open source analytics platform!