Skip to content

Persist standard first-touch UTM attribution - #415

Open
jmgasper wants to merge 1 commit into
devfrom
aws_analytics
Open

Persist standard first-touch UTM attribution#415
jmgasper wants to merge 1 commit into
devfrom
aws_analytics

Conversation

@jmgasper

Copy link
Copy Markdown
Collaborator

Summary

  • persist all six standard UTM fields for 30-day first-touch attribution
  • validate cookie JSON and bound values to the shared AWS analytics contract
  • propagate the complete attribution set to signup URLs
  • document ownership boundaries so host applications initialize the AWS SDK only once
  • resolve existing Svelte type errors surfaced by the required repository check

Verification

  • npm run lint was attempted but this repository has no lint script
  • npm run check: 0 errors and 0 warnings
  • npm run build
  • legacy Heap, Sprig, Google Analytics, and tag-manager reference scan: clean

@jmgasper

Copy link
Copy Markdown
Collaborator Author

CI note: the Use Trivy check fails during job setup, before repository checkout or scanning, because origin/dev already pins aquasecurity/trivy-action@0.33.1 and GitHub reports that version cannot be resolved. The branch does not modify the workflow. CircleCI build-dev, check-types, both CodeQL jobs, and the AI review all passed.

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

Successfully merging this pull request may close these issues.

1 participant