Sign in Get started

Tracking pixels — your pixel library

Add your Meta, GA4, GTM, LinkedIn, Pinterest, X, Quora, TikTok and Snapchat pixel IDs once. Attach them to any short link with a checkbox.

Updated today 6 min read

Most marketing platforms send their data home through a small JavaScript snippet that fires when someone hits a page. Meta's pixel, Google Analytics, TikTok's pixel — they're all the same shape: a tiny tag that loads, sends a PageView event, and disappears.

Short links normally redirect too fast to fire any of that. The visitor never lands on a page where your pixels live. They land on the destination — somebody else's page, where your pixel can't reach.

A tracking pixel attached to a Linked.Codes short link fixes that. Right before the redirect, we load a fast invisible page that fires every pixel you've attached. The PageView lands in your dashboards. Then the redirect happens.

Add a pixel once, attach it to anything. The library lives at Pixels in your sidebar. Give it a name and the ID, then tick the box on any short link that should fire it.

What you can do

Add a pixel Name + platform + ID. One form, takes 20 seconds. Attach to a link Open any short link, tick the box, done. Multiple per link Fire several pixels on the same click. Up to 20. Remove a pixel Detaches automatically from every link that used it.

Supported platforms

Nine of the platforms most operators run. Pick the one that matches what's already capturing data in your marketing stack.

  • Meta (Facebook) — the numeric Pixel ID from Events Manager.
  • Google Analytics 4 — your Measurement ID, usually G-XXXXXXXXXX.
  • Google Tag Manager — the container ID, GTM-XXXXXXX.
  • LinkedIn — the Insight Tag partner ID.
  • Pinterest — the Pinterest Tag ID.
  • X (Twitter) — the Universal Website Tag pixel ID.
  • Quora — the Quora pixel ID.
  • TikTok — the pixel SDK ID from TikTok Events Manager.
  • Snapchat — the Snap pixel ID.

Each platform stores the same shape of data on its side — clicks, when, from where — and you read it in your own dashboards there. Linked.Codes never reaches into those dashboards or runs analytics on the pixel data. We just fire the events.

Add a pixel

  1. Open Pixels from the sidebar.

    Or hit the "+" next to it for a direct shortcut to the new-pixel form.

  2. Name it something you'll recognise.

    "Main FB pixel", "GA4 prod", "TikTok holiday campaign" — names matter when you've got fifteen of them. Up to 80 characters.

  3. Pick the platform.

    Tap the tile that matches. The hint text under the ID field changes to show what the platform's ID looks like.

  4. Paste the ID.

    Raw value from the platform's events manager — we strip everything that isn't safe to put in a script.

  5. Save.

    The pixel lands in the list. Now it's ready to attach.

Same pixel, many links. Create one "Main FB pixel" and use it on 500 short links. Update the ID once in Pixels and every link picks up the change.

Attach to a link

  1. Find the short link, click into it.

  2. Find the Tracking pixels card.

    Below Social preview, above Metadata. The list shows every pixel in your library with a checkbox.

  3. Tick the boxes for the pixels that should fire.

    Each ticked pixel will fire on every click of this link. No tick — nothing fires for that pixel.

  4. Walk away.

    Autosaves like everything else. The bottom-right pill confirms.

You can also add a brand-new pixel without leaving the link editor — there's a "+ New pixel" button at the top of the Tracking pixels card. The newly-created pixel is auto-attached to the link.

Multiple pixels per link

Up to 20 pixels can fire on a single click. Common patterns:

  • One per network you're advertising on — Meta + Google + TikTok on the same UGC campaign so each platform sees its own attribution.
  • One per event format — a GA4 pixel for the dashboard, plus a GTM container that fans out to the rest of your stack.
  • Per-campaign vs always-on — a long-term GA4 pixel attached to every link, plus a short-term Pinterest pixel attached only during a launch.
Pixels add a 500ms wait. No pixels attached = instant 302 redirect. Any pixels = a short interstitial page so they have time to fire. Faster than waiting for the destination's own pixel to load, but it's not zero.

Remove a pixel

  1. Open Pixels.

  2. Click Delete on the pixel card.

    Confirm. The pixel is gone.

  3. You don't have to walk the list — the cleanup happens for you.

If you only want to stop firing one pixel on one specific link, untick the box on that link instead — the pixel stays in your library.

What visitors see

For a brief moment, a small dark page with a "Redirecting…" message and a mint dot. The pixels load and fire their PageView events in the background. Then the page replaces itself with the destination. Total wait: about 500ms — fast enough that visitors barely notice, slow enough that pixels actually fire.

If you'd rather not show the interstitial — for example on a link where you're tracking opens but care more about speed — leave the Tracking pixels card empty. The 302 redirect happens with no in-between page.

Combine with other settings

Analytics Our own click counts — separate from what the pixels send to their platforms. Short link basics Slug rules, custom domains, the redirect surface where pixels fire. Password protection Gate a link before pixels fire. Failed unlocks don't trigger any tracking.

FAQ

Will my pixel show "scan" or "click" as the event?

It fires a standard PageView event. Every pixel platform treats a PageView the same way — counted, attributed, dropped into the right report.

Can I fire a pixel only on QR scans, not link clicks?

Not yet — pixels fire on every visit to the short URL regardless of how the visitor got there. Use a separate short link for the QR if you want to split the signals.

Does this work for tenant users on my whitelabel domain?

Yes — pixels are scoped to whoever owns the link. Your sub-users see their own pixel library, attach their own pixels to their own links. Cross-tenant pixel sharing isn't a thing on purpose.

Is my pixel ID exposed publicly?

Yes — that's true of every site that uses tracking pixels. The ID is in the page source on any platform you've installed it. It's not a secret credential; the platform's security model assumes it's public.

What if the visitor blocks tracking?

Their browser stops the pixel script from loading or sending. The redirect still works — we don't gate it on the pixel firing.