Link retargeting explained: how it works and where it breaks
Link retargeting runs a Meta, Google Ads or LinkedIn pixel on a redirect page. See how it works in 2026, which browsers block it and what EU rules require.
Muzahid Maruf, FounderUpdated
On this page
Explore with AI
Opens this article inside the chosen assistant with a ready-made prompt.
Link retargeting adds an ad platform's pixel to a short link, such as the Meta Pixel, a Google Ads tag or the LinkedIn Insight Tag.
Each click runs the pixel on the redirect page, and the platform can add the visitor to an audience even when the link points to a page you do not own.
In StatCounter's September 2026 data, Chrome holds 66.36% of browser share, Safari 18.27% and Firefox 2.80%. Chrome leaves third-party cookies to user choice, Safari blocks them and Firefox confines them to the site that set them.
EU and UK rules add a consent step that a redirect page cannot show.
Key takeaways
- Chrome has 66.36% of browser share in September 2026 and leaves third-party cookies to user choice, so link retargeting can still match consenting visitors there.
- Safari (18.27%) and Firefox (2.80%) block or isolate third-party cookies by default, which leaves about 1 clicker in 5 unmatched before consent is counted.
- EDPB Guidelines 2/2023, Google's EU User Consent Policy and Meta's Business Tools Terms all expect consent before ad cookies are set, and a redirect page has no room to ask.
- Replug includes retargeting pixels from $9 a month and Rebrandly from its Professional plan. TrackRev fires Meta Pixel, Google Ads and LinkedIn Insight Tag IDs per campaign.
How link retargeting works
Rebrandly's guide to retargeting links, last updated December 16, 2025, lists 5 steps: create a branded link, attach a retargeting script from Meta, Google Ads, LinkedIn, TikTok or X, a user clicks, the pixel fires during the redirect, and the platform adds that person to an audience.
Replug's retargeting page says its pixels fire on the short link, so the owner of the destination installs nothing. A Meta Pixel on your own site sees which pages people view; on a link it sees only the click.
Tools that include link retargeting
| Tool | Pixels it supports | Availability |
|---|---|---|
| Replug | Meta Pixel, Google Ads, Google Analytics 4, Google Tag Manager, X, LinkedIn, Pinterest, TikTok, Quora and custom code | Billed annually, per month: Essentials $9 (1 pixel, 10,000 clicks), Scale $23 (unlimited pixels, 50,000 clicks), Agency $79 (unlimited pixels, 250,000 clicks); none on Free. Past the click limit, links redirect but pixels stop firing |
| Rebrandly | Meta Pixel, Google Ads, LinkedIn, TikTok and X | Professional, Growth and Enterprise, with a pixel per workspace or per link; none on Free or Essentials |
| Short.io | Meta Pixel and AdRoll | Pro, according to its Meta Pixel guide |
| TrackRev | Meta Pixel, Google Ads and LinkedIn Insight Tag, by ID only | Switched on per campaign in the link form |
Prices from each vendor's pricing page, October 2026 (Replug, Rebrandly). Short.io's plan comes from its Meta Pixel help article.
Which browsers let the pixel match a visitor
When the Meta Pixel uses first-party cookies, it saves an _fbp cookie for the redirect page's domain, according to Meta's documentation, updated January 9, 2026.
Linking that browser to an account typically needs cookies Meta keeps on its own domain, and a browser sends those only if it allows third-party cookies. I found no published match rate from Meta, Rebrandly, Replug or Short.io.
| Browser | Share, September 2026 | Third-party cookie default | Effect on a pixel on a redirect page |
|---|---|---|---|
| Google Chrome | 66.36% | Left to the user in Settings; Incognito blocks them (Google, April 22, 2025) | Can match visitors who have not blocked them; on October 17, 2025 Google announced the retirement of 10 Privacy Sandbox technologies |
| Apple Safari | 18.27% | Intelligent Tracking Prevention blocks them with no exceptions since Safari 13.1 and iOS 13.4 (WebKit, March 24, 2020) | Platform cookies are not sent; script-written cookies are deleted after 7 days without interaction |
| Microsoft Edge | 6.04% | Balanced, the default of 3 levels, blocks storage for advertising trackers unless the user has a site engagement score of 4.1 or more with that organization (Microsoft) | Partial |
| Mozilla Firefox | 2.80% | Total Cookie Protection confines cookies to the site that created them (Mozilla, rollout June 14, 2022) | A cookie set on the redirect page stays in that page's jar |
| Brave | Outside the top 6 | Shields block trackers and cross-site cookie tracking (Brave) | Blocked |
Shares are StatCounter's worldwide figures. Samsung Internet (2.31%) and Opera (1.77%) are left out because I did not check their defaults.
Apple's App Store Review Guidelines, rule 2.5.6, require apps that browse the web to use WebKit, with engine entitlements for the EU and Japan.
Chrome and Firefox on an iPhone are built on it, so the Chrome row probably includes some iPhone traffic running on WebKit. See Safari ITP and iOS 17 Link Tracking Protection for what else Apple's browser removes.
Worked example with 5,000 clicks
Split 5,000 clicks like StatCounter's global mix. Chrome brings 3,318, Edge 302, Safari and Firefox together 1,054 (21.07%), and other browsers 326. Those 1,054 cannot be matched by default. Of the 3,620 in Chrome and Edge, anyone who declines ad cookies drops out too. If half accept, which is an assumption because banners and countries vary, 1,810 remain, or 36.2% of the 5,000. At the 10,000 monthly clicks of Replug's Essentials plan, the same split puts 2,107 Safari and Firefox visitors out of reach every month. Your analytics browser report will differ from the global mix, so rerun the arithmetic with your numbers.
Why consent is the harder problem
| Source | Date | What it asks |
|---|---|---|
| EDPB Guidelines 2/2023, version 2.0 | October 7, 2024 | Paragraphs 47 to 51 put tracking pixels and tracking links under Article 5(3) of the ePrivacy Directive, even when storage is temporary |
| Google EU User Consent Policy | No date shown | Legally valid consent, where legally required, for cookies and for personal data used in ad personalization, from users in the EEA, the UK and Switzerland, on properties you control |
| Meta Business Tools Terms | November 3, 2025 | Verifiable consent where law requires it before Meta cookies are stored; no pixels on websites you do not own |
A redirect page is on screen for a fraction of a second and has nowhere to collect consent, and neither Rebrandly's guide nor Replug's page explains how a visitor gives it.
The Business Tools Terms also bar pixels tied to your Business Manager or ad account on websites you do not own, which turns on whose domain serves the redirect.
A branded domain you control is arguably yours and a shared vendor domain is not. That is my reading, and the terms never mention link shorteners, so ask Meta or a lawyer first.
How to test your own match rate
Create a test campaign with a Meta Pixel, send 100 clicks from Chrome and 100 from Safari, and look in Events Manager and Pixel Helper for a PageView from the redirect domain.
After 7 days, compare the audience size the platform reports with the clicks in your link report. Audience sizes are estimates.
When the destination is your own site, a pixel there behind a consent banner reaches the same visitors on firmer legal ground.
What to build instead
A server-side click log counts every visit in every browser, and joined to payments it shows which links produced revenue; see link tracking without cookies and server-side versus client-side click tracking.
For audiences, Google Customer Match matches uploaded emails and phone numbers against signed-in Google accounts. Memberships last at most 540 days, and a list needs 100 members added or refreshed in that window.
Neither reaches readers of content you do not own, which is what link retargeting uniquely offered.
Link retargeting in TrackRev
TrackRev stores a Meta Pixel ID, Google Ads tag ID or LinkedIn Insight Tag ID once per workspace under Settings and Integrations, and you tick "Enable link retargeting" on each campaign.
Visitors pass through a page that loads each script, waits 800 milliseconds and continues. Bots and link-preview crawlers get a plain redirect, and a human click is logged once.
It takes IDs only, for 3 platforms, with no custom code. Replug, with 9 platforms plus custom code, fits better if you need TikTok, Pinterest, X or Quora.
The pass-through page shows no consent prompt, so for visitors in the EEA, the UK or Switzerland I would leave it off unless you collect consent before the click.
On paid plans the same link ties the visit to the Stripe, Paddle, Polar or Lemon Squeezy payment it produced; see Links and Analytics, first-party tracking and the PixelMe comparison.
The free plan covers link tracking with 50 links and 1,000 tracked events a month, and revenue figures start on Starter at $39 a month.
Found this useful? Share it.
Frequently asked questions
- It builds ad audiences from link clicks. A Meta Pixel, Google Ads tag or LinkedIn Insight Tag sits on a short link's redirect page, so each click can add the visitor to an audience for later ads. The link can lead to your site or anyone else's.
- For some visitors. Chrome and Edge hold 72.40% of share and allow some cross-site cookie matching, while Safari and Firefox (21.07%) do not, so measure the match rate on your own traffic.
- Yes, because the pixel fires on the redirect page and the destination installs nothing. Consent rules, Meta's Business Tools Terms and the EDPB's Guidelines 2/2023 still apply, including the limit on pixels placed on websites you do not own.
- Only with a legal basis under the GDPR (Regulation 2016/679) for the data the pixel sends, plus consent where the ePrivacy Directive (2002/58/EC) requires it, which for advertising pixels generally means before the pixel fires. This is general information and not legal advice, so check your own setup with a lawyer.
- Yes, per campaign, for Meta Pixel, Google Ads and LinkedIn Insight Tag IDs. Its pass-through page shows no consent prompt, and it records the click on its own server whether or not a pixel fires.
- Mostly not for matching. Safari has blocked all third-party cookies since March 24, 2020, and Chrome and Firefox on an iPhone generally run on WebKit under App Store rule 2.5.6.
- Replug starts at $9 a month billed annually for 1 pixel and 10,000 clicks, and its $23 Scale plan removes the pixel limit at 50,000 clicks. Rebrandly includes it from Professional, and Short.io's Meta Pixel guide says Pro.
Written by
Founder, TrackRev.io & Contant.io
Muzahid Maruf is the founder of TrackRev.io and Contant.io. He writes about marketing attribution, link tracking, and revenue analytics for SaaS teams.
Writes about Marketing attribution · Link tracking · Revenue analytics · SaaS growth
Stop guessing where your revenue comes from.
Set up TrackRev in about five minutes. The free plan covers 1,000 events a month, no card needed.
Start free