Marketing · 7 min read · Updated October 12, 2026

Retargeting Pixels on Short Links: How They Work

A retargeting pixel normally has to sit on the page someone lands on, as a script tag that fires when the page loads. That works fine for your own site, and falls apart the moment the destination is an app store listing, a partner landing page, a PDF, or anyone else's domain, because you cannot edit their HTML.

A short link does not have that problem. Every click already passes through ReSlug on its way to the destination, so the pixel can fire there instead, before the redirect, regardless of what page the visitor ends up on. This guide covers how that works, what it costs you in reliability and privacy, and when it is worth setting up.

Why pixels usually cannot reach the destination

A platform pixel, whether it is Meta, Google Ads, LinkedIn, TikTok or X, is JavaScript that runs in the visitor's browser and reports back "this person reached this page." That requires write access to the page: an app you own, a site you host, something you can paste a script tag into. The moment a campaign sends clicks to a page you do not control, that stops being possible, and most of the links worth retargeting on are exactly that kind of page.

• App store listings. You can link to your app on the App Store or Google Play, but you cannot inject a pixel into Apple's or Google's page.
• Partner and affiliate pages. A co-marketing landing page, a reseller's site, a press mention: all out of your control.
• Documents and files. A PDF, a calendar invite, a map pin opened from a QR code on a flyer. There is no page to put a script on at all.
• Anywhere the destination changes. Even on your own site, swapping the landing page for an A/B test or a fallback redirect means re-adding the pixel every time.

Firing the pixel on the redirect instead

ReSlug attaches the pixel to the link itself, not the destination. When someone clicks, the request reaches ReSlug first; before it issues the redirect, it serves a brief pixel step that fires every pixel attached to that link, then sends the visitor on to the destination URL. The visitor sees nothing but a normal, fast redirect. The short URL does not change, and the destination page needs no changes at all.

That last point matters more than it sounds: a pixel embedded directly on a page can, in principle, slow that page down if the ad network is having a bad day. On a redirect link there is no page to slow down, only a hop that either includes the pixel call or times out and proceeds without it.

The platforms and ID formats ReSlug supports

Pixels are created once per workspace and then attached to as many links as you like. Each one needs a platform and the identifier that platform's ad manager gives you, and ReSlug validates the format before saving it.

Paste the ID in wrong and ReSlug rejects it immediately rather than saving something that will silently fail to fire later. If you are not sure which value your ad platform means by "pixel ID," the format column above is usually enough to tell it apart from an account ID or an API key.

Attaching pixels to a link

Pixels live at the workspace level, separate from any one link. Create them from Pixels in your workspace settings, giving each one a name, a platform and an ID, then attach whichever ones apply from the Retargeting pixels option when you create or edit a link. A link can carry up to 5 pixels at once, so a single click can feed several ad accounts, for example a Meta pixel for one agency and a Google Ads pixel for your own account on the same link.

The workspace holds up to 10 pixels on the Pro plan; the Free plan does not include retargeting pixels. If your workspace is on Free and you already configured pixels, nothing is deleted: the configuration is kept but paused, and pixels start firing again the moment you upgrade. Deleting a pixel detaches it from every link that used it and stops it firing immediately, while the pixel itself stays exactly as configured on the ad platform side, ready to be re-added later under a new name if you need it again.

What this buys you, and what it does not

A pixel attached to a link tells the ad platform that one specific click happened, which is enough to add that visitor to a retargeting audience. It is not a replacement for a pixel embedded on your actual site, and it does not see anything past the redirect: no page views on the destination, no add-to-cart, no purchase. If the destination is a page you do control and you can also embed the platform's own pixel there, do both; the link-level pixel covers the clicks the embedded one never will.

• No cookies of its own. ReSlug does not set marketing cookies; the ad platform's pixel call does whatever that platform normally does when it fires.
• Consent stays with you. You are still the one running the ad campaign and showing the destination to visitors, so cookie and privacy disclosures for the platforms you attach remain your responsibility, the same as if the pixel were embedded on your own page.
• One event, not a funnel. Each click fires each attached pixel once. Anything after the redirect is the destination page's job to track, if it can be tracked at all.

Where a link-level pixel actually pays off

The common thread is a click you want to count toward retargeting on a page you did not build. A QR code printed on a flyer or storefront window that points at a map listing or a menu PDF becomes a retargeting touchpoint instead of an untracked scan. A link-in-bio page that sends traffic to an App Store listing can retarget everyone who tapped through, long before anyone opens the app. An affiliate or press link to a partner's page still builds your audience even though their page has nothing of yours on it.

It is also worth combining with UTM parameters on the same link: the pixel builds the ad audience while the UTM values tell your analytics which campaign, channel and placement produced the click, so you are not choosing between retargeting and attribution on the same piece of traffic.

Checking that a pixel actually fired

Because the pixel step is invisible to the visitor, the way to confirm it worked is on the ad platform side: Meta's Events Manager, Google Ads' tag diagnostics, LinkedIn's Insight Tag status and the equivalents for TikTok and X all show recent pixel activity, usually within a few minutes of a real click. If a platform shows nothing after several test clicks, re-check the ID against the format table above first; a transposed digit is the most common cause, and ReSlug's format validation only catches malformed IDs, not ones that are simply wrong. You can also use a redirect checker to confirm the link itself still redirects correctly after adding pixels, since that is the one thing that must never break.