---
title: "Retargeting pixels: retarget everyone who scans your QR codes"
description: "New: add your Meta Pixel, Google tag, TikTok Pixel, LinkedIn Insight Tag or Google Tag Manager container once, and every link and QR code of your workspace fills your ad audiences. Available on every plan, and from the API, MCP server, CLI and SDKs."
canonical: "https://linkbreakers.com/help/article/retargeting-pixels-retarget-everyone-who-scans-your-qr-codes"
last-updated: 2026-11-04
---

# Retargeting pixels: retarget everyone who scans your QR codes

> New: add your Meta Pixel, Google tag, TikTok Pixel, LinkedIn Insight Tag or Google Tag Manager container once, and every link and QR code of your workspace fills your ad audiences. Available on every plan, and from the API, MCP server, CLI and SDKs.

## Short answer

New today: **Integrations > Retargeting pixels**. Paste your Meta Pixel ID, Google tag, TikTok pixel ID, LinkedIn partner ID or Google Tag Manager container ID, and every link and QR code of your workspace adds the people who open it to your audiences on those ad platforms. You can then show ads to everyone who scanned your packaging, your poster or your booth sign.

Pixels add a short delay to every visit, usually well under a second and at most 2 seconds (1.2 seconds unless a Meta or TikTok page view is still on its way), because a pixel has to run in the visitor's browser. Without pixels, links keep redirecting instantly. Retargeting pixels are available on every plan, Free included, and everything can be set up by an AI agent, the API, the CLI or the SDKs as well as the dashboard.

## What we shipped

### Five pixels, each with its own page

Open **Integrations** in the dashboard: under **Retargeting pixels**, each platform has its own card and page, where you paste its ID:

| Pixel | What you paste | What it feeds |
|---|---|---|
| Meta Pixel | Pixel ID, digits only, such as `123456789012345` | Facebook and Instagram audiences |
| Google tag | A Google Analytics 4 measurement ID (`G-...`) or a Google Ads tag (`AW-...`) | Google Ads remarketing audiences and GA4 page views |
| TikTok Pixel | Pixel ID, such as `C4ABCDEFGHIJKLMNOPQR` | TikTok audiences |
| LinkedIn Insight Tag | Partner ID, digits only | LinkedIn audiences |
| Google Tag Manager | Container ID (`GTM-...`) | Whatever your container holds, such as Pinterest, Snap, Reddit, X or Microsoft Ads tags |

Each ID is checked for the right shape when you save. Select **Remove** on a pixel's page to turn it off.

Each pixel also has its own guide: [Meta Pixel](/help/article/meta-pixel-retargeting-for-qr-codes-and-links), [Google tag](/help/article/google-tag-ga4-and-google-ads-for-qr-codes-and-links), [TikTok Pixel](/help/article/tiktok-pixel-retargeting-for-qr-codes-and-links), [LinkedIn Insight Tag](/help/article/linkedin-insight-tag-retargeting-for-qr-codes-and-links) and [Google Tag Manager](/help/article/google-tag-manager-for-qr-codes-and-links).

To report scans in Google Analytics without the delay, see the [Google Analytics 4 integration](/help/article/google-analytics-4-integration-for-qr-codes-and-links), which sends them from our servers.

### Every link and QR code, at once

Pixels apply to every link and QR code of the workspace by default: once a pixel is set, every visit by a person fires it. Since 2026-11-01 you can also fire a pixel only on selected links, directories or tags, from **Where it fires** on the pixel's page.

### Why there is a short delay

A pixel is JavaScript that runs in the visitor's browser. A plain redirect sends the browser straight to the destination, so no script ever runs. Once any pixel is set, a person's visit goes through a brief page that loads each platform's standard base code, sends a page view, then redirects.

The visitor leaves as soon as the scripts have loaded and had a moment to send the page view, after at most 2 seconds (1.2 seconds unless a Meta or TikTok page view is still on its way). It is usually well under a second. This is the same short page that [Advanced data collection](/help/article/what-data-you-can-collect-from-qr-code-scans-location-device-behavior) uses, so a link that has both loads one page, not two.

Every link tool that fires retargeting pixels does it this way, with a page in the browser before the redirect. Each pixel's page in the dashboard shows the same warning, so nobody turns pixels on without knowing.

### Only people enter your audiences

Pixels fire only for visits classified as **Human**. Crawlers, link previews (Slack, Teams, Discord, WhatsApp, Facebook, LinkedIn), [AI agents and automated browsers](/help/article/how-linkbreakers-detects-ai-agents-and-automated-browsers) get the instant redirect and never land in your audiences. Pasting a link in a group chat does not add the preview bot to your Meta audience.

### Built for agents too

Everything on the pixel pages is also available without the dashboard:

- **MCP server**: `retargeting_pixels_get` and `retargeting_pixels_update`
- **REST API**: `GET /v1/retargeting-pixels` and `PUT /v1/retargeting-pixels`, with the `integrations:read` and `integrations:write` scopes
- **CLI**: `linkbreakers retargeting-pixels get` and `linkbreakers retargeting-pixels update`, arriving with the next CLI release
- **SDKs**: the same two operations in TypeScript, Python, Go, Java and Rust
- **Assistant**: ask "Add my Meta pixel 123456789012345 to all my links" in the dashboard

An update sends only the pixels to change. An empty string removes one, and the ones you leave out keep their value. For example, an AI agent connected to the [MCP server](/help/article/mcp-server-setup) can take this prompt as is:

> Check which retargeting pixels my Linkbreakers workspace has, then set my Meta pixel to 123456789012345 and my Google tag to G-ABC1234, and leave the others as they are.

The [feature article](/help/article/retargeting-pixels-meta-google-tiktok-linkedin-and-google-tag-manager) has the API request, the CLI flags and where to find each ID.

## Who it helps

- **Consumer goods brands** can retarget people who scanned the QR code on a pack with a refill or a new flavor
- **Event and trade show teams** can show follow-up ads to everyone who scanned the booth sign, including the people who did not fill in the form
- **Out-of-home campaigns** can turn poster and flyer scans into an audience for the online campaign that follows

See [how to retarget people who scanned your QR code with ads](/help/article/how-to-retarget-people-who-scanned-your-qr-code-with-ads) for the full setup.

## Limits and caveats

- Pixels add a short delay to every visit by a person, usually well under a second and at most 2 seconds (1.2 seconds unless a Meta or TikTok page view is still on its way)
- Pixels apply to the whole workspace by default; choose Selected links on a pixel's page to limit it
- Each pixel sends a page view. Purchases, leads and other conversion events are not sent, and there is no server-side Conversions API connection
- Linkbreakers does not show a consent banner; consent for marketing cookies is the workspace's responsibility

## Frequently asked questions

### Which plans include retargeting pixels?

Every plan, Free included.

### Will my links get slower?

Only once a pixel is set, and only for people's visits: a short page loads before the redirect, usually well under a second and at most 2 seconds (1.2 seconds unless a Meta or TikTok page view is still on its way). Remove every pixel and links redirect instantly again.

### Can I put a pixel on one link only?

Yes, since 2026-11-01. On the pixel's page, choose Selected links under Where it fires and pick the links, directories or tags it should fire on. It fires on every link by default.

### Does Linkbreakers show a cookie consent banner?

No. Pixels set marketing cookies, which in the EU and the UK usually need the visitor's consent. Covering that in your privacy policy and consent setup is the workspace's responsibility.

### When will my audience fill up?

The ad platform decides. Audiences take time to build on their side; Meta mentions about 24 to 72 hours.

### Does it send purchases or other conversions?

No. Each pixel sends a page view for the visit. Conversion events stay on your own website.
