DavidWells / DavidWells/analytics
__anon_id purpose
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
Hi @DavidWells and thank you for this project.
We are currently integrating this tool in a project. But to acomplish legal requirements (RGPD) we need to explain, and offer opt-in/out, any data stored in the browser. Then,
whats the purpose of __anon_id stored in localStorage?
why is setted once Analytics is initialized? (even with all plugins disabled)
We have used a plain basic config:
{
app: 'gestio-emocional',
debug: false,
plugins: {
// google-analytics...
// google-analytics-v3...
},
}
Our first strike is to initialize Analytics ASAP and enable plugins after user consent, but maybe we have to delay Analytics initialization after user consent.
Thank you.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by tracing Analytics initialization to find where __anon_id is created and what data it stores, then check how plugin-disabled and consent-related flows behave. Done means the purpose, initialization timing, and opt-in/out implications are documented or covered by a clearly scoped change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- analytics
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100