Skip to content
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

DATA | dataLayer Improvements #1509

Closed
scottqueen-bixal opened this issue Jun 27, 2024 · 5 comments
Closed

DATA | dataLayer Improvements #1509

scottqueen-bixal opened this issue Jun 27, 2024 · 5 comments
Assignees

Comments

@scottqueen-bixal
Copy link
Collaborator

Domain

data

Related Issue(s)

Due: 7/5

New issues that arise from this task should be created using the Bug Report form.

Create a unique data layer value for the modal #1478
bf_page_change fires multiple times on inital page load #1468
Update pageView data layer variable to differentiate between form pages #1477
Create data layer event to track benefit link click #1467
Add data layer value to track benefit accordion open #1466

Description

Testing env: https://bf-cms-main.bxdev.net/benefit-finder/death

Please take some time to QA the above items ensuring that the event behavior is working as expected and confirm that you can use it with integrating tracking in GTM.

cc: @fongcindy, @EnriqueOrt

@nickpistone
Copy link
Collaborator

I'm getting a 404 error when I try this link: https://bf-cms-main.bxdev.net/benefit-finder/death.

@nickpistone
Copy link
Collaborator

I was able to test using https://bf-cms-dev.bxdev.net/benefit-finder/death instead of bf-cms-main. Testing in this environment, I found the following:

Confirmed:

@fongcindy
Copy link
Collaborator

Scott will sync with Nick to figure out the issue he's seeing on his end.

@scottqueen-bixal
Copy link
Collaborator Author

confirmed the 404 on main https://bf-cms-main.bxdev.net/benefit-finder/death, I'll reach out to DevOps to see what's going on with the main env.

@scottqueen-bixal
Copy link
Collaborator Author

I was able to test using https://bf-cms-dev.bxdev.net/benefit-finder/death instead of bf-cms-main. Testing in this environment, I found the following:

Confirmed:

Looks like all items are confirmed, and notes of additional work were requested after sprint34, and are being tracked in the current sprint 35 under the associated items

#1514

  • Benefit accordion event fires as expected, but request name change from benefit_click to benefit_accordion_open

#1516

because these two requests were done after the work in sprint34, you should expect that they will be part of the upcoming QA sprint.

@nickpistone if you agree, with the above - please confirm and mark this ticket as done.

CC: @fongcindy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants