Can I add a Facebook pixel to a short link?

Yes — paste your Meta pixel ID into the link options and set the link to preview or frame mode. The pixel fires as a PageView when someone opens it, adding that visitor to your retargeting audience without touching the destination site.

Why is my pixel not firing on my short link?

Almost always because the link is in redirect mode. A redirect sends the browser straight on, so no page renders and no JavaScript runs. Switch the link to preview or frame mode, then confirm with your platform debug tool that the hit registers.

Do I need access to the destination website?

No. That is the whole point — the pixel runs on the interstitial your short link serves, before the visitor continues. You can build an audience from clicks to a page you have no control over, such as a press article about you.

Is putting a retargeting pixel on a link legal?

It is regulated, not forbidden. In the EU and UK a marketing pixel needs consent before it fires, and you are the one responsible for having it — not the shortener. Also disclose the tracking in your privacy policy, which the ad platforms require anyway.

Retargeting Pixels on Short Links: Audiences From Clicks

Here is a problem every marketer eventually runs into. You share a link — to a review of your product on someone else's blog, to a press mention, to a partner's landing page — and it does well. Hundreds of people click. Those people just raised their hand and said "I am interested." And you cannot reach a single one of them again, because the pixel that would have remembered them sits on a website you do not own.

A retargeting pixel on a short link closes that gap. The link passes through your shortener before it continues to the destination, and that moment is enough to add the visitor to your advertising audience. You did not need access to the destination site. You only needed the link to be yours.

What a retargeting pixel actually does

A pixel is a small piece of tracking code from an ad platform. When it runs in someone's browser, it drops an identifier that lets the platform recognise that browser later. Build up enough of them and you have an audience: a group you can advertise to specifically, instead of paying to shout at strangers.

Retargeting audiences convert better than cold ones for an unglamorous reason — they are made of people who already showed interest. Someone who clicked your link is a warmer prospect than someone who has never heard of you, and the ad budget knows it.

Which pixels you can attach

urlik supports the four that cover most of the market:

Meta (Facebook / Instagram) — the classic fbq pixel, fired as a PageView.
VK — VK Retargeting, for audiences you use inside VK Ads.
Google — a gtag tag, so clicks flow into Google Ads remarketing and Analytics.
Yandex Metrica — with clickmap and link tracking enabled.

You paste the pixel ID when you create or edit the link. Nothing else to install: no snippet on the destination, no cooperation from whoever owns it.

The catch nobody mentions — and it is a big one

A pixel is JavaScript. JavaScript needs a page to run on. And a plain short link, by design, does not give it one: the server answers with a redirect and the browser leaves immediately, before any code could execute.

So on urlik, pixels only fire on links set to preview or frame mode, because those modes actually render a page. Set the link to straight redirect and the pixel silently never runs — you will collect exactly zero audience and wonder why. This is not a urlik quirk; it is how the web works, and any service claiming pixels on a pure redirect is either rendering an interstitial too or misleading you.

That makes the mode a real trade-off. Preview mode adds a step between the click and the destination — a card showing where the visitor is going, with a countdown. You pay a little friction and lose a few impatient clickers. In exchange you get the audience. Whether that trade is worth it depends on the link: for a cold social post pushing hard for the click, probably not. For a campaign whose whole point is to build a remarketing pool, absolutely.

How to set it up

Three steps, about a minute:

Get the ID from your ad platform — the numeric pixel ID in Meta Events Manager, the counter number in Metrica, the tag ID in Google Ads.
Create the link on urlik.xyz, open the advanced options, choose preview or frame mode and paste the ID into the pixel field.
Verify it fires — open your own short link and watch the platform's debug tool (Meta Pixel Helper, Metrica's live report) register the hit. Do not skip this. A pixel that was never verified is a pixel that quietly did nothing for three weeks.

Where this earns its keep

The pattern that pays off is targeting intent you cannot otherwise capture:

Press and reviews. A magazine writes about you. Share the article through a pixelled link and retarget everyone who read it — an audience with genuine intent, on a page you have no access to.
Affiliate and partner traffic. Your partner's landing page carries their pixel, not yours. A pixelled short link gives you your own copy of that audience.
Offline to online. A QR code on a flyer resolves through a pixelled link, and the person who scanned it in a shop becomes retargetable online. Pair it with a dynamic QR code and you can change the destination later without reprinting.
Content you did not write. Anything you amplify — a study, a comparison, a video — can build your audience instead of only theirs.

Do it lawfully, or do not do it

This is tracking, and tracking has rules. In the EU and UK, a retargeting pixel is not "strictly necessary", so it needs the visitor's consent before it fires — that is ePrivacy, and GDPR sits behind it. The uncomfortable part: the consent banner lives on the destination site, and on an interstitial you control there is no banner at all. Firing a marketing pixel on an interstitial to EU traffic without consent is a violation, and "the shortener did it" is not a defence — you set it up, so you are the controller.

Practical reading: use pixelled links where you can honestly justify the legal basis, keep them off audiences where you cannot, and remember that the platforms themselves (Meta especially) also require you to disclose tracking in your privacy policy. Nobody enjoys this paragraph. It is still cheaper than a complaint.

Pixels are not analytics

Worth separating two things people conflate. A pixel builds an advertising audience — it is for reaching people again. It is not how you find out what happened: for that you want click statistics, which urlik records on every link regardless of mode, including plain redirects. If your question is "how many clicked, from where, on what device", read the guide to tracking link clicks. If your question is "how do I advertise to them next week", that is the pixel. Use both, and tag the links with UTM parameters so the campaigns stay legible in analytics.

The short version

A pixel on a short link turns other people's pages into your audience. It only works in preview or frame mode, because a redirect gives JavaScript nowhere to run — accept that trade or skip the feature. Verify the pixel actually fires before trusting it, get consent where the law asks for it, and keep pixels and click stats in separate mental boxes: one is for reaching people again, the other for understanding what already happened.