You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thekaveman opened this issue
Aug 18, 2022
· 0 comments
· Fixed by #873
Assignees
Labels
analyticsApp event tracking, instrumentation, logging: Metabase, AmplitudechoreChores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
Right now we send a page view event for the success view in enrollment. In Amplitude, we have a custom event for page view with path = /enrollment/success to indicate a successful enrollment.
We should send a dedicated event instead, for greater reliability and less chance of e.g. duplicate events or a missing page view.
Acceptance Criteria
We have a dedicated completed enrollment event, sent only when the user has successfully registered with the payment processor
The text was updated successfully, but these errors were encountered:
thekaveman
added
chore
Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
analytics
App event tracking, instrumentation, logging: Metabase, Amplitude
labels
Aug 18, 2022
analyticsApp event tracking, instrumentation, logging: Metabase, AmplitudechoreChores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
Right now we send a page view event for the
success
view inenrollment
. In Amplitude, we have a custom event for page view with path =/enrollment/success
to indicate a successful enrollment.We should send a dedicated event instead, for greater reliability and less chance of e.g. duplicate events or a missing page view.
Acceptance Criteria
completed enrollment
event, sent only when the user has successfully registered with the payment processorThe text was updated successfully, but these errors were encountered: