Change setting in Portal snowplow file
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- analytics
Research direction
Locate the portal's assets/snowplow.js file and inspect the collector setting shown in the issue. Change the collector value from spm.apps.gov.bc.ca to spt.apps.gov.bc.ca, then verify the file serves the expected value at the provided portal URL.
Written by the indexing model from the issue text.
Description
Describe the Bug
It looks like there’s a small error in the tracking setup on https://portal.alc.gov.bc.ca/login
In the Javascript tracking code, the site is set to send tracking data to our Dev/Test data pipeline (which doesn’t feed into dashboards).
This setting is made in the https://portal.alc.gov.bc.ca/assets/snowplow.js file with this line:
var collector = "spm.apps.gov.bc.ca";
If you can get your developer to change that to
var collector = "spt.apps.gov.bc.ca";
(changing “spm” to “spt”), I believe tracking should start working as expected.
Expected Behaviour
var collector = "spt.apps.gov.bc.ca";
Actual Behaviour
var collector = "spm.apps.gov.bc.ca";
** Steps To Reproduce**
Steps to reproduce the behaviour -> go to https://portal.alc.gov.bc.ca/assets/snowplow.js file
** Additional context**
Snowplow helps us track analytics between the Portal and the ALC website so we can understand how people use the two sites in conjunction.
Confirm this task meets our team Definition of Ready (DoR) before moving to the Next Sprint column.
Confirm this task meets our team Definition of Done (DoD) before moving to the Done column.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 0
- Avg merge
- 21h 40m
- Merged PRs (30d)
- 27
Contributor guide
No contributing guide indexed for this repository
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.
More from bcgov/alcs
-
Task
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Task
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Deploy test to prod OpenTask
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100