FB Pixel Short Links: Retarget on Click

How does a short link carry an FB Pixel for retargeting?

When you create a short link in 連, you can attach one or more tracking tags to it: FB Pixel, GA4, GTM, TikTok Pixel and LINE LAP — and you can put several of them on the same link.

When someone clicks that short link, 連 first returns a tiny interstitial page that fires the pixel in the browser, then sends the visitor on to the real destination. In other words, audience collection happens at the moment of the click, not after the visitor lands or completes a purchase.

Why does a click add someone to your audience without landing or converting?

The traditional approach puts the pixel on your own web page, so a visitor has to actually open that page before the pixel records them. But in many ad scenarios visitors drop off on the way, or the destination simply isn't a site where you can install a pixel.

連 moves the pixel's trigger point earlier — to the instant of the click. The interstitial fires the pixel first, then redirects. So as soon as someone clicks your short link, they are already in your retargeting audience, and you can run follow-up ads to that group even if they never see the destination page.

What if you can't install a pixel on the destination (e.g. a marketplace listing)?

This is the core use case. When your destination is a marketplace product page, someone else's site, or any page where you have no right to drop a tracking tag, you cannot install a pixel on the destination itself.

Instead, use a 連 short link: attach the pixel at the link layer, then point it to that destination you don't control. The pixel fires on the interstitial regardless of whether the destination accepts a tag, so you still collect those clickers into your retargeting audience.

Honest note: this is a client-side pixel relay, not server-side CAPI

To be clear: what 連 does is a client-side pixel relay — it fires the pixel inside the browser at the moment of the click. That is a different thing from a server-to-server Conversions API (CAPI).

If you need server-side conversion reporting (CAPI), you configure that on the destination side. The 連 layer handles the pixel fire at the moment of the click. Keeping the two distinct avoids misreading your ad data.

Pair with /suffix and A/B for channel-level audiences

Pixel relay works alongside 連's other features. With /suffix source tracking you can tell which channel a click came from, and with A/B splitting you can separate clickers by variant and by channel into different retargeting audiences.

That way you don't just collect one undifferentiated pile of clicks — you get audience groups you can split by channel and by variant, and retarget each one separately.

FAQ