Skip to content

docs: migrate sponsor link to canonical UTM convention (GTM-32)#2

Merged
benvinegar merged 1 commit into
mainfrom
talton/gtm-32-migrate-slop-scan-hunk-podguy-sponsor-links-to-canonical-utm
Jun 10, 2026
Merged

docs: migrate sponsor link to canonical UTM convention (GTM-32)#2
benvinegar merged 1 commit into
mainfrom
talton/gtm-32-migrate-slop-scan-hunk-podguy-sponsor-links-to-canonical-utm

Conversation

@TaltonFiggins

Copy link
Copy Markdown
Contributor

Summary

Migrates the README sponsor link's UTM params to the canonical "Modem-owned repo README" row in the GTM UTM Tagging Strategy (updated 2026-05-18):

  • utm_campaign: podguyoss_podguy
  • utm_content: (none) → readme_footer

Aligns with the convention applied to newly-shipped sponsor blocks in modem-dev/baudbot (GTM-29) and modem-dev/glance-agent-plugins (GTM-30). Companion PRs land in modem-dev/hunk and modem-dev/slop-scan on the same branch name.

Linear

GTM-32 — Migrate slop-scan, hunk, podguy sponsor links to canonical UTM convention

Changes

  • Update both occurrences of the sponsor link (text + <a href> wrapping the <picture>)

Testing

  • README renders correctly in GitHub markdown preview
  • After merge: confirm $pageview with utm_campaign=oss_podguy lands in PostHog (low traffic — may take time)

Related

  • UTM Generator (Notion) row needs Campaign/Content updated to match after merge

Update the README sponsor link's UTM params to match the canonical
"Modem-owned repo README" row in the GTM UTM Tagging Strategy
(updated 2026-05-18): utm_campaign=oss_podguy (snake_case) and
utm_content=readme_footer. Aligns with the convention applied to
recently-added sponsor blocks in modem-dev/baudbot and
modem-dev/glance-agent-plugins.

Linear: GTM-32

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@benvinegar benvinegar merged commit a860d3b into main Jun 10, 2026
3 checks 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.

2 participants