gaCookies using potentially fragile mechanism

Open
#578 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
analytics

Research direction

Read src/js/tracker.js around line 1202 and the linked Google Analytics guidance for retrieving the client ID. Compare the current cookie handling with that method; the work is done when the context uses the intended GA data and the backwards-compatibility choice is resolved.

Written by the indexing model from the issue text.

Description

category:browser priority:low status:needs_triage type:enhancement

gaCookies just takes the entire Google Analytics cookie out and plugs it into a context.

GA provides a method and callback to do this properly. We should probably use this. Possibly keep both for backwards compatibility? This probably makes the modelling stage a bit easier too since there's more than just the client ID in there.

Dominant language
TypeScript
Stars
590
Forks
232
Avg merge
2h 22m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from snowplow/snowplow-javascript-tracker

All issues in snowplow/snowplow-javascript-tracker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.