docs: attribute the dashboard link with UTM parameters - #19
Merged
Conversation
The dashboard now records first-touch UTM and breaks new API keys down by acquisition channel, but it can only receive what the links carry. Without this, everyone arriving from this README is attributed to direct.
Sapient docs evalsWaiting for the staging docs URL before running evals. Sapient will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
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
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.
The Sonilo dashboard now captures first-touch UTM parameters and breaks new API keys down by acquisition channel (sonilo-ai/sonilo-api-dashboard#171). That instrumentation is only a receiver — it can attribute a visitor only if the link they followed carries the parameters. Until this lands, everyone arriving from this README is recorded as
direct.Tags the "create an API key" link with
utm_source=sonilo_python&utm_medium=readme&utm_campaign=sdk_quickstart.GitHub and PyPI render this same README, so they share one
utm_source— they are not separately distinguishable, which is fine. The useful question is which package brought the user, not which host they read about it on.Docs only. No code, no dependency, no release required.