For Developer Tool Companies
Track GitHub README to Signup Conversions
Embed invisible tracking pixels in your GitHub READMEs. See exactly which repositories drive the most signups for your developer tool — and double down on what works.
Pixel Generator
Unique URLs per repo
Visitor Analytics
Real-time dashboard
Signup Attribution
Webhook integration
Simple Pricing
Pro
$12
per month
- ✓Unlimited tracking pixels
- ✓Real-time visitor analytics
- ✓Signup attribution via webhooks
- ✓Top converting repos dashboard
- ✓CSV export
- ✓Email support
FAQ
How does the tracking pixel work?
You embed a tiny 1×1 transparent image URL in your README markdown. When GitHub renders the README and a visitor loads the page, their browser fetches the pixel — logging the visit, referrer, and timestamp against your repository.
How are signups attributed to a repository?
When a tracked visitor signs up for your tool, your signup flow fires a webhook to our API with the user identifier. We match it to the pixel visit session and record the conversion, showing you exactly which README drove the signup.
Does this violate GitHub's terms of service?
No. Embedding external images in READMEs is standard practice and explicitly supported by GitHub Flavored Markdown. Many analytics and badge services work the same way.