Tracking pixels

How it works

1. You create a pixel

   It gets its own URL: gettrack.link/p/<slug>

2. You embed it as an image

   Anywhere HTML or Markdown images render — a blog post, a docs page, a Notion page, a GitHub README.

3. Every page load fetches the image

   Track Link serves a 43-byte transparent 1×1 GIF and records a hit. The image is invisible to the reader and served with no-cache headers, so repeat views count too.

Hits are stored exactly like clicks, so all the analytics you have for links — unique visitors, geography, devices, browsers, referrers, hour-by-hour charts — work for pixels as well. Known bots and crawlers are filtered out automatically.

Create a pixel

1. Go to Pixels in the sidebar and click the new pixel button
2. Give it a name — an internal label only you see (e.g. "Blog post: Q2 launch")
3. Optionally set a slug — the URL path after /p/. Letters, numbers, dashes, and underscores; auto-generated if left blank
4. Click Create Pixel

You land on the pixel's detail page with ready-to-copy embed snippets, live stats, and the counter badge builder.

Embed snippets

The pixel detail page offers four formats. Pick whichever your platform accepts:

HTML

<img src="https://gettrack.link/p/your-slug" width="1" height="1" alt="" style="display:none" />

Markdown

![](https://gettrack.link/p/your-slug)

URL only

https://gettrack.link/p/your-slug

AMP

<amp-pixel src="https://gettrack.link/p/your-slug"></amp-pixel>

Some tools insist on an image file extension — appending .gif, .png, or .jpg to the pixel URL works the same (e.g. /p/your-slug.gif).

Where pixels work well

• Blog posts and documentation pages
• Landing pages and internal HTML pages where you can't add scripts
• Notion and Confluence pages
• GitHub READMEs and profiles (especially with the counter badge)
• Any CMS that lets you insert an image but not JavaScript

Email caveats

Pixels load in most email clients, but treat email open counts as approximate:

• Apple Mail Privacy Protection preloads images on Apple's servers — you'll see opens that never happened
• Gmail proxies images through Google's datacenters — the recipient's real IP is hidden, so geography typically shows a US or Canadian datacenter

The counter badge

Besides the invisible pixel, every pixel also serves a visible counter badge — an SVG that displays the live hit count, like views | 2,451. It's popular on GitHub READMEs and profile pages. Each badge load also records a hit and shows the updated count.

![views](https://gettrack.link/p/your-slug/badge.svg)

The badge builder on the pixel detail page customizes it with a live preview (previewing never inflates your count):

Options are query parameters, for example: /p/your-slug/badge.svg?label=readers&color=brightgreen&compact=true

Reading the numbers

• Total hits — lifetime count, every load
• Unique — visitors deduplicated by a fingerprint of IP, browser, and screen; shown for the recent window on the detail page
• Top country / top device — quick context on the detail page

For full breakdowns — countries, browsers, referrers, hour-by-hour — open View analytics on the pixel detail page or use the Analytics page, where pixels appear alongside your links.

FAQ

Next steps

• Link tracking - Track clicks when you control the link
• Conversion tracking - Measure actions, not just views
• Plans & limits - How hits count against your quota