LINK RETARGETING

Fire your pixel before the redirect.

Attach Meta, TikTok, Google, LinkedIn, and Pinterest pixels to any OfferSwap short link. Every click becomes an audience member, including clicks to sites you do not own.

https://
  • Pixels fire before the 302
  • Multiple pixels per link
  • Works on affiliate URLs
  • Async, no click latency
WHY RETARGET

You only get one shot at most visitors.

A normal short link is a one-way door. The user clicks, hits the destination, leaves, and the only data you keep is a row in your analytics. You cannot retarget them on Meta because you do not own the page they landed on. Link Retargeting fixes that by firing your tracking pixels on the resolver page (the brief interstitial between click and destination), so the visitor lands in your custom audience whether or not they ever converted.

Where it's used

One link. Every surface.

01

Affiliate marketers

Drop a Meta pixel on your Amazon links. Anyone who clicked through to a product is now a retargetable audience, even though you do not own amazon.com.

02

Curators & newsletter ops

Sharing third-party articles? Pixel-tag the link so every reader joins a Lookalike seed audience for your real funnel.

03

Paid social

Layer a TikTok pixel on top of a Meta pixel on top of a Google tag: three audiences, one short link, one click.

What you get

Everything built in.

◐Core

Fires before redirect

The pixel call happens in the same response as the resolver page, before the visitor is bounced to the destination.

⇆Core

Async, sub-100ms

Pixels load in parallel with the redirect. The visitor never sees a measurable delay, even on flaky mobile networks.

✦Agent

Agent-managed pixels

Use the MCP server to attach or rotate pixels per campaign. Your agent reads your Meta + TikTok IDs from config once and reuses them.

▦Core

UTM preservation

utm_source, utm_campaign and any custom params survive the redirect untouched so your destination analytics still attribute correctly.

◆Core

Works on every link

Retargeting is a link-level toggle. Apply it to one campaign URL or your entire portfolio. No separate plan, no per-pixel fee.

How it works

Three steps. That's it.

  1. 01

    1. Add pixel IDs

    Paste your Meta, TikTok, or Google pixel IDs into Traffic & Pixels (or push them via the API).

  2. 02

    2. Toggle per link

    Choose which pixels fire on which links. Default-on rules let you cover everything you ship by default.

  3. 03

    3. Build audiences

    In Meta or TikTok, create a Custom Audience from "people who visited a URL" using your short link domain.

Yes. The pixel fires on the OfferSwap domain, before the redirect to Amazon. Your audience grows even though the user never touches a property you own.

Meta Pixel, TikTok Pixel, Google Ads tag, GA4, LinkedIn Insight Tag, Pinterest Tag, X Pixel, Snap Pixel, and Reddit Pixel. Add multiple per link.

Not measurably. Pixels are fired async on the resolver page and the redirect happens in parallel. Typical added latency is well under 100ms.

Yes. utm_*, gclid, fbclid, and arbitrary query strings are forwarded to the destination URL untouched.

Yes. The MCP server exposes a set_pixel tool so Claude or Cursor can add or rotate pixel IDs across links without you opening Settings.

Pixels fire on the resolver page, then we hand off to the app. The web-based pixel call completes before the OS opens the native app.

Every click is a person you can talk to again.

Connect your agent in 30 seconds. One MCP install, no card.