Closed dneel-bah closed 4 years ago
Testing instructions for AC#2 in Chrome
Navigate to either page for A or B
Open Dev Tools
Go to Sources tab
In the Page section, navigate to top/"webpack://"/./src/applications/edu-benefits/10203/
and click on analytics-functions.js
Put a breakpoint on line 39, this should be last line of exitApplication
function
Click "Exit Application", breakpoint should be hit
In console type window.dataLayer
and hit enter
Observe event is present
Note: after leaving a form, window.dataLayer
is cleared so this is how to check event is added
In staging. Closing story.
As a developer, I need to add additional Google Analytics tracking to the STEM 10203 so that adjustments can be made to the form based on user behavior.
Assumptions:
Acceptance Criteria:
The
edu-eligibilty-criteria-months-remaining-for-use
event is replaced withedu-eligibility-criteria-months-remaining-for-use
. (Note: Typo (missing second "i" in eligibility)The event
cta-primary-button-click
is triggered on each "Exit Application" button: a./education/other-va-education-benefits/stem-scholarship/apply-for-scholarship-form-22-10203/benefits/initial-confirm-eligibility
b./education/other-va-education-benefits/stem-scholarship/apply-for-scholarship-form-22-10203/benefits/confirm-eligibility
The unnecessary firing of event
cta-primary-button-click
is removed. (Note: There looks to be a one-offcta-primary-button-click
event firing occasionally upon continuing frombenefits/stem-eligibility
to/benefits/confirm-eligibility
and/benefits/eligibility
to/benefits/initial-confirm-eligibility
we will want to remove. Theedu-stem-scholarship-ineligibility-alert
andedu-form-change
events are perfect here and we will be able to determine those who continue / move back using page URLs.)The ineligibility alert is tracked on
/benefits/initial-confirm-eligibility
using the following event:Supporting Artifacts:
For AC1:
For AC2:
Notes:
cc: @bsmartin-ep and @bmcgrady-ep for visibility