WOC: Implement utm* params of a login UserAction stored in the DB feature #2212 #2359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is for saving utm* params to DB for data analysis, relevant story is 2212.
Whenever user access gitcoin with "utm_medum, utm_source, utm_campaign" will store them in cookie, after user login or user logout will store to dashboard_useraction table.
Checklist
Affected core subsystem(s)
UserAction data model.
Testing
Test with below 3 scenarios.
Scenario: Record utm* in Cookie
Give: utm_medum, utm_source, utm_campaign in URL
When: User open gitcoin
Then: Should record utm* in Cookie
Scenario: Record utm* in DB
Give: utm* in Cookie
When: User click "LOG IN" button
Then: Should record utm* in DB
Scenario: Record utm* in DB
Give: utm* in Cookie
When: User click "Log Out" button
Then: Should record utm* in DB
Refers/Fixes