How link retargeting works, and where browsers and EU rules break it

Link retargeting is the practice of adding 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.

Safari plus Firefox cover 21.07% of visitors. EU and UK rules add a consent step, and a redirect page cannot show one. In practice, 3 limits shape the result: the browser, the consent rule and the ad platform's terms.

How does link retargeting work?

Link retargeting is a 5-step process.

Rebrandly's guide to retargeting links, last updated December 16, 2025, lists the 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, the pixel sees only the click, because the redirect page holds no content to view. The platform then builds the audience for later Meta, Google Ads or LinkedIn campaigns.

Sources: rebrandly.com/blog · replug.io/retargeting-pixels

Which tools include link retargeting?

Link retargeting is a paid feature at Replug, Rebrandly and Short.io.

Replug supports 9 platforms plus custom code and bills Essentials at $9 a month for 1 pixel and 10,000 clicks, Scale at $23 for unlimited pixels and 50,000 clicks, and Agency at $79 for 250,000 clicks.

Past the click limit, Replug links still redirect, but pixels stop firing. Rebrandly includes retargeting from its Professional plan, with Meta Pixel, Google Ads, LinkedIn, TikTok and X. Short.io names Meta Pixel and AdRoll on Pro.

TrackRev fires Meta Pixel, Google Ads and LinkedIn Insight Tag IDs per campaign, and the table below sets the 4 vendors side by side.

Which browsers let a pixel match a visitor?

A pixel match is the step where an ad platform links a browser to a known account.

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.

According to StatCounter (September 2026), Chrome holds 66.36% and Safari 18.27%, so the default of each browser decides the outcome for most clicks.

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 WebKit, 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.

How many of 5,000 clicks can a pixel match?

A match estimate is a short sum, and the sum shows the scale of the loss. For example, 5,000 clicks split like StatCounter's global mix leave only a fraction matchable.

Why is consent the harder problem?

Consent is the legal permission to set an ad cookie, and consent is the harder problem because a redirect page is on screen for a fraction of a second with nowhere to collect it.

According to EDPB Guidelines 2/2023 (October 7, 2024), tracking pixels and tracking links fall under Article 5(3) of the ePrivacy Directive. Neither Rebrandly's guide nor Replug's page explains how a visitor gives consent.

The Meta 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 do you test your own match rate?

A match-rate test is a short experiment on your own traffic. First, create a test campaign with a Meta Pixel.

Second, send 100 clicks from Chrome and 100 from Safari, and look in Meta Events Manager and Pixel Helper for a PageView from the redirect domain.

Third, after 7 days, compare the audience size the platform reports with the clicks in your link report.

Audience sizes are estimates, so expect Chrome to show a higher share than Safari, which blocks all third-party cookies since March 24, 2020. For example, 100 Chrome clicks and 100 Safari clicks reveal the gap in one afternoon.

When the destination is your own site, a pixel there behind a consent banner reaches the same visitors on firmer legal ground.

What can you build instead of link retargeting?

A server-side click log is the replacement for link retargeting in measurement: the 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. Google documents the 540-day and 100-member limits on its Customer Match page, so plan a list refresh at least once a year.

How does link retargeting work in TrackRev?

TrackRev is SaaS affiliate software with link tracking built in.

In our build, 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. In our pass-through page, bots and link-preview crawlers get a plain redirect, and we log a human click once.

TrackRev 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 Billing, Polar, Lemon Squeezy, Creem or Dodo Payments payment it produced; see Links and Analytics, first-party tracking and the PixelMe comparison.

Revenue figures start on Indie at $29 a month.