Skip to content

docs: attribute dashboard links with UTM parameters - #1

Open
spencer-zqian wants to merge 1 commit into
mainfrom
docs/utm-attribute-dashboard-links
Open

docs: attribute dashboard links with UTM parameters#1
spencer-zqian wants to merge 1 commit into
mainfrom
docs/utm-attribute-dashboard-links

Conversation

@spencer-zqian

Copy link
Copy Markdown

The Sonilo dashboard now captures first-touch UTM parameters (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 plugin is recorded as direct.

Tags the sign-up link and the authorization sign-in link with utm_source=codex_plugin&utm_medium=readme&utm_campaign=mcp_quickstart.

Deliberately left alone:

  • The Support-section link — a support path for people who already have an account.
  • The manifest author.url / homepage / websiteURL fields — metadata rather than click targets, and scripts/check_release.py asserts on them exactly. python3 scripts/check_release.py passes on this branch.

Worth knowing: this plugin authenticates over OAuth rather than an API key, so its users do not show up in the "new API keys by channel" metric that motivated this work. They will still carry correct first-touch attribution on their PostHog person.

Docs only. No code, no dependency, no release required.

The dashboard now records first-touch UTM and breaks acquisition down by
channel, but it can only receive what the links carry. Without these,
everyone arriving from this plugin is attributed to direct.

The Support-section link is left untagged (support path, not acquisition),
and the manifest author/homepage/website fields are untouched -- those are
metadata that scripts/check_release.py asserts on exactly.
@sapient-app

sapient-app Bot commented Jul 28, 2026

Copy link
Copy Markdown

Sapient docs evals

Waiting 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: bba7b1d
Status: waiting for staging docs URL

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