Repository navigation
Measure campaign visits, starts and completions before acquisition launch - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Campaign links such as ?source=x now emit deduplicated visit, start and completion events for Daily Five. Six fixed sources are accepted (X, Listdle, Playlin, DLE Directory, WebGames and Show HN); arbitrary query values are never uploaded. This lets us evaluate actual play from the launch channels while ordinary analytics continue to exclude query strings.
Events have no custom properties, respect host/Do Not Track restrictions, and exclude practice. Expands the loading queue to eleven requests and enforces the ledger's 4 KB write bound as well as its seven-day retention. These are source-attributed browser-day counts, not verified new-user cohorts. A tagged complete-and-shared incoming challenge adds at most three quota units.
Validation: full Node suite and 21 Python tests pass. New checks cover attribution, unknown sources, reload deduplication, Do Not Track/preview/practice exclusions, maximum queued events, and worst-case ledger size. The existing deployment workflow rebuilds generated public pages from these source changes.