Retargeting pixels

A retargeting pixel tells an ad platform "this person clicked" — so you can show your next ad to the exact people who tapped your link. Attach your Meta Pixel, TikTok Pixel, or Google Tag Manager container to a Zippy link, and every tap fires them before the visitor is sent on.

That works even where pixels normally can't reach — a bio link, a story link, a link in a caption. If Zippy is in the middle of the tap, your pixel sees it.

Retargeting pixels are available on Hero and up.

How it works

1. You add your pixel IDs once, in the dashboard.
2. On any link, tick the pixels you want it to carry — up to 5 per link.
3. Someone taps the link. Zippy fires the ticked pixels, then redirects:
   • Platform links (Instagram, TikTok, YouTube, …) fire the pixels on the interstitial page — the same page that springs the native app. No extra hop.
   • Plain links get a lightning-fast pass-through page: the pixels fire, then the visitor bounces straight to the destination. Blink and you miss it.

Either way the visitor ends up exactly where they were going — the pixels just get their split second first.

Which pixels

Pixel IDs can use letters, numbers, dashes, and underscores, up to 32 characters — the formats Meta, TikTok, and GTM actually issue. Zippy checks the format when you save, so a typo'd ID gets caught in the dashboard, not silently dropped on a live link.

Set it up

Dashboard (web): add your pixel IDs in Settings → Pixels (paste the ID from your Meta Events Manager, TikTok Ads Manager, or GTM container — e.g. GTM-XXXXXXX). Then, in the ZIP form or a link's editor, open Retargeting pixels and tick the ones this link should fire. Untick to stop; changes take effect immediately and the short link never changes.

It fires on YOUR behalf

The pixels on a link are your pixels — they fire for you, the link's creator, exactly as if the visitor had landed on a page you own. That means your privacy obligations apply: your privacy policy, your consent requirements, whatever disclosures the platforms and your local rules require of you as an advertiser. Zippy fires the tags; the data relationship is between you, the ad platform, and your audience.

Notes

• Pixels compose with everything else on the link: a password gate comes first, audience routing resolves the destination, your UTMs ride along — and the pixels fire on the way through.
• The pass-through page is deliberately tiny and never cached — a living link's destination stays editable, and the pixels re-fire on every tap.
• Max 5 pixels per link. If you need more than that on one link, a GTM container is the move — one container, as many tags as you want inside it.

Read more

• Blog: Every tap on your link can feed your ads · why your pixels miss in the in-app browser
• Changelog: Retargeting pixels