---
title: "Meta Pixel retargeting for QR codes and links"
description: "Connect your Meta Pixel to Linkbreakers so every person who scans your QR codes or opens your links joins your Facebook and Instagram audiences. Where to find the Pixel ID, the PageView it sends, the audiences you can build, how to check it fires, consent and limits."
canonical: "https://linkbreakers.com/help/article/meta-pixel-retargeting-for-qr-codes-and-links"
last-updated: 2026-11-03
---

# Meta Pixel retargeting for QR codes and links

> Connect your Meta Pixel to Linkbreakers so every person who scans your QR codes or opens your links joins your Facebook and Instagram audiences. Where to find the Pixel ID, the PageView it sends, the audiences you can build, how to check it fires, consent and limits.

Video: [QR code retargeting: add a Facebook pixel to your QR codes](https://www.youtube.com/watch?v=w_NBaINSUFo)

:::try-ai-prompt {"prompt":"Connect my Meta pixel 123456789012345 to all my links and QR codes","description":"Set up the Meta Pixel with the Assistant.","target":"assistant"}:::

## Short answer

Open **Integrations** in the Linkbreakers dashboard, pick **Meta Pixel** under **Retargeting pixels**, paste your Pixel ID and select **Connect**. From then on, every person who scans one of your QR codes or opens one of your links fires your Meta Pixel with a `PageView`, and you can build a Facebook and Instagram audience from them in Meta.

The pixel adds a short page before the redirect, usually well under a second and never longer than 2 seconds. It is available on every plan, Free included.

## Quick summary

- One Pixel ID per workspace, applied to every link and QR code by default, or only to the links you select
- Sends the standard `PageView` event, nothing else
- The page URL Meta records is the Linkbreakers short link address, which lets you build an audience per campaign
- Only people fire it: bots, link previews, AI agents and automated browsers are skipped
- Consent for marketing cookies is the workspace's responsibility
- Also available from the Assistant, the MCP server, the REST API and the CLI

## How it works with Meta

Once the Meta Pixel is connected, a person's visit goes through a brief page in their browser. That page loads Meta's standard base code, runs `fbq('init', '<your Pixel ID>')` and `fbq('track', 'PageView')`, then redirects to your destination as soon as Meta has answered the PageView. Meta's script fetches your pixel's settings before it sends the PageView, so on a slow phone connection the page waits for it: up to 1.2 seconds, or up to 2 seconds when the PageView is already on its way. See [how retargeting pixels fire on slow mobile connections](/help/article/how-retargeting-pixels-fire-on-slow-mobile-connections) for the measurements.

In Meta, this is the same `PageView` a website sends when the pixel is installed on its pages. The event reports the page URL, which is the address of the Linkbreakers link that was opened, such as your short link or your custom domain link.

That gives you two ways to use it:

- **Everyone who scanned or clicked**: a website custom audience of all visitors on the pixel
- **One campaign at a time**: a website custom audience of people who visited pages whose URL contains the short link of that campaign

### Audiences you can build

In Meta Ads Manager, create a **Custom audience** with **Website** as the source and your pixel selected. Then choose either all website visitors or people who visited specific web pages, with a URL rule that contains your short link's path. Set the retention window you want.

From that custom audience you can also create a **Lookalike audience**, to reach people similar to those who scanned.

Meta needs time to fill an audience, and its help mentions about 24 to 72 hours. Ads only serve once the audience is large enough for Meta.

## Where to find your Pixel ID

In **Meta Events Manager**, select your pixel (Meta also calls it a dataset) under your data sources. The Pixel ID is the number shown with it, often in the pixel's settings. Copy the digits only.

Linkbreakers checks the shape when you save: a Meta Pixel ID is 10 to 20 digits. An ID with letters or spaces is refused with `RETARGETING_PIXEL_INVALID`, and nothing is changed.

## Step-by-step in Linkbreakers

1. Open the dashboard and go to **Integrations**
2. Under **Retargeting pixels**, open **Meta Pixel**
3. Paste your Pixel ID and select **Connect**
4. Read the delay notice and the consent note on the page
5. [Check that the pixel fires](#how-to-check-that-it-fires)

To use another pixel, open the same page, replace the ID and select **Save**. To turn it off, select **Remove**. When no pixel is left on the workspace, links go back to redirecting instantly.

## How to check that it fires

1. Install Meta's Chrome extension. It used to be called **Meta Pixel Helper** and is now listed as **Meta Ads Data Advisor** in the Chrome Web Store
2. Open one of your links in a normal browser window, not a private window with tracking blocked
3. The extension shows your pixel loading and the `PageView` being sent before the redirect. The page is brief, so reopen the extension's history if it moves on too fast

In Events Manager, the `PageView` events appear on your pixel after a few minutes, with the short link address as the URL. Check the URLs there before you build a per-campaign audience.

Ad blockers and some browsers' tracking protection block the Meta Pixel. Visitors who use them block it on your links too, as on any website.

## The short delay

A pixel is JavaScript that runs in the visitor's browser, and a plain redirect runs none. So once a pixel is connected, people's visits go through the brief page described above: usually well under a second, never longer than 2 seconds. Workspaces without any pixel keep the instant redirect.

If you also use Advanced data collection, both share the same page, so the visit loads one page, not two.

## Who fires the pixel

Only visits classified as **Human** go through the pixel page. Crawlers, link previews (Slack, Teams, Discord, WhatsApp, Facebook, LinkedIn), AI agents and recognized automated browsers get the instant redirect and never reach your Meta audiences. When someone shares your link in a Facebook post or a WhatsApp group, the preview bot does not join your audience.

See [how Linkbreakers detects AI agents and automated browsers](/help/article/how-linkbreakers-detects-ai-agents-and-automated-browsers) for how visits are classified.

## Consent

The Meta Pixel sets Meta's marketing cookies. In the EU and the UK, that usually needs the visitor's consent first. Linkbreakers does not show a consent banner. Covering the pixel in your privacy policy and consent setup is the workspace's responsibility.

## Set it up from an AI agent, the API or the CLI

**Assistant**: in the dashboard, ask "Connect my Meta pixel 123456789012345 to all my links".

**MCP server**: an agent connected to the [Linkbreakers MCP server](/help/article/mcp-server-setup) calls `retargeting_pixels_update` with `meta_pixel_id`. Only the fields sent change, so the other pixels keep their value. For example:

> Set my Meta pixel to 123456789012345 on my Linkbreakers workspace and leave the other pixels as they are.

**REST API**, with a token that has the `integrations:write` scope:

```bash
curl -X PUT https://api.linkbreakers.com/v1/retargeting-pixels \
  -H "Authorization: Bearer $LINKBREAKERS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"metaPixelId": "123456789012345"}'
```

Send `{"metaPixelId": ""}` to remove it.

**CLI**, from the next CLI release:

```bash
linkbreakers retargeting-pixels update --meta-pixel-id 123456789012345
```

See [set up every Linkbreakers integration with an AI agent](/help/article/set-up-linkbreakers-integrations-with-an-ai-agent-mcp) for the other integrations an agent can configure.

## Limits and caveats

- **Page views only.** Linkbreakers sends `PageView`. It does not send `Lead`, `Purchase` or other events, and there is no Conversions API connection
- **All links by default.** The pixel fires on every link and QR code of the workspace until you choose **Selected links** under **Where it fires** and pick links, directories or tags; a separate workspace still gives a client separate pixels
- **One Meta Pixel per workspace.** To fire a second Meta Pixel, add it as a tag in [Google Tag Manager](/help/article/google-tag-manager-for-qr-codes-and-links)
- **Short delay on people's visits**, usually well under a second, never longer than 2 seconds
- **No consent banner.** Consent is the workspace's responsibility
- **Blocked like any pixel** by ad blockers and tracking protection
- **Audiences fill on Meta's schedule** and need a minimum size before ads serve

## Frequently asked questions

### Which event does Linkbreakers send to Meta?

The standard `PageView`, with the Linkbreakers link address as the page URL.

### Can I build an audience for one QR code only?

Yes, in Meta. Create a website custom audience of people who visited specific web pages, with a rule on the URL of that QR code's short link.

### Can I make a lookalike audience from the people who scanned?

Yes. Build the website custom audience first, then create a lookalike audience from it in Meta.

### Does my destination website still need its own pixel?

For anything after the redirect, yes. Linkbreakers fires the pixel on the visit to the link. Purchases, sign-ups and other events on your website still come from the pixel installed there.

### Will people who see my link in a Facebook post preview join the audience?

No. Link preview bots get the instant redirect and never load the pixel.

### Why was my Pixel ID refused?

A Meta Pixel ID is 10 to 20 digits. Copy the number only, with no spaces, letters or the word "ID".

## Sources

- Linkbreakers Meta Pixel page, API and MCP tool, checked in the product on 2026-10-30.
- [Retargeting pixels overview](/help/article/retargeting-pixels-meta-google-tiktok-linkedin-and-google-tag-manager)
- [How to retarget people who scanned your QR code with ads](/help/article/how-to-retarget-people-who-scanned-your-qr-code-with-ads)
- Meta for Developers, get started with the Meta Pixel: https://developers.facebook.com/docs/meta-pixel/get-started
- Meta Business Help Center, learn about Meta Pixel: https://www.facebook.com/business/help/742478679120153
- Meta Business Help Center, create a website custom audience: https://www.facebook.com/business/help/1474662202748341
- Meta Business Help Center, about Lookalike Audiences: https://www.facebook.com/business/help/164749007013531
- Chrome Web Store, Meta Ads Data Advisor (formerly Meta Pixel Helper): https://chromewebstore.google.com/detail/meta-pixel-helper/fdgfkebogiimcoedlicjlajpkdmockpc

## Last reviewed

2026-10-30 by Laurent Schaffner.
