Retargeting pixel on short links: how it works
Add a Meta, LinkedIn, X, Google Ads, Microsoft Ads or Pinterest retargeting pixel to a short link, so the people who click can see your ads again.
On this page
A retargeting pixel on a short link tells your ad platform who clicked, so you can show those people your ads again later. You add each pixel once as an integration, tick it on the links that should fire it, and Brevily loads it on a one-second page before sending the visitor on.
That matters most when the page behind the link isn't yours. A podcast sends listeners to a marketplace listing, a poster's QR code opens a partner's event page, a post links to a review site. You can't put your pixel on those pages, but you can put it on the short link in front of them.
Before you start: you need a short link (see how to create a short link) and your pixel's ID from the ad platform. Adding a pixel needs the Integrations permission. Pixels depend on your plan, and they count towards your plan's integrations with webhooks and Google Analytics 4; see pricing.
How a retargeting pixel on a short link works
- Set up once: each pixel is an integration of your organisation, so one Meta pixel can serve all your links.
- Chosen per link: a link fires only the pixels you tick on it, up to 10. A new link fires none, unless its folder has pixels set for new links.
- A one-second page: a person following the link sees a bare page titled "Opening…" while the pixels load from the ad platforms, then goes on to the destination. A Continue link is there for anyone who doesn't want to wait.
- Never for bots or previews: crawlers, chat apps drawing a link preview and link checkers never see the pixel page, so they don't end up in your audiences.
Each pixel sends its platform's standard page-visit signal, with no script and no event or value of your own. A short link sets no cookie of its own, but the ad platforms may set theirs, so asking for any consent that needs is yours to handle. Brevily's trust page names pixels as the one reason a short link may need a consent banner.
Which ad platforms are supported
The Pixel ID each platform takes:
- Meta: the Meta pixel ID.
- LinkedIn: the LinkedIn partner ID.
- X: the X pixel ID.
- Google Ads: the ID that starts
AW-. - Microsoft Ads: the UET tag ID.
- Pinterest: the Pinterest tag ID.
Add a pixel as an integration
- Open Link setup › Integrations and find the Ad pixels card.
- Choose Add a pixel.
- Pick the Platform and paste the Pixel ID.
- Choose Add pixel.
[screenshot: the Integrations page's Retargeting pixels card with the Add a pixel dialog open]
Add as many as you need, even several of one platform: a Meta pixel per client or per ad account, for example. Each counts as one integration. A pixel fires in the visitor's browser, so its row reads In the browser rather than showing deliveries.
Turn off stops a pixel on every link that names it, without unticking it anywhere; Turn on brings it back.
Choose the pixels a link fires
On a new link, open Ad pixels on the New link page and tick the pixels. On a link you already have:
- Open Links, choose the link and open its Routing tab.
- In Ad pixels, tick each pixel to fire, such as Fire Meta pixel, with its ID beneath.
- Choose Save pixels.
[screenshot: the Routing tab's Retargeting pixels panel with two pixels ticked and Save pixels]
Running a whole campaign through one folder? Set the folder's Ad pixels preset, and every new link in it starts with those pixels ticked.
What visitors see, step by step
On the Routing tab, How a click is decided puts pixels near the end. A visit first passes the safety check, any password, and the link's targeting rules and A/B test; then:
- The click is counted, exactly as on a link without pixels.
- On iPhone and Android, a link with a deep link heads for your app instead (on iPhone, sometimes by way of a page offering the app), and the pixel page isn't shown.
- Everyone else sees the pixel page for about a second.
- The browser moves on to the page the routing chose, with the link's UTM tags.
Pixels belong to the link, whichever rule or variant sent the visitor. QR code scans fire them too, since a scan opens the same link.
Common questions
Does a retargeting pixel slow down a short link?
By about a second, for people only: they see a one-second page while the pixels load. Bots, link previews and link checkers never get the page.
How do I know a retargeting pixel fired on my short link?
Check the ad platform's own reports. The pixel loads in the visitor's browser, so a browser that blocks ad platforms stops it, and Brevily can't see whether it loaded.
What happens to retargeting pixels if my plan drops them?
Your pixels, and the links they're ticked on, stay as they are, and nothing fires until your plan includes pixels again.
Do retargeting pixels on short links need a cookie banner?
They may. The short link sets no cookie of its own, but the ad platforms you pick may set theirs, so collecting any consent that needs is up to you.
Next steps
- Link tags and events: count sign-ups and sales from each link.
- Send link clicks to Google Analytics 4: see link clicks beside your site's traffic.
- Targeting rules: send each audience to its own page before the pixel fires.
- Usage limits and add-ons: what to do when your integrations are all in use.
- Brevily API: do the same from your own code.
On this page